►
From YouTube: Community Demo - Using Office 365 CLI for easily updating your SPFx solutions to latest version
Description
This community call demo is taken from the SharePoint Development monthly community call recording on 14th of May 2019. In this video, Stefan Bauer (n8d) demonstrates how to use Office 365 CLI to easily update your existing SharePoint Framework solution to latest version.
Presenter - Stefan Bauer (n8d) - @StfBauer
Full details on the community call from https://developer.microsoft.com/en-us/sharepoint/blogs/sharepoint-dev-community-pnp-may-2019-monthly-community-call-recording/
More details on the Office 365 CLI - https://pnp.github.io/office365-cli/
More details on the PnP SPFx Yeoman generator - https://pnp.github.io/generator-spfx/
More details on the SharePoint dev community calls from http://aka.ms/sppnp.
A
What
I
have
here
is
actually
the
first
project
is
my
first
web
part
that
I
ever
built
was
shovel
framework
so,
and
it
works
really
great
over
the
last
couple
of
months
for
the
customer,
but
recently
in
1.8
extra
we
got
the
team
support,
so
basically
can
run
your
quite
part
in
teams
and
the
custom
of
them
come
to
you
and
say:
hey:
can
you
please
make
it
available
in
teams?
So,
therefore,
this
is
one's,
an
area
that
we
need
to
update
our
or
our
web
part,
so
the
this
project.
A
So
what
I
can
do
now
to
upgrade
this
to
the
1.8
version
is,
for
example,
go
over
here,
go
to
the
release,
notes
go
to
the
first
one
then
apply
the
check
out
what
has
changed
in
1.4,
update
all
the
changes
in
1.4,
1.5
and
so
on,
and
there's
really
complicated
to
follow
the
steps
to
make
it
actually
working
in
1.8,
because
there
are
so
many
changes
and
sometimes
the
schema
changes,
and
sometimes
only
the
package.
References
only
changes.
So
another
approach
is
with
this
project.
A
The
certs
this
can't
be
an
outdated
which
actually
should
bring
me
all
the
packages
that
are
not
up-to-date,
anymore
and
I.
See
here,
the
SBS
build
is
the
current
version
is
the
1.0.1
and
the
latest
one
here
is
the
one
point:
zero
eight
point
two
so
I
can
up
get
go
now
and
upgrade
all
those
packages
in
here,
but
this
is
not
a
guarantee
that
the
web
actually
then
lets
itself
compile
and
runs
everything
because
their
schema
changes
in
the
source
files
that
you
can
do.
A
What
actually
is
an
approach
to
create
this
really
old
project
to
the
1.8
went
to
is
a
tool
that
is
included
in
the
office,
365
CLI,
so
in
general,
when
the
office
365
Scylla
is
somewhat
like
the
powershell.
So
when
you
go
in
here
on
the
on
the
documentation
page,
you
see
here
commands-
and
this
is
for
hey-
I
can
log
in
and
get
files
and
folders
from
sharepoint
online
I
can
connect
to
the
Microsoft
craft.
But
one
specific
part
of
this
office,
365
CLI,
is
the
SPF
X.
A
Then
in
here
we
have
a
command
which
says
project,
and
this
allows
you
to
upgrade
our
project
to
the
very
latest
version.
So
when
we
scroll
down
here,
these
are
all
the
versions
that
came
out
that
was
published
and
these
all
these
versions
have
release
notes
and
some
changes
in
there.
So
I
need
to
go
step
by
step
SAP
to
one
point,
eight
point
one
and
one
more
day,
point
two,
which
is
not
really
a
relative
Pro.
So
what
did
actually
this
this
commands?
Does
it
it?
It
runs,
rules
and
changes.
A
And
when
I
came
now
to
my
wishes,
studio
code
I
see
here
exactly
the
common
lines
to
execute
in
here
to
upgrade
the
project
to
the
latest
version.
This
is
pretty
nice
and
and
I
can
run
the
script
right
away,
but
what
I
also
can
do
is
I
want
to
make
sure
that
what
what
is
in
there
so
I
can
also
change
in
here.
The
output,
let's
say
I,
want
to
do
a
markdown
file
and
export
everything
to
upgrade
dot
nd.
A
A
My
SP
webpart
base
I
need
to
update
the
types
for
the
react,
and
all
these
are
the
findings
from
my
project
and
steps
that
I
need
to
do
in
order
to
upgrade
to
the
latest
version
and
at
the
end,
what
you
actually
see
here
is
a
summary
that
combines
all
these
single
rules.
You
see
here
there's,
for
example,
here
you
see
a
slimmed
config
needs
to
be
modified.
A
A
A
A
A
A
So,
for
example,
let's
check
out
the
URC
file
in
here
the
RC
file.
Actually
I
showed
you
before
I
need
to
change
generator
version
gear
to
1.6
and
I
will
do
this,
for
example,
with
the
package
of
Jason,
so
I
crept.
This
reline
out
here
upgrade
to
the
let's
upgrade
this
package,
the
TS
length,
microsoft,
contribute.
A
A
Actually,
what
we
see
in
here,
the
tears
lint
Microsoft
contribute
is
not
available
in
this
list
anymore.
So
it
gives
you
it's
a
safe
approach
to
upgrade
the
version
and
when
you
are
not
sure,
if
you
have
done
all
the
steps,
you
can
run
this
command
again
and
gives
you
the
find
the
list.
What
steps
you
actually
need
to
do
in
order
to
make
it
really
running
with
one
point.
Eight
point:
two:
that's
one
way
of
using
it.
A
A
In
the
PPS
pfx
generator,
we
need
to
make
sure
that
when
you
create
a
project
which
is
a
version,
one
point
eight
point:
two
that
you're
able
to
embed
there-
the
right
web
part
so
that
you
use
the
version
that
the
right
version
of
the
Shemin
framework
your
project
is
running
on
when
you,
for
example,
at
a
new
web
part.
So
we
use
this
office
365
CLI
in
the
PMP,
as
the
effects
generator
as
well.
A
So
what
we
do
in
the
PMP
s,
VFX
generator,
is
we
use
the
office
365
CLI
in
the
background
and
say
hey,
you
cannot
add
a
webpart
right
now,
because
your
project
needs
to
be
upgraded
and
what
we
do
in
here
is
the
police
review
the
upgrade
lock
and
when
I
go
in
here
and
show
the
upgrade
lock.
This
is
actually
it
says
again
here
the
one
point
eight
point
two,
and
this
is
actually
the
diversion
that
the
GPS
effects
generators
running
on.
A
B
To
be
fair,
Stefan
just
to
be
fully
transparent
and
open
on
messaging,
our
release
notes
do
not
have
a
really
bulletproof
way
of
always
explaining
what
it
updates.
So
from
that
perspective,
using
the
office
365
CLI
is
is
really
really
convenient.
It
is
an
easy
to
later.
It
is
a
cross-platform,
it
works
in
Windows,
Mac
Linux,
and
so
it's
a
great
tool
for
that,
and
it
doesn't
has
logic
inside
of
it.
B
I
used
the
tool
yesterday
to
upgrade
chip
on
starter
kit
from
I
think
it
was
from
1.8
to
1.8
and
obviously
that
the
level
of
a
steps
which
needs
to
be
done
was
significantly
smaller.
In
this
case,
the
scenario
is
quite
hectic
from
one
point:
zero.
Two
to
one
point
eight
point:
two:
now
before
we
actually
to
the
Q&A
and
back
on
the
slice,
can
you
scroll
down
all
the
way
down?
B
If
you
can
find
the
summary
section,
because
it's
very
important
to
realize
that
there's
a
combined
commands
here
excellent,
so
don't
have
to
execute
the
NPM
install
commands
for
every
single
packets
one
by
one
and
that's
a
very
important
to
realize.
So
there
is
a
summary
of
things.
What
you
need
to
actually
do
in
the
end
in
this
case
again,
because
we
are
creating
from
one
point
zero
to
one
point
n,
but
two,
which
is
a
15
versions.
B
But
they
say
a
combined
set
of
commands
which,
which
again
then
has
taken
reuse
and
executes
that's
directly
in
the
project
to
upgrade
under
on
the
right
version.
Any
questions,
there's
a
lot
of
comments
related
on
super
helpful,
very
helpful
on
the
on
Windows
any
comments
related
on
questions
Oh
from
Charlie
Charlie.
B
So
it
would
actually
want
to
go
back
in
time
to
one
point
for
version
and
you
created
something
one
day
too,
because
that
doesn't
work
that
one
on
there's
a
quick
question:
can
we
all
create
SharePoint
2016,
slash
upon
2019
project
using
CLI?
You
can
upgrade
to
SharePoint
Online?
Yes,
no,
you
cannot
use
there's!
B
No
specific
versions
with
SharePoint
framework
solutions
which
are
specific
versions
of
SharePoint
framework
supported
in
SharePoint,
2016
or
2019,
so
you
can
cannot
create
a
SharePoint
2016
version
and
then
I'll
create
that
to
a
newer
version
with
the
CLI
and
then
assume
that
that
would
work
and
show
up
on
2016.
That
is
not
the
case.
So
when
you're,
when
you're
targeting
Chevonne
2016
2019,
you
cannot
upgrade
to
a
later
version.
The
solution,
a
yeoman
generator,
will
scoff
all
tier
two
right
versions
which
are
optimized
for
the
photos,
on-premises
and
ones.