►
Description
Webcast around covering details on how to upgrade your SharePoint Framework solutions to use the latest packages from Microsoft. Detailed description of covered topics available from http://dev.office.com/blogs
A
Welcome
everybody:
this
is
SharePoint
prevention
practices
webcast
on
system.
We
wanted
to
actually
address
some
of
the
common
questions.
What
we're
all
the
time
getting
around
the
SharePoint
framework,
because
from
Shibata
engineering
sites
were
releasing
new
versions
every
now
and
then
and
in
future,
maybe
in
a
more
frequent
even
more
frequently
so
we're
looking
into
aligning
to
a
certain
schedule.
One
of
the
questions
what
the
community
always
enhanced
is
that.
A
Okay,
now
that
you've
released
a
new
version,
for
example,
1.4
version
under
both
1.3
version,
what
do
I
actually
need
to
do
to
make
that
upgrade
happen?
Do
I
go
to
the
package.json
and
update
that
back
a
JSON
file,
which
is
by
the
way
wrong
answer
or
do
I
do
something
else.
So
in
this
webcast
we'll
walk
through
the
steps
of
going
through
that
and
going
through
those
steps
to
get
upgraded
on
the
latest
version.
A
A
Thank
you,
Thank
You,
Paula,
so
and
we'll
jump
into
the
walk
through
first
the
steps
in
slides
and
then
we'll
have
a
live
demo
from
one
point.
Three
at
one
point
four
I
think
that's,
and
that
was
actually
two
demo
today,
but
well.
Let's
actually
politie
lead
the
discussion
and
I'll
jump
in
and
ask
questions
where
needed.
Okay,.
B
So
yeah,
so,
let's
assume
that
we
have
a
SharePoint
framework
solution
can
can
be
a
client-side
web
part
or
an
extension
or
whatever
house
you
built
using
the
SharePoint
framework,
and
let's
say
that
now
you
want
to
update
it
to
the
latest
version
of
the
packages
that
you
have.
So
let's
try
to
see
how
to
do
that
following
the
right
part
of
the
right
pattern.
B
So,
first
of
all,
you
need
to
find
what
are
the
outdated
packages
that
you
have
in
your
environment
and
likely
NPM
provide
us
with
a
common
which
is
the
outdated
common
which
will
let
us
know
what
are
the
outdated
packages
that
we
have
in
our
current
solution.
From
a
SharePoint
framer
perspective,
you
have
to
look
for
the
at
Microsoft,
slash
SPD,
because
all
of
those
packages
will
be
the
packages
included
in
the
SharePoint
framework
development,
and
so
you
will
need
to
update
all
of
those
packages
to
update
them.
Pretty
easy,
pretty
straightforward.
B
You
simply
need
to
say
npm
install,
which
will
be
the
comment
from
an
NPM
perspective.
You
provide
the
package
name
at
the
version
that
you
want
to
download.
You
want
to
install
in
your
solution.
That's
the
saver
to
save
it
locally.
Moreover,
if
you
want
just
to
install
the
latest
version,
you
can
just
say
package
name
at
latest
to
get
the
latest
and
greatest
version
of
the
package
that
you
want
to
install
actually.
A
Something
I'm
just
going
to
jump
there.
The
desktop
save
is
for
saving
that
locally
to
the
package
situation,
just
to
pay
precise.
So
that's
the
save
is
to
make
sure
that
when
you've
done
the
NPM
install
package
name
and
version
it
will
be
then
an
entry
in
the
package
JSON.
So
whenever
you
check
in
your
code
to
the
visitors
to
the
online
or
kit
and
some
people's
down
under
stuff-
and
they
do
NPM
install,
that
means
it
is
the
in
the
in
the
right,
JSON
format
or
mention
to
be
dependent.
So
sorry,
sorry.
B
Totally,
ok
once
you've
done
that
you,
you
should
make
a
cleanup
of
your
project,
so
gout
cleanup
and
golf
builder
to
build
your
solution
with
the
new
bit
with
the
new
version
of
the
libraries.
Of
course
it
could
happen,
and
sometimes
it
happens,
that
between
one
version
and
another
version
of
a
package
that
you
are
using
in
your
solution,
that
something
will
be
changed
and
there
will
be
some
breaking
changes
so
most
likely
when
you
will
execute
the
gulp
but
build
the
commands.
You
will
also
have
to
face
some
issues.
B
Some
compilation
issues
that
you
will
have
to
fix
before
being
able
to
release
the
new
and
updated
version
of
your
project,
so
keep
in
mind
that
there
will
be
some
work
around
the
updater
and
most
likely
you
will
have
to
update
some
code
or
some
configuration
files
in
order
to
being
able
to
build
again
your
solution
and,
depending
on
how
far
you
are
upgrading
your
solution
from
so.
If
you
are
bringing
your
solution
for
a
very
early,
a
version
of
SPF
X
to
the
latest
one.
B
B
You
need
to
use
NPM,
updated,
g4,
global
or
globally,
so
you
will
get
the
list
of
globally
available
packages
and
there
will
be
the
Mike's
of
the
generator
SharePoint
in
that
list.
If
you
install
that
one
globally,
of
course,
to
update
the
yeoman
generator,
the
syntax
from
an
NPM
perspective
is
exactly
the
same
as
before
so
NPM
install
at
Microsoft,
slash
generator
SharePoint
at
leaders
to
get
the
latest
version
and
again
the
g2
update
it
at
the
global
level.
B
In
your
machine,
you
also
need
to
keep
in
mind
that
you
can
always
play
locally
in
a
local
folder,
with
a
different
version
of
the
yeoman
generator
and
our
of
all
of
the
packages
that
you
want
to
use,
and
you
will
simply
need,
for
example,
to
create
local
folder
to
an
NPM
install
of
at
Mike's
or
/
generator
SharePoint
and
select
any
specific
version
that
you
want
to
target.
Once
you
have
done
that.
B
So
it
could
be
that
you
need
not
only
to
update
the
SharePoint
framework
libraries,
but
also
some
of
the
dependencies,
and
the
same
would
happen
when
you
will
build
the
solution
after
the
update.
Maybe
you
will
have
to
fix
the
stuff
not
only
and
not
just
related
to
SPF
X
but
may
be
related
to
reactor
or
office
UI
fabric
or
new
styles,
from
a
UI
perspective,
and
so
on
so
forth.
B
Moreover,
if
you
build
a
solution
targeting
sharepoint
2016
at
the
time
of
this
recording,
for
example,
the
sharepoint
framework
for
sure
appointed
on
16
uses
a
another
version
of
the
libraries.
So
you
should
be
really
careful
updating
such
kind
of
solutions
because,
for
example,
if
you
will
update
the
solution
for
sure
position,
16
to
the
latest
version
of
SharePoint
River,
there
could
be
some
issues
in
the
on-premise
environment.
On.
A
That
one
actually
power
is
that
at
the
moment
of
the
recording
of
Twitter
upon
2016,
it
is
using
an
older
version.
Then
in
SharePoint
Online
that
the
answer
is
yes,
it
will
always
be
using
all
the
version
and
SharePoint
happy,
because
the
reality
is
are
that
we
don't.
We
can't
control
your
own
premises
environment.
So
whenever
we
are
shipping
a
our
doing,
a
new
operate
on
SharePoint
2016,
a
potentially
maybe
at
some
point
we
will
support
a
newer
version.
Not
just
one
point.
One
version
in
SharePoint
2016
feeds
back
to
eventually
very
unlikely.
A
B
B
So
let's
say
that
I
think
we
are
ready
to
see
how
to
update
a
solution
which
has
been
built
using
a
sharepoint
framework,
one
point
3.0
to
the
latest,
one,
which
is
one
point
4.0
at
the
time
of
this
recording
again
one
more
time
so
time
for
demo.
Okay,
okay,
here
we
are
in
Visual
Studio
code,
and
here
we
have
a
client-side
web
part
project,
which
is
now
using
version
1.3
point
0
of
the
SharePoint
framework.
B
Now,
let's
assume
that
we
want
to
update
this
solution
to
the
latest
version
of
SharePoint
framework,
at
least
at
the
time
of
this
recording,
which
is
nowadays
one
point
four
point
one.
So,
first
of
all,
in
order
to
understand,
if
our
solution
is
up-to-date
or
has
any
outdated
package,
we
can
simply
use
NPM
powder
dated
with
this
command.
B
You
will
be
able
to
see
what
are
the
packages
and
the
version
of
your
packages
compared
with
the
latest
versions
available
on
network
and,
as
you
can
see
here,
I
have
few
packages
at
Mike's
or
/,
something
which
are
those
related
to
the
SharePoint
framework.
Currently
I
have
one
point,
three
point,
four
version,
but
the
latest
one
on
the
network
is
one
point
four
point
one.
B
So,
in
order
to
update
the
packages
in
my
solution,
I
can
simply
use
the
NPM
install
command,
providing
the
name
of
the
package
that
I
want
to
update
and
any
specific
version
or
latest
to
say
that
I
want
to
get
the
latest
one
and
ministry
must
save
or
bash
that
save
to
store
the
information
in
the
package.json
file.
So
I
will
execute
this
common
for
each
and
every
sharpen
framework
package
that
I
have
in
my
solution
and
step-by-step
I
will
have
my
solution,
upgraded
or
updated.
B
So
now
we
updated
all
of
the
dependencies
in
the
packages
and
file.
As
you
can
see
now
we
have
one
point
four
point:
one
version
of
the
three
packages
and
we
now
need
to
update
the
depth.
Dependence
is
still
in
the
solution,
so
in
order
to
update
them
still
npm
install
the
name
of
the
package,
they
should
have
saved
as
them
which
will
go
into
the
dev
dependencies.
So
let's
execute
the
same
common
for
the
three
packages
that
we
have
in
dev
dependencies
and
then
the
solution
will
be
fully
updated.
B
And
here
we
are
now
we
have
version
one
point,
four
point,
one
of
all
of
the
packages
in
the
packages
and
file
and,
of
course,
in
the
solution.
So
we
are
now
ready
to
do
gulp
cleaner
to
clean
up
the
solution
and
to
build
again
using
how
to
build
the
full
solution.
There
could
be
some
issues,
some
build
issues
or
exceptions
which
we
will
need
eventually
to
fix,
and
it
really
depends
on
how
far
you
started
your
upgrades.
B
So
if
you
are
upgrading
back
to
back
one
version
to
the
new
one
most
likely,
you
will
adjust
a
few
issues.
Otherwise,
if
you
are
creating,
for
example,
from
a
very
old
version
of
the
SharePoint
framework
to
the
latest
one,
maybe
you
will
have
much
more
issues
to
face
in
two
minutes,
but
regardless
number
of
issues,
for
example,
here
I
have
three
tasks
here
or
I
can
fix
them.
B
B
Let
me
refresh
the
workbench
and,
let
me
add,
the
simple
web
part,
which
is
the
one
I
define
in
that
project
and,
as
you
can
see,
I
have
my
friend
said
web
part
based
on
one
point
four
point:
one
fully
functional
and
upgraded
from
version.
One
point
three
point:
zero,
so
that's
it
I,
don't
know
if
you
have
anything
to
add
the
ways
about
these
upgrade
the
process
and.
A
Well,
not
that
much
like
I
said
it's.
It's
didn't
know
that,
depending
on
a
version
and
cross
two
versions
which
you're
moving
there
might
be
some
bits
and
pieces
and
also
depending
what
your
code
is
actually
doing,
which
I
need
to
modify
within
the
code,
and
you
can
see
those
in
a
compilation,
output,
some
of
them
might
be
relatively
cryptic.
Some
of
them
might
be
pretty
logical
what
you
need
to
do
now,
if
there's
any
questions,
any
doubts
on
hey.
What
do
we
need
to
do
something?
A
Please
open
up
an
SBA
issue
in
the
SPD
books
and
we
from
engineering
can
actually
help
an
answering
why
certain
things
have
to
happen
so
or
maybe
there's
a
regression
and
you're
seeing
something
around
hey.
This
doesn't
make
any
sense.
Please
let
us
know
and
we'll
process
that
and
within
our
facial
engineering
process,
but
I
think
that's
it
follow
from
demo
site.
You
didn't
have
anything
else
to
show
right
exactly.
A
So,
let's
actually
flip
back
on
the
slides
and
close
up
the
webcast.
Thank
you
cool
and
that's
that's
all
we're
gonna
do
and
within
this
webcast,
so
Craig
demo,
Apollo
on
up,
create
steps
and
like
I,
saw
it's
not
actually
rocket
science
to
be
fair,
and
this
should
have
been
potentially
much
more
detailed
document
it.
But-
and
that's
one
of
the
reasons
why
we
actually
recorded
this
webcast
to
have
it
live,
save
videos.
A
So
you
can
always
repeat
the
steps
on
how
to
make
these
things
happen
and
it
like
you,
so
there's
something,
let's
say
changes
what
you
needed
to
do
in
the
case
of
one
point
three
to
one
point:
four:
on
the
code
base
as
well
and
those
are
always
dependent
on
version
and
so
being
a
ship
on
the
engineering
side.
We
tried
to
mention
then
in
release
notes,
but
it
might
be
that
we're
missing
them
and
yes,
we
need
to
potentially
do
a
better
job
on
that
one
in
the
future.
A
So
if
you
would
be
upgrading
from
one
point,
zero
to
one
point,
four,
the
steps
are
required
for
code
changes
are
slightly
more
significant,
so
it's
not
just
updating
packages
and
you'll
be
good
to
go
because
they
are,
there
might
be
changes
in
a
code
base,
anything
else.
What
we're
missing
power?
No.