►
From YouTube: Upgrade Web Parts using CLI for Microsoft 365
Description
In this 7 minute developer-focused demo, Hugo shows how to take an old version of an SPFx solution and update it with CLI for Microsoft 365. He also provides guidance on when to do this and why. 💡
🚀 Presenter: Hugo Bernier (Microsoft) | @bernierh
Resources:
✔️ https://pnp.github.io/cli-microsoft365/
✔️ https://aka.ms/m365pnp
✔️ https://pnp.github.io/blog
A
A
A
So,
let's
just
for
example,
let
me
go
to
the
sample
gallery
here
and
look
for
a
sample
that
I
remember
I
built
a
while
ago
that
allows
me
to
display
the
version
number
of
the
web
part
that's
currently
running,
and
it
was
a
very
simple
web
part,
but
it
was
built
in
spfx
110
and
we're
almost
at
114
now.
So
obviously,
this
is
a
great
opportunity
for
me
to
upgrade
it
now.
A
A
few
things
we
need
to
think
about
one
is,
if
you're
trying
to
upgrade
a
gigantic
solution
that
has
a
lot
of
web
parts
and
a
lot
of
components,
it's
probably
easier
for
you
to
rebuild
a
new
solution
and
import
the
web
parts
into
it.
But
if
you're
trying
to
just
do
a
simple
upgrade
of
a
symbol,
a
web
part
solution
there's
a
tool
for
that.
A
A
A
A
So
it's
up
to
you
whether
you
want
to
use
the
code
tour
option
or
the
markdown
version,
or
the
text
version
it's
up
to
you
for
the
purpose
of
this
sample,
I'm
going
to
use
a
code
tour
because,
frankly,
it
looks
cool
alright.
So,
let's
go
to
the
code
tour:
let's
do
this
and
I'm
going
to
go
into
the
terminal.
A
A
Let
me
hit
get
started
and
while
it's
doing
this,
you
know
the
code,
tour
extension
is
installed
here.
What
we
should
see
is
that
it
doesn't
quite
detect
that
the
code
tour
or
the
new
code
tour
got
created,
but
you'll
see
right
here
in
my
project.
Now
I
have
a
new
code
tour
project
called
the
upgrade
tour.
A
A
There
you
go,
and
so
what
it
does
right
away
is.
It
starts
by
walking
me
through
this
test,
and
it
says
here
that
there's
43
steps
for
me
to
do
now.
You
might
say
43
steps,
that's
a
lot
of
step.
It
can
actually
get
worse
than
that,
depending
on
how
many
elements
there
are
in
your
solution
and
things
like
that.
This
is
relatively
simple
solution,
but
here's
the
thing
you
don't
have
to
go
through
all
these
steps
manually.
A
A
Okay,
when
the
first
step
is
complete,
there's
a
few
things
you
can
do.
You
can
click
on
the
next
arrow.
Here
you
can
hit
ctrl
right
arrow
and
I'm
a
big
fan
of
shortcut
keys.
So
that's
more
than
likely
what
I'll
do
or
you
can
just
look
at
the
code,
tour
steps
here
and
just
click
on
the
next
step.
So
let's
just
go
on
to
the
next
step.
A
So
next
step
it
does
the
same
thing
it
takes
you
to
where
in
the
project
you
need
to
make
a
change
and
it
gives
you
the
steps
to
do
it.
So,
let's
just
do
that
all
right,
and
now
I
just
need
to
keep
going
through
the
steps
one
by
one
once
you're
done
with
the
upgrade
it
gives
you
a
final
step
that
says:
that's
it
optionally.
You
should
probably
remove
the
tour
file
or
again,
if
you
use
the
markdown
output
or
the
json
input
output,
or
something
like
that.
A
You
just
need
to
delete
the
upgrade
file
because
you
don't
want
to
leave
just
a
boring.
You
know
file
that
serves
no
purpose.
So
I'll
just
say
finish
the
tour.
I
will
go
delete
the
entire
folder
here
for
my
tour
and
that's
it.
I
now
have
a
project
that
is
upgraded
to
the
latest
version
of
spfx
that
I'm
currently
running
on
my
machine
today.
I
showed
you
how
to
use
the
cli
for
microsoft
365
to
upgrade
an
existing
spfx
solution
to
the
most
current
version
on
your
workstation.