►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 8th of November. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
Live preview on Microsoft Teams tab development with SharePoint Framework, which at the time of the call was not yet available, but has been now released to preview as part of the SPFx 1.7 release.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
Demos:
- Vesa Juvonen – Building Microsoft Teams tabs using SharePoint Framework
- Stefan Bauer – SharePoint Framework solution scaffolding with Angular Elements support using PnP SPFx Yeoman templates
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Hello,
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group
bi-weekly:
sync,
it
is
November
8,
2018
and
we've
got
another
great
meeting
here
for
you
today
for
folks
that
might
be
new
to
the
call
or
new
to
watching
the
recordings.
We
always
like
to
talk
a
little
bit
about
what
these
are
all
about.
So
these
calls
are
part
of
the
larger
SharePoint
patterns
and
practices
program
and
we've
started.
A
These
special
interest
group
calls
so
we
could
provide
a
little
bit
deeper
focus
on
certain
topic
areas,
because
we
had
a
single
monthly
community
call
that
we
just
had
too
much
stuff
to
cover.
You
know
across
all
of
the
the
work
we're
doing
in
patterns
and
practices
to
fit
it
all
into
a
single
call.
So
we've
started
these
bi-weekly
community
calls.
We
have
this
one,
which
is
focused
very
much
on
SharePoint
framework
and
client
side
development
patterns
associated
with
that
and
as
well.
A
The
pn
pjs
libraries,
the
office,
365
CLI,
the
SPF
x,
reusable
controls
and
something
not
new.
It's
been
worked
on
now
for
a
few
months,
but
new
to
this
call
that
we're
going
to
be
bringing
in
and
talking
about
on,
each
call
is
the
new
SPF
x,
community,
yeoman
generator,
and
so
this
is
something
Stephan
is,
hopefully
gonna
be
doing
a
great
demo
on
a
little
bit
later
on.
A
This
call
pending
some
device
issues,
but
this
is
a
it's
it's
an
extension
of
the
out-of-the-box
SharePoint
framework,
yeoman
generator
that
provides
a
few
more
options
and
some
some
different
capabilities
than
the
out-of-the-box
one.
But
it's
it's
an
extension,
so
you're
gonna
get
a
valid
SharePoint
framework
project
out
of
that.
But
it's
a
very
cool
thing
and
we'll
talk
more
about
that
later
on
the
call,
so
we
hopefully
will
have
the
demo
and
a
bigger
discussion
around
that.
A
So
a
very
cool
thing
definitely
worth
checking
out,
especially
if
you're
looking
for
some
capabilities
that
might
not
be
in
the
out-of-the-box
SharePoint
framework,
yeoman
generator.
So
two
legs
down:
there's
Bob,
aka,
MSSP,
PNP
community,
we'll
take
you
to
the
Microsoft
tech
community.
Take
you
to
the
SharePoint
area
of
the
tech
community
there
and
that
will
it's
a
great
place
to
ask
general
questions.
How
would
I?
How
would
you
architect
things
that
might
not
necessarily
be
specifically
related
to
a
given
library
or
a
given
project,
but
is
something
that
you
would
ask?
A
A
The
agenda
for
today's
call
engineering
update
on
SharePoint
framework,
we'll
do
our
patterns
and
practices
updates
and
then
as
well.
We've
got
the
demo
from
stuff
on
on
the
SPO
FX
community
yeoman
generator
that
I
was
mentioning
before,
and
we
will
keep
that.
Hopefully
I'm
not
seeing
him
back
on
the
call,
so
we're
fighting
some
audio
issues
on
his
own,
so
hopefully
he'll
be
back
for
that,
and
then
I'll
have
a
little
bit
of
time.
A
I
think
today,
at
the
end
for
Q&A,
so
always
before
we
get
into
things
like
to
talk
about
opportunities
for
all
of
you
in
the
community
to
get
involved
in
the
SharePoint
framework
in
the
JavaScript
special
interest
group.
The
first
two
are
demos,
so
demoing
a
SharePoint
framework
solution
demo
in
any
of
the
at
PNP
resources
in
an
app
ocation
in
SharePoint
framework
or
without,
and
that
includes
the
CLI,
of
course,
the
PNP
GS
libraries,
the
the
new
yeoman
generator.
A
We
will
do
our
best
to
find
you
a
slot
in
an
upcoming
call.
It
might
not
always
be
the
the
immediately
next
call,
for
example,
but
we'll
do
our
absolute
best
get
you
signed
up,
get
you
a
slot
and
get
you
an
opportunity
to
demo
your
work.
So
very
much
encourage
you
to
do
that.
We
welcome
those
demos,
I
think
they're
super
valuable
for
all
of
us
to
see
the
other
ways
to
get
involved.
A
You
can
always
contribute
on
github
across
any
of
our
projects
that
we
mentioned
here,
all
of
which
are
accepting
pull
requests
are
accepting.
Obviously,
the
reporting
of
issues
and
those
things
really
help
improve
stuff
and
make
it
better
for
all
of
us
in
the
community,
make
it
better
for
everybody
in
the
community.
So
those
contributions
are
very
welcome
and
very
valuable
and
very
much
appreciated,
so
keep
those
coming.
A
We've
across
everything,
seen
a
big
uptick
in
the
last
couple
of
months
on
contributions
from
folks
out
there
in
the
community
and
that's
really
outstanding,
because
it
gets
improvements
in
and
develops
new
capabilities.
Much
faster
than
you
know.
The
folks
in
the
core
team
can
necessarily
get
it's
doing.
Everything
that
you
know,
even
we
might
want
to
do
or
think
is
a
great
idea.
A
You
know
that
feedback
is
always
welcome.
It's
something
we
take
to
heart.
We
do
discuss.
We
do
our
best
to
adjust
and
improve
again
it's
not
something.
We
could
always
react
immediately.
So
if
you
don't
see
a
change,
as
you
know
soon,
as
you
report
the
feedback
trust
me,
we
do
listen
to
it.
We
do
take
it
to
heart,
we
do
take
it
back
and
discuss
it
and
do
our
best,
even
if
change
sometimes
is
slower
than
would
be
ideal.
So
with
that
I
will
hand
things
over
to
vae.
B
I'll,
just
gonna
check
the
presentation
on
here
and,
let's
actually
load
here
so
cool
slide,
which
I
always
do
so.
First
of
all
repeating
the
the
classic
slide,
so
obviously
akms
SP
dev,
dev
Docs.
Actually
in
October,
we
were
in
960,000,
so
I
didn't
update
the
view,
so
we're
pretty
close
on
hitting
the
1
million
marker
marker
in
shape
on
dev
documentation,
which
seems
to
indicate
that
people
are
finding
that
location
useful,
which
is
always
good.
But
if
something
is
missing,
please
let
us
know
if
you
need
to
have
additional
guidance
on
something.
B
Please
let
us
know,
because
your
input
truly
matters
here,
we're
not
gonna.
Take
we're
not
gonna
write
any
documentation
which
is
not
meaningful,
because
every
single
piece
of
documentation
requires
also
maintenance
and
that's
maintenance.
So
we're
always
then
increasing
our
workload.
So
please
please,
please.
If
something
is
missing.
Let
us
know
now.
The
second
thing,
what
I
wanted
to
remind
everybody
is
take
MSSP,
dev,
active
issues
so,
if
you're
running
into
their
issues,
API
issue
functionality
issue.
B
Please
use
this
to
report
to
issue
and
for
us
we
right
now
have
a
support
personnel
who
are
doing
the
initial
triage
and
then,
if
it's
a
critical
critical
issue,
they
will
flag
that
right
away.
We
are
falling
significantly
behind
of
doing
a
active
triage
on
this,
mainly
actually
because
we
are
looking
into
shipping
SharePoint
framework
1.7
question,
so
we've
been
kind
of
a
prioritizing
the
delivery
of
1.7
on
top
of
the
issues
and-
and
that's
that's
a
hard
call,
but
it's
also
related
on
the
fact
that
there
isn't
well.
B
We
need
to
prioritize
our
time
as
well
now,
let's
actually
quick,
update
and
reminder
if
you're
an
MVP
if
you're
looking
into
a
meeting
or
if
you
want
to
have
additional
visibility.
True,
for
example,
the
sharepoint
twitter
channel,
we
test
220,000
followers.
Please
please.
Please
use
this
opportunity
of
of
submitting
a
suggestion
for
the
having
a
PM
MVP
article
in
the
sharepoint,
dev,
blog
and
and
there.
If
you
go
to
the
sharepoint
dev
blog,
you
can
actually
find
an
article
which
will
explain
the
process.
B
So
please
send
us
an
email
with
a
suggested
content,
so
we
can
actually
see
if
we
get
it
out
or
not
from
there
or
not.
Now,
on
the
sharepoint
framework
usage
sharepoint
framework
usage
suggests
a
kind
of
a
small
update
on
this
one.
So
this
is
the
latest
charts.
It
includes
yesterday's
usage
and
we
did
a
all
time
record
once
again
on
Monday.
So
we
keep
on
breaking
the
record
on
every
single
Monday
around
the
all
around
the
users
using
third-party
custom
web
parts
or
extensions
in
SharePoint
Online.
B
So
basically
this
Monday
we
once
again
today
all-time
record.
We
have
now
crew
four
hundred
four
hundred
and
forty
nine
percent
since
the
start
of
this
year
and
year-over-year
growth
is
four
hundred
and
eighty
one
percent.
So
it's
a
pretty
insane
growth,
especially
considering
that
already
year
ago,
at
this
moment,
SharePoint
framework
past
SharePoint
Adams
in
SharePoint
Online
on
the
usage,
so
we've
kind
of
a
we're
by
far
the
number
one
customization
model
in
the
whole
office
365
with
SharePoint
framework.
So
if
you're
kind
of
a
considering
are
people
actually
writing
new
stuff
on
this?
B
Oh
yes,
they
are,
and
we
can
see
that
massive
uptake,
also
during
this
autumn,
we're
which
potentially
is
related
on
people
accepting
the
realities
of
okay
shape
and
framework
is
the
future
after
SBC
owners
on
spring
and
then
ignite
further
in
encouraging,
where
we're
heading
with
SharePoint
framework.
So
we
in
engineering
we
build
all
of
our
stuff
using
SharePoint
framework,
so
it's
pretty
safe
to
bet
on
SharePoint
framework,
because
the
whole
SharePoint
Online
is
built
using
SharePoint
framework.
So
you
get
the
same
tooling
same
from
generally
the
same
package
for
you
as
well.
B
B
The
estimate
on
this
one
so
we're
looking
into
all
girls,
are
getting
1.7
out
early
on
before
the
holiday
season
starts
in
u.s.,
which
starts
in
Thanksgiving
and
and
so
that
there's
plenty
of
time
for
people
to
give
us
feedback,
because
there's
quite
a
few
items
on
the
dev
preview
and
we've
been
already
in
this
course.
We
demonstrated
the
domain
as
a
let
it
wait
part
roughly.
We
also
demonstrated
the
probably
hosted
solutions
and
ad
pages
actually
in
this
course.
B
What
our
list
subscriptions-
it's
it's
basically,
your
web
part
or
an
extension,
can
say
that
I'm
interested
on
events
on
a
single
list.
So
whenever
there's
a
new
item
or
an
item
is
changed
in
the
list,
your
web
part
or
an
extension
will
be
notified.
So
basically,
you
can
subscribe
on
live
events
on
the
list,
so
it's
basically
socket
IO,
but
using
our
terminology
under
now,
but
on
the
on
the
team's
development
and
really
before
I
go
to
the
actual
demo.
Let
me
let
me
explain
what
the
why
we
are
doing
this.
B
So
obviously
you
saw
the
the
success
of
SharePoint
framework,
so
we
can
see
a
massive
uptake
on
the
adoption
of
sharepoint
framework,
which
is
great
a
lot
of
our
customers
and
enterprise
customers
are
using
it
and
that
their
users
is
growing
all
the
time.
So
obviously
the
mix
of
teams
is
that
one
area
of
the
cooperation
platform
in
office
365
and
one
of
the
key
challenges-
Microsoft
aims
platform
have
been
have
or
have
been
have
been.
B
The
fact
that
if
you
write
in
a
Microsoft
themes
tab
you
need
to
figure
out
whether
you
host
it
and
how
do
you
control
the
permissions
and
manage
everything
every
every
single
aspect
of
that
application?
First
sure,
if
you
have
access
to
National
subscription,
you
can
easily
create
a
as
your
application
and
then
you
can
manage
the
permissions
using
Azure
ad,
but
that's
really
easy,
potentially
as
a
developer,
but
that's
not
actually
super
easy
for
enterprise
scale
or
in
an
enterprise
level.
B
So
if
I
would
actually
go
to,
let's
say
a
random
oil
company
in
Netherlands
and
say
hey,
can
you
give
me
access
on
your
sure,
subscription
I
need
to
create
an
application.
I
don't
need
to
manage
your
azure
ad
dancer
would
be
obviously
no
and
I
would
have
to
justify
the
tasks.
I
would
have
to
explain
to
ask,
and
what
does
it
mean,
and
there
would
be
months
and
months
of
evaluation?
Will
they
accept
that
or
not
so
we
want
to
simplify.
B
B
From
behalf
of
you,
for
example,
under
Asha
ad
permission
management
through
SharePoint
framework,
all
of
that
stuff,
without
the
requirement
of
actually
going
to
touch
ID
and
getting
the
the
web
application
and
hosting
or
sorted
out
and
all
of
the
additional
things
and
and
all
the
costs
related
on
hosting
and
all
of
that.
Well,
let's
actually
use
the
SharePoint,
because
if
you
have
Microsoft,
teen
didn't
have
a
sharepoint
online
as
well,
even
though
you
would
have
been
using
that
necessarily
well.
B
Typically,
people
are
so,
let's
actually
utilize
the
existing
costs
and
the
more
of
what
you
have
without
any
additional
requirements,
and
this
is
really
I
would
say.
This
will
enable
normal
developers
really
truly
start
designing
applications
which
are
then
can
be
surfaced
either
as
a
ship
on
framework
webparts
or
as
a
tabs
and
max
of
themes,
and
this
is
really
really
cool
now,
because
and
quickly
coming
out.
Stefan
Mallos
question
related
on
the
on
the
workbench.
B
So
technically,
what
you're
building
is
a
web
part,
and
let
me
show
this
one
in
practice,
so
let
me
actually
jump
on
my
screen
and
hopefully
screen
sharing
and
everything
works,
so
I'm
sharing
this
monitor.
Yes,
so
let's
say
somebody
needs
to
confirm
when
you
get
the
screen-
and
this
is
I'm
gonna-
explain
what
it
is
actually
confirmed.
B
A
B
Thank
You
Patrick,
so
what
I'm
done
here?
I
haven't
done
anything
more
than
I
just
wanted
to
save
time
on
the
scaffolding.
So
what
I'm
actually
done
here
is
that
I've
scuffled
a
web
part,
so
I've
scuffled
a
SharePoint
framework,
quick
part
which
is
a
standard
wake
Bert.
It
actually
has
two
welcome
to
SharePoint
message
and
everything
else
there
when
I
run
this
in
human.
B
Let
me
actually
get
in
here.
So
let
me
do
em
D
test
CD
test,
yo
Microsoft
SharePoint.
So
what
I
actually
selected
in
the?
Let
me
zoom
just
slightly
so
you
can
see
it
done,
but
whenever
the
yeoman
actually
executes
come
on,
come
on,
come
on
run,
don't
you
there
we
go
so,
and
the
only
thing
but
I
actually
did
here
is
basically
I
targeted
sharepoint
online
and
unjust
to
be
through
super
clear.
I'm
running
one
point,
seven
version
which
is
not
yet
available.
B
You
can't
you
can't
see
anything
yet
you
can't
get
this
to
your
environment,
yet
it's
worker
relations.
This
is
the
new
choice
of
the
environment,
so
I
can
obviously
kind
of
target
happened
online
because
just
this
preview
of
the
touchdevelop
in
Japan
or
in
office,
365
I'm
going
to
use
current
folder
and
then
what
I'm
saying
is
that
I'm
gonna
use
that
ten
and
wide
deployment?
That's
easy,
sup
the
setup
and
no
domain
isolation.
And
we
are
creating
a
bed
part
and
let's
call
that
something
and
description.
And
then
it's
a
no
JavaScript
framework.
B
So
there
is
no
option
in
the
Yeomen
which
you
would
say.
No,
no
I
want
this
functionality
to
be
target
teams,
because
we
don't
actually
have
to
isolate
that.
We
can
use
the
exact
same
piece
of
code
as
a
web
part
or
as
Microsoft
teams
tab
and
that's
the
beauty
of
the
thing
so
because
in
in
general,
when
you
think
about
teams,
when
do
people
actually
use
teams,
let
me
actually
close
that
one
we're
one
who,
as
there
are
people
who
use
teams
and
then
there's
people
who
prefer
ship
one.
B
So,
basically,
our
our
kind
of
a
messaging
from
our
side
from
Microsoft
side
is
that
well,
if
the
team's
is
more
suitable
for
use,
use
teams
and
then
surface
debate
is
and
everything
else
in
the
team
signed
asset
apps
if
the
SharePoint
feels
suitable
for
you,
if
you're
a
larger
customer,
you
want
to
have
a
portal.
Yes,
please
use
a
communication
side
and
build
your
porters
using
communication
sign.
The
beautiful
asks
as
a
developer
is
that
you
use
the
exact
same
piece
of
code.
B
I
asked
you
surface
or
functionality
in
either
side
of
the
of
the
game,
so
either
in
teams
or
either
as
a
sharepoint
web.
So
it
is
right
now.
Well
the
base
classes
and
everything
else
is
a
web
part.
So
I
haven't
done
any
modifications
in
here.
What
I'm
gonna
do
is
that
I'm
gonna
make
this
aware
of
the
context,
so
I'm
gonna
do
small
modifications
and
this
all
will
is
gonna,
be
in
the
hands-on
labs
which
what
we
relate
together
with
a
a
1.7,
so
I'm
gonna,
add
a
a
on
in
it
on
init
method.
B
Here,
where
I'm.
Actually,
then,
using
the
this
context,
Mike's
of
teams
get
context.
So
if
you
ever
implemented
anything
on
Mike's
of
teams,
this
is
how
you
figure
out
the
context
of
the
tab.
What
I'm
doing
here
is
just
basically
storing,
then
that
context
in
the
team's
Congress
property
and
then
II
I'm
gonna,
implement,
which
is
kind
of
letting
us
know
in
my
being
rendered
either
in
teams
or
am
I
reading,
am
I
rendered
in
the
SharePoint
site.
B
So
here
if
the
team's
context
has
been
set,
we
know
that
we're
in
teams,
if
the
team's
context
has
not
been
set,
we're
in
SharePoint
so
and
then
we're
gonna
modify
the
Welcome
message
based
on
that
and
that's
it
basically,
that's
it
for
the
the
code
and
technically,
the
exit
out
of
the
box
piece
of
code
would
work
as
such
as
a
team
stamp
as
well.
So
what
I'm
gonna
do
is
that
I'm
going
to
actually
jump?
Let's
save
the
changes.
B
First,
I
always
forget
about
doing
that,
and
then
I
wonder
where
am
I
not
saying
any
changes.
I'm,
not
gonna,
do
any
any
debugging
exercises
in
here.
Let
me
actually
open
up
a
terminal
here
and
let
me
actually
back
it's
this
one.
So
there
we
go.
Let's
do
call
up
bundle,
that's
the
ship,
bum-bum-bum
papa
papa
and
that
shouldn't
take
too
long,
but
you
can
hear
me
singing
while
we
wait
the
coop
and
all
to
share
to
do
it.
Sharp.
B
Well,
that
went
really
well,
oh
yeah.
That
makes
a
lot
of
sense
because
my
stylings
are
now
I
basically
could
be
pasted
the
code
from
the
from
the
tutorial
and
the
name
of
the
style
is
different.
So
let's
actually
fix
that.
That's
a
fair
point!
That's
a
wanna
me
see.
I
I
can
still
code
I'm,
not
just
a
a
PowerPoint
p.m.
B
B
And
then,
let's
get
back
on
some
of
the
questions
slightly
later
so
I
don't
actually
lose
the
flu
stem
and
then
because
I
want
to
actually
work
through
the
whole
process.
So
you
understand
how
it's
then
being
exposed.
What
I'm
gonna
do
now
is
the
Bob
where's,
the
packet
in
the
solution
and
I'm
gonna
do
the
the
shape
so
I,
don't
have
to
worry
about
running
the
localhost
or,
and
everything
will
be
packaged
automatically
to
Adolphus,
resist
for
CDN
or
served
automatically
from
office
resist
five
and
that's
it
now.
B
We
are
ready
to
go
and
let
me
actually
make
sure
that
this
one
is
working
so
I'm
gonna.
It's
actually
hide
that
left
navigation.
There
we
go.
So
let
me
go
to
the
SharePoint
folder
SharePoint
solution.
There's
my
team
step
seek
ASB
ASB,
FX
and
now
what
I'm
gonna
do
is
that
I'm
going
to
jump
to
the
context
of
the
talent
and
let's
actually
test
that
web
part.
B
So,
let's
test
the
fair
part,
first
in
a
ship
one
side
and
let's
put
the
same
web
part
to
work
then
in
in
the
teams
and
I'll,
show
you
the
process
how
to
make
that
happen.
It's
it
insanely
super
easy.
So,
first
of
all
this
was
a
tenant
wide
deployment
and
there
are
considerations.
Do
you
want
it
to
be
a
tenant,
wide
deployment
or
not?
If
you
put
it
as
a
tenant
wide
deployment,
it
means
that
the
web
part
is
automatically
and
all
of
the
available
in
all
of
the
SharePoint
sites.
B
If
you
don't
want,
if
you
don't
want
that,
you
could
actually
hide
this
web
part
to
be
only
visible
in
that
particular
team's
team
teams.
Aztap,
if
you
want
to
do
that,
so
there
are
options
of
kind
of
a
scoping.
The
visibility
of
the
web
part
absolutely
what
we
have
in
the
SharePoint
framework
as
well.
Now,
that's
now
done
so
that's
being
deployed,
so
let
me
actually
create
a
page
here,
so
we
can
test
that
it's
working
properly
random
site
in
my
tenant.
B
It
was
at
my
deployed
web
port,
so
it
should
be
visible
here
if
I
write
something
related
and
seek
it's.
My
call
team
sick
demo,
so
it's
aware
it
works.
It
uses
use
the
asset
packaging.
I
packets,
all
of
the
JavaScript
files
inside
of
the
APK
chief.
Well,
I,
don't
have
to
worry
about
hosting
I,
don't
have
to
worry
about
deployment,
it
works
as
a
web
part.
Okay,
that's
wet
for
what
about
teams,
so
how
do
I
actually
get
this
one
in
teams?
B
So
let
me
get
back
on
the
on
the
file
system
and
I
will
actually
let
me
get
back
on
the
first
on
the
visual
studio
code
sight
and
let
me
extend
the
teams
folder,
so
pi
default
when
you
scaffold
a
webpart
starting
from
1.7
version.
We
actually
also
give
you
a
manifest
file,
which
we
set
the
configurations
and
everything
else
automatically
based
on
the
web
part
you
are
using
so
in
here,
and
this
is
a
typical
team's
manifest
file.
It
references
a
certain
images
which
we
need
to
double
check.
B
There's
apparently,
a
new
way
of
associating
echo
icons
in
teams
which
we
missed
and
it
sets
all
of
the
goods
and
everything
else
accordingly,
based
on
the
solution,
what
you're
doing
so,
you
don't
actually
have
to
worry
about.
What's
in
the
manifest
file,
it's
a
complex
file,
but
you're
basically
ready
to
go
as
long
as
you
deploy
your
team's
manifest
to
the
team.
So
let's
actually
do
that
so
I'm
gonna
go
to
the
team's
folder
I
can
see.
The
image
is
I
can
say
the
manifest
lets
me
actually
create
a
zip
file.
B
So
let's
call
this
my
supercool
team's
tap
dot
C,
so
I'm
gonna
copy
the
path.
I'm
gonna
go
to
my
SharePoint
in
the
team's.
What
I've
done
already
and
the
dis
will
be
obviously
explained
in
the
documentation,
I
enable
site
loading,
and
that
means
that
I
can
actually
go
to
a
specific
team
site
and
I
can
upload
the
application
or
customization
in
the
specific
team.
Well,
not
a
team
site
specific
team.
In
this
case
it
were
using
max
of
teams,
and
the
team
name
is
team,
which
is
slightly
confusing.
B
But
anyway
you
can
see
it
in
team.
I
have
plenty
of
other
teams
here
as
well,
but
I'm
just
using
this
one
for
demonstration
our
purposes.
Now,
if
you
would
like
to
have
that
this
tab
visible
to
cross
every
single
team
in
your
team's
installation,
you
can
actually
upload
that
to
the
catalog
here
as
well,
so
in
the
store
in
the
more
apps,
and
you
can
upload
that
to
be
catalog
and
then
the
web
part.
Sorry
not
a
web
part.
B
So
you
can
actually
see
those
gears
in
here
and
it's
just
to
indicate
that
it's
a
in
development
app.
So
now
my
cool
teams,
sick
demo,
is
the
application
and
let's
go
to
the
teams.
Let's
actually
add
my
our
application.
We
can
see
it
was
my
cool
teams.
Second
demo,
it's
actually
at
that
one
on
the
on
the
asset
tap
on
that
teams,
because
now
it's
available
in
the
context
there's
my
description
field
I
can
parameter
side
in
the
same
way
as
you
can
parameter
side
wet
parts
in
the.
B
In
our
case,
we
used
our
at
the
Box
wet
part
and
that's
it
I'm
gonna
click
Save,
so
I'm
not
gonna,
actually
change
the
parameter
station
and
voila
poof.
There's
my
custom
team
available
in
the
team's
UI
and
it
works
like
a
team's.
It
works
like
a
wet
part
or
a
SharePoint
rate
card.
It
looks
exactly
like
the
web
part
accepted
based
on
our
code,
we're
rendering
and
different
output
in
the
SharePoint
site.
We
said
welcome
to
SharePoint
and
into
the
team
site.
B
We're
saying
welcome
to
teams-
and
this
was
because
we
actually
had
this
logic
here-
that
if
we
are
in
teams
context,
we're
saying
welcome
to
teams
if
we
are
in
SharePoint
Congress
were
saying:
welcome
to
ship,
but
what's
really
cool
when
I
think
of
it.
I
didn't
actually
write
any
specific
code
for
teams.
I
just
took
advantage
of
the
hosting
deployment
mechanisms
of
SharePoint
the
tenon
by
deployment.
That's
it
and
that's
basically
available
for
anybody.
If
I
want
in
the
into
implementation
now,
Russell
has
a
question.
B
So
does
the
web
part
in
the
team's
have
access
to
on
the
lists
in
the
associate
side?
Answer
is
yes,
so,
if
needed,
this
web
part
could
also
take
advantage
of
saving,
for
example,
data
in
the
context
of
that
team,
because
every
single
team
will
actually
see
that.
So
let
me
go
here:
every
single
team
has
a
SharePoint
site
behind
of
it,
so
basically
that
the
web
part
it
being
rendered
in
the
context
of
the
team
in
the
show,
in
the
context
of
this
particular
SharePoint
site
behind
off
the
team.
B
Now
technically
the
end
users,
don't
necessarily
even
never
need
to
go
to
this
side,
but
this
is
the
same
side
which
we
use
if
you
upload
files,
the
mics
of
themes.
This
is
basically
the
information.
What
is
coming
from
that
side,
so
your
web
part
can
take
advantage
of
this.
Can
I
can
I
get
access
on
mics
of
craft?
Absolutely
you
can
can
I
can
I.
Do
a
call
third-party
web
api
switch
with
released
in
SharePoint
framework
1.6.
Absolutely
you
can
anything.
B
What
we
have
in
SharePoint
framework
is
available
in
this
context
as
well,
because
technically,
what
we're
seeing
here
is
the
same
webparts
same
implementation
rendered
in
the
context
of
the
SharePoint
site
behind
of
the
team,
so
we're
basically
just
and
I
framing
that
web
part
dynamically
to
be
visible
in
the
team,
and
now
it's
up
to
you
what
the
web
part
actually
does.
So
this
particular
web
part
is
relatively
simple
and
it's
it's
relatively
well
basic.
Now
I
was
waiting
somebody
to
jump
on
the
on
the
font
issue.
B
So
at
the
font
and
the
we
there
is
a
small,
let's
say,
a
bug
related
on
the
phones
when
we
start
in
dev
preview,
which
says
that
we
do
not
load
the
office,
you
have
fabric
phones
in
this
host
page,
which
means
that
this
looks
slightly
different.
Then
it
looks
and
in
the
SharePoint
context,
but
you
can
actually
easily
fix
that
we're
looking
into
loading
those
phones
properly
in
this
page
as
soon
as
possible.
So
super
small
thing:
why
is
it
green?
B
How
did
the
cocoa
tree
if
I
go
to
this
theme
site,
which
was
behind
of
the
theme?
The
theme
of
this
theme
side
is
actually
clean,
so
basically,
as
I
didn't
set
any
as
any
theme
settings
to
my
web
part,
it
basically
inherited
the
theme
from
this
particular
SharePoint
site,
which
is
behind
off
the
team,
and
that's
why
it's
green
so
now,
if
I
actually
would
go
and
change
this
one
to
use
an
alternative
theme
by
default,
it
would
flip
the
color
in
here
now.
Do
you
want
that
to
happen?
B
That's
a
different
thing
and
we
want
to
have
a
specific
colors.
Yes,
you
can
easily
do
that
as
well,
but
as
I
didn't
change,
anything
in
a
code
I'm,
basically
using
exactly
the
same
code
as
start
of
the
books,
web
/
creation
except
I'm,
just
aware
of
the
context
it's
gonna
actually
use
by
default.
The
themes
which
are
available
now,
like
I,
said
this
is
as
part
of
the
1.7.
This
will
be
in
the
1.7
beta
version,
so
plus
beta
one
point,
seven
plus
beta,
because
this
is
in
Def
previous
status.
B
So
this
is
not
ready
for
production.
Yet
we
want
to
get
your
feedback
for
it
before
we
actually
ship
the
g8
as
the
way
of
creating
tabs
in
the
Microsoft
themes,
but
it
really
simplifies
the
model.
Yes
beta.
It
really
really
simplifies
the
model
of
creating
tab
custom
based
customizations
in
the
teams,
and
if
your
users
prefer
to
use
teams,
they
can
still
access
your
business
lots
of
business
applications
and
web
parts,
which
are
then
exposed
basically
as
a
team
as
a
team
tab.
B
So
we
use
to
SharePoint
framework
which
after
this
we'll
go
chie,
we
might
want
to
consider
renaming
SharePoint
framework
as
a
office,
365
framework
or
something
else,
and
then
and
then
we
use
the
same
framework
for
surfacing
the
same
business
logic
in
the
two
different
location
based
on
your
own
preference
and
that's
insanely,
cool
right
now,
and
maybe
a
1ws
with
one
additional
note
on
that.
So
right
now
we
started
the
collaboration
with
teams.
B
People
and
themes
is
the
first
one
which
is
adapting
the
shipment
framework
of
doing
SharePoint
framework
way
of
doing
things,
we're
looking
into
and
having
constant
discussions
with
other
teams
as
well.
So
because
we
want
to
make
the
deployment
and
hosting
and
everything
else,
super
easy
for
anybody
who
wants
to
just
concentrate
on
their
customization
and
especially
in
the
context
of
office
365
there
so
a
shape
or
a
pond
underneath.
So
why?
Wouldn't
we
take
advantage
of
this
implementation?
So
the
office
settings
bubble
is
mentioned
in
the
office.
B
Sorry
outlook,
add-ins
or
office
add-ins
we're
looking
into
potentially
going
that
direction
as
well
in
the
future.
It's
a
logical
discussion
point
now
when
and
has
it
been
decided,
it
has
not
yet
been
decided
and
it's
constant.
It's
a
ongoing
discussion.
How
does
it
happen,
but
looking
how
simple
it
is
to
implement
teams
tab
most
likely
will
do
the
same
for
the
additional
services
as
well.
B
Cool
and
I
don't
want
to
take
more
time,
because
we
want
to
make
sure
that
Stefan
has
time
for
his
content.
So
let's
actually
get
back
on
the
slides.
I
will
answer
the
the
ongoing
questions
if
I,
if
I,
can
keep
up
with
them,
so
I'm
gonna,
flip
back
on
the
slides
and
I
think
we're
I'm
handing
it
over
to
you
Patrick
unless
I'm
mistaken.
B
B
A
So
quick
updates
before
we
get
to
the
demo,
so
PMP
j/s
client
library
updates,
so
we
released
one
two
four
on
November
2nd,
which
I
believe
was
last
Friday.
I
just
wanted
to
say
again
thank
you
and
great
work
by
the
community.
This
is
our
largest
community
contributed
release,
that's
probably
an
awkward
way
to
say
it,
but
we
had
the
most
community
contributions
in
any
release
ever
for
the
library.
So
that's
really
fantastic
and
it's
really
exciting
to
see
that
continue
to
grow.
It
wouldn't,
of
course,
encourage
all
of
you.
A
If
you're
interested,
please
do
contribute.
It
really
makes
things
expand
and
get
better
a
lot
faster
than
relying
necessarily
on
the
core
team
to
get
everything
done.
Some
of
the
highlights
we've
updated
the
eight
old
client
internally
to
when
you
use
the
Adel
client
within
SharePoint
framework,
1.6
we're
now
going
to
use
the
new
SharePoint
framework
1.6
a
the
token
provider,
the
big
advantage.
There
is
no
more
pop-ups.
So
this
was
we
got
some
feedback
around.
A
Would
it
be
great
if
we
could
get
rid
of
the
popups
and
help
with
the
authentication
experience
and
we've
done
that?
So
if
you're
in
SharePoint
framework
1.6,
we
now
take
advantage
of
that
new
capability
and
it
really
is
a
much
smoother
experience,
so
great
work
by
the
product
team
there
and
we
were
able
to
just
sort
of
piggyback
on
that
work
and
it
of
our
stuff,
if
you're
not
in
SharePoint
framework
1.6
that
won't
work.
Obviously,
but
you
have
the
other
capabilities
are
still
available
for
you.
A
You
can
create
your
own
client
with
your
own
ID
and
secret,
and
these
sorts
of
things
will
still
work,
but
you
will
still
have
popups
and
that's
it's
honestly,
just
an
architectural
problem.
We
as
PNP
can't
deploy
the
same
kind
of
things.
The
folks
from
the
product
team
can
to
the
servers
to
enable
these
kind
of
populist
scenarios
so
would
encourage
you
to
upgrade
and
use
SharePoint
framework
1.6.
If
you
have
a
need
to
call
the
graph,
for
example,
or
to
call
SharePoint
or
to
crawl
call
other
resources
with
an
aad
authentication
token.
A
It's
a
great
new
capabilities.
So
I
want
to
highlight
that
as
well.
We
have
support
now
for
site,
designs
and
site
scripts,
so
applying
those
which
is
really
exciting
to
see.
We've
got
some
great
feedback
around
number
one
graph,
batching
being
broken
and
then
number
two
some
ways
we
could
improve
it
once
it
was
working
so
appreciate
that
feedback
we
are
able
to
act
on
that
last
month.
We've
also
expanded
some
of
the
graph
capabilities.
A
I
really
try
to
get
it,
but
if
you
have
contributed
and
you're
not
in
the
authors
file,
please
let
me
know
it's
an
oversight
on
my
part
and
I
apologize
for
that,
but
it
has
happened
and
want
to
make
sure
it's
not
happening.
So,
just
let
me
know
it's
it's
a
Miss
on
my
part:
it's
not
a
purposeful,
not
inclusion
of
you
right
or
something
like
that.
So
please,
just
let
me
know
we'll
get
to
add
it
in
there
no
big
deal
and
then
sew
links
down
there
at
the
bottom.
A
The
first
one
there,
the
PNP
github
dot
is
such
keen
pjs
is
to
our
documentation.
You
can
follow
the
hashtag
P
and
PJs
on
Twitter
as
well.
You
can
follow
me
at
mediocre
bowler
on
Twitter
I,
don't
tweet
out
a
ton
of
stuff-
it's
mostly
just
related
to
this
library,
so
you
won't
get
a
lot
of
spam.
For
me,
I
do
an
answer.
Real
cool,
quick!
This
question
is
p.m.
PG
s
or
requirements
to
utilize,
Adel
Jas
stuff
with
no
no
pop-ups.
So
no
p.m.
A
A
You
won't
actually
interact
with
Adel
GA
s
at
all
in
your
code
anymore.
If
you
go
down
that
route
as
well,
if
you
go
down
the
PGS
Ralph,
you
won't
need
to
interact
with
Adel
jeaious
on
your
own
anymore
either,
but
it
is
not
a
requirement
of
course.
We
hope
you'll
use,
P
and
PJs
and
use
it,
but
not
a
requirement.
So
you
can
use
that
stuff
in
SharePoint
framework
1.6,
absolutely
with
Alps
PJs.
So
it's
a
ad
HTTP
client
as
well
there's
an
ad
token
provider.
A
Those
are
both
accessible
off
of
the
context,
object.
There's
a
couple
of
methods
called
ad
token
provider
factory
and
a
ad
HTTP
client
factory,
I
believe
so
check
those
out
also
new
capabilities
and
as
well.
You
can
take
advantage
of
those
now
in
p.m.
PJs
if
you
like,
but
that
is
optional
and
not
a
requirement
so
great
questions,
a
number
of
rabbits
the
same
as
contributors.
A
No,
actually,
that
would
have
been
a
really
good
easter
egg,
but
I
didn't
think
of
that.
So
you,
you
are
more
clever
than
me
with
that,
but
no,
the
number
of
rabbits
is
just
sort
of
an
ongoing
joke,
or
is
it
the
October
p.m.
PJs
by
the
numbers,
the
top
left
column
or
the
top
left
graph?
There
is
a
number
of
requests
and
unique
tenants
per
month,
so
we're
up
to
1.8
billion
requests
in
the
month
of
October
across
5.9
or
50
900
tenants.
A
So
again,
amazing
growth
over
September,
and
that
is
all
thanks
to
you
in
the
community.
So
really
everybody's
saying
they
lost
video.
Some
folks
are
saying
they
still
have
it.
Everything
looks
fine
on
my
end,
so
I'm
gonna
keep
going
in
the
top
right
graph.
There
is
the
number
of
NPM
downloads,
for
so
this
is
actually
for
the
at
P
and
P.
A
Slash
SP
library,
I
had
to
pick
one
to
be
representative
and
we
can
see
again
great
growth,
so
we
had
11,000
downloads
from
NPM
in
the
month
of
October
which
in
in
in
the
realm
of,
if
you
talk
about
stuff
like
react,
and
things
like
that
is
not
a
large
number
but
for
us
is
really
impressive.
It
shows
some
great
growth
month
over
month
and
then
actually
from
when
we
started
tracking
this.
It's
some
really
really
fantastic
growth.
So
appreciate
that
again,
that's
thanks
to
all
of
you
and
the
bottom
graph.
A
A
So
hopefully
you
found
that
helpful
and,
of
course,
if
you
have
updates
or
suggestions
or
things
missing
in
the
documentation,
please
let
us
know
we'll
do
our
best
to
get
that
updated
just
as
quickly
as
we
can
moving
up
to
updates
on
office,
365
CLI
new
version,
one,
eight
zero
with
commands
for
adding
channels
to
teams
managing
site
classification,
managing
taxonomy,
updating
tenant
settings
as
well
as
managing
web
hooks.
The
cross-platform
PNP
starter
kits
setup
script
is
still
in
progress
and
more
commands
are
also
being
worked
on.
A
Of
course,
if
this
is
a
great
opportunity
to
contribute
CLI,
if
you'd
like
to
get
involved,
there's
a
lot
of
open
issues
marked
as
Help
Wanted,
so
definitely
encourage
you
to
check
those
out
and
a
CLI
is
a
nice
place
to
I
mean
hopefully
everywhere.
It's
a
nice
place
to
contribute,
but
the
CLI
is
nice,
because
each
of
the
commands
is
fairly
atomic.
So
you
can
work
on
one
thing
without
necessarily
having
to
learn
how
the
entire
library
functions
so
check
that
out.
A
You
can
always
install
the
latest
versions
from
NPM,
get
more
information
at
the
AKMs
o365
CLI
there's
also
a
hashtag
on
twitter
office,
365
CLI,
the
guitar
IM
channel.
You
can
follow
there
as
well,
and
then
the
docs
are
at
that
link.
A
kms,
35
CLI
update.
Excuse
me
update
on
the
reusable
controls.
So
if
you
haven't
checked
these
out,
there's
two
sets
of
controls,
property
controls
and
then
react
content
controls.
The
property
controls
are
designed
to
work
in
the
property
pane
for
your
web
part.
So
that's
inside
that
editing
experience.
A
You
can
go
check
that
out.
That
would
be
when
you,
edit,
your
web
part.
You've
got
these
controls;
these
are
all
designed
using
the
office,
UI
fabrics,
you're
gonna,
get
a
nice
out-of-the-box
look
and
then
as
well,
will
really
save
you.
Some
time
help
you
out
in
your
building
your
applications
and
getting
things
started.
So
a
lot
of
these
are
common
asks.
Why
isn't
there
control
to
do
X,
Y
&
Z?
Well,
now
you
can
find
them.
A
This
is
also
a
great
place
to
contribute
if
you
have
ideas
for
new
property
controls
or
as
well
new
content
controls,
which
is
the
other
library
of
controls
and
the
content.
Controls
are
designed
to
work
in
the
body
of
your
webparts,
so
either
displaying
data
or
otherwise
providing
an
UI
surface.
That
would
be
interactive
for
your
users
as
opposed
to
folks
editing
the
web
part.
So
please
check
out
both
of
those
libraries,
I'm
really
good
stuff,
and
then
you
know,
of
course,
they're
a
great
place
to
contribute
great
place
to
provide
feedback.
A
The
most
used
controls
with
the
placeholder
control,
the
web
part
title
control,
and
then
the
people
picker
control,
there's
also
taxonomy
picker
controls,
color
picker
controls
some
various
different
things
so
really
exciting.
Stuff
really
save
you
a
lot
of
time
on
your
development
efforts
and
give
you
a
great
out-of-the-box
built
in
look
for
your
editing
and
content
controls.
So
we
did
get
a
new
field
control.
A
The
list
item
picker
we
were
gonna
have
that
demoed
on
this
call,
but
unfortunately
I
screwed
up
I
got
my
dates
wrong,
so
we
will
get
that
onto
a
future
call
but
a
great
new
control,
so
that
was
actually
added
from
the
community
and
you
can
see
that's
number
item.
165
I
think
they'd
be
pull
request.
165
do
check
that
out
and
then
we
have
more
information
at
2
links
down
below
the
SP
dev
effects,
property
controls
and
the
SP
dev
effects.
Controls
react
so
and
I
didn't
mention.
A
These
are
all
react,
based
controls
so
to
check
those
out
and
sorry
I'm
gonna
come
down
here
and
meet
somebody
there.
We
go
so
last
thing:
I!
Don't
have
updates
for
this
today.
So
we're
about
to
see
a
demo
on
this,
but
we'll
have
updates
on
the
calls
for
this
going
forward.
So
we
have
this
I
said
new
to
this
call
thing,
but
it's
been
now
worked
on
for
a
few
months
by
stefan
bauer
and
it's
a
yeoman
generator.
It's
a
community
yeoman
generator
on
top
of
the
out-of-the-box
SharePoint
framework,
yeoman
generator.
A
So
it's
an
extension
of
that
generator.
So
out
of
this
you're
gonna
get
a
valid
SharePoint
framework
project,
built
on
all
the
same
libraries,
just
with
a
few
different
options
for
configuring.
The
project
and
a
few
different
frameworks
available
to
get
you
started,
but
I
don't
want
to
steal
his
thunder.
So
I
will
turn
things
over
to
Stephan
if
he
is
ready.
A
C
Quit
so
in
one
point
three:
actually,
we
currently
have
the
version
1.4
and
there
is
something
which
you
might
familiar
with.
So
the
office365
CLI
has
the
SP
FX
project
update,
which
allows
you,
when
you
have
an
existing
project,
to
check
out
what
version
you
currently
have
in
your
project
and
when
you
want
to
upgrade
to
1.6
or
1.7,
you
can
use
this
command
out
of
the
office.
365
CLI,
when
you
have
a
really
old
project
like
I,
have
here
I
can
check
up
the
package
so
Jason
and
see
okay.
It's
one
point.
C
C
So
when
I
checked
in
my
project
root
directory,
I
hear
markdown
file,
which
explained
me
in
detail
what
steps
I
have
to
take
to
upgrade
my
project
to
the
latest
version.
This
is
one
of
the
benefits
and
with
the
PP
effects.
Generator
tilde
come
a
lot
of
things
together
from
from
point
P.
What
we'll
see
in
the
next
couple
of
seconds
so
the
late
vision
to
this.
C
So
it
is
pretty
convenient
because
you
don't
have
to
update
you,
don't
have
to
run
the
office
365
CLI
manually,
but
instead
you
can.
Whenever
you
want
to
have
a
new
web
part
or
check
what
version
the
project
is.
You
can
execute
PPS
effects,
but
that's
not
all
so.
The
latest
update
I
have
here
and
to
folder,
and
the
latest
update
we
have
is
actually
we
have
no
angular
elements
in
there
so
taeeun
now
in
this
blank
folder
p.m.
VSP
FX,
then
it
gives
me
a
lot
of
options.
C
So
we
have
here
the
handlebars,
which
was
the
first
generator
has
been
built,
and
we
have
Gooch's,
for
example
in
here
that
sets
up
a
project
to
use
whoo
yes,
but
you
can
also
use
the
default
SPF
X
generator
like
the
default
SharePoint
framerate
1.6
generator
for
knockout
no
framework
and
and
react
shifts.
So
but
let's
check
out
this
angular
experimental
is
there
because
we
currently
constantly
improving
the
angular
element
story
and
try
to
make
it
more
better
from
a
developer
perspective.
C
So
the
next
step
is
I
can
select
here
now
among
multiple
libraries
and
what
you
see,
for
example,
whenever
you
start
a
new
project
to
zucchini
es,
then
you
can
directly
selected
here
and
that
will
be
included
in
your
SPF
X
project.
The
PMT
property
controls
that
Patrick
already
mentioned
are
always
there,
because
when
a
web
part
renders
then
it's
always
by
default,
react
control.
C
So
the
PNP
property
controls
and
not
you-
cannot
only
use
in
reactive
projects,
but
you
can
just
use
this
this
kind
of
this
library
in
all
your
projects,
okay,
so
the
next
thing
is:
what
is
your
solution
name?
This
is
something
specific
to
the
angular
elements
generator,
because
we
need
to
first
check
the
solution
before
the
SPF.
X
generator
runs
because
what
we
do
with
the
angular
elements
generated.
We
create
two
projects
there,
instead
of
one
SP
FX
project,
so
I'm,
fine,
that
was
ng,
Angola
awesome
and
one
concern
for
angular
developers
is
always
hey.
C
I
want
to
use
their.
My
CLI
and
I
want
to
set
up
my
project
with
additional
parameter
so
because
we
creates
project
where
it
can
actually
in
the
angular
project,
you
can
use
the
CLI
as
you
used
to
you
as
an
angular
developer.
When
we
set
up
the
project
for
you,
you
can
pass
here
some
additional
properties
in
there
how
your
angular
project
should
be
generated.
So
in
this
case
we
have
defaults
for
style
to
make
it
a
CSS
CSS.
C
Then
we
won't
talk
much
of
routing
in
there
and
it
also
shouldn't
include
directly
a
git
repository
and
now
what
you
see
now
is
actually
the
base
default.
1.6
sharing,
so
I
can
say
now:
SharePoint
Online
latest
version
tenant
deployment.
I
want
to
create
a
web
part.
What
is
your
name
alvaro,
scripting
and
then
what
you
see
now?
The
first
part
is
generated
by
the
SP
fest
framework.
Now
what
you
see
we
created
an
NG
awesome
file
directory
where
we
create
a
new
angular
project
so
save
time.
C
I
currently
already
fit
this,
so
we
have
here
two
projects.
Now
let
me
open
this
in
code,
so
the
mg
awesome
project
is
standard.
Angular
project.
When
you
say
a
create
me,
please,
in
your
angular
project,
the
SP
FX
project
is
actually
completely
SP
FX
chef
on
framework
project.
So
when
I
go
now
to
ng,
awesome
and
sayi
ng
serve
and
start
my
angular
project
in
debug
mode.
Then
it
first
built.
C
You
see
this
default,
this
component
that
we
default
by
default
generate
here.
So
let's
do
something
in
here,
so
this
is
stored
in
the
mg
pro
thousand.
It's
in
the
source,
folder
ng,
the
angular
elements
are
actually
something
like
web
components
you
might
heard
of.
So
we
have
an
HTML
template
here
that
takes,
for
example,
the
description
of
the
web
part
like
the
hell
world's
web
for
us
and
when
I
do
something
like
this.
C
Like
this
one
and
say
lorem
15
for
a
forum
and
save
my
project,
it
should
actually
rebuild
its
soup
right
here,
and
this
is
how
the
component
history
can
be
built
directly
with
all
the
angle
of
goodies
that
are
in
the
framework.
Okay,
so
any
angle
of
developer
actually
can
write
you
now,
a
component
for
your
Shepherd
framework
that
part.
So
this
is
embedded
on
the
index
of
HTML
and
the
whole
idea
behind
web
components
is
to
write
custom
elements
to
the
native
HTML
elements
that
are
available,
which
is
actually
the
future.
C
So
when
I'm
done
with
developing
my
web
part,
I
can
go
here,
stop
the
debugger
and
say
and
NPM
to
run
bundle
and
what
this
actually
does.
It
creates
a
production,
build
a
library
that
I
can
use
in
my
SD
FX
web
part,
so
what
it
actually
does
here.
It
builds
a
productive,
read,
production,
ready
library
and
then
bundles
all
the
different
components.
Like
main
she
has
polyfills
runtime
script,
stars
and
bender.
She
has
to
a
single
file.
C
Ok
now,
when
I
go
back
to
my
angular
project
here,
I
have
here
in
the
dismissed
or
folder
bundle
file,
which
is
minimized
and
optimized,
and
everything
in
there
swell
is
really
small,
because
it
only
has
two
hundred
and
eighty
kilobytes,
something
like
that.
Ok,
so
how
do
we
bring
this
over
to
our
SPF
X
project?
C
What
you
see
in
the
angular
project
and
every
angle
of
project
is
also
a
package
of
chasing
ok,
so
you
have
here
all
the
dependencies.
You
have
a
name
version
number.
You
have
here
a
bundle
task,
for
example,
but
because
this
has
a
package
that
chasing
you
can
MPM
install
it
from
wherever
you
like.
So
you
don't
always
have
to
install
packages
directly
from
the
web
from
NPM
Jia's.
C
You
can
also
install
NPM
packages
from
github,
or
you
can
also
use
if
local
reports
here
and
when
we
look
over
to
the
ng
awesome
SPF
X
project,
what
we
have
him
here
in
the
package
of
Chasen.
We
have
a
reference
directly
to
ng
awesome,
which
says
file
lot
dot
and
she
awesome
which
points
our
stuff
directly
to
this
folder.
C
So,
whenever
I
build
a
new
project
in
here,
I
don't
need
to
cope
it
over
wire
up
things,
but
I
can
directly
use
it
like
a
mobile
use,
any
library
in
the
web
part
you
see
the
black
part
of
TS
and
what
we
actually
do.
Is
we
import
here?
The
ng
awesome,
dist
ng,
awesome
bundle
which
is
located
in
the
other
project
in
here.
Okay.
C
So
whenever
I'm
building
the
angular
project
and
new
version,
then
this
automatically
gets
included
in
my
SPF
X
project
and
then
what
we
do
in
the
render
method
here
is
we
just
create
the
project.
The
base
project
is
a
non
HTML
standard
project
and
what
we
do
is
we
simply
render
here
this
new
custom
element
on
our
page.
So
when
I
do
not
over
to
my
ng
awesome-
and
she
awesome
SP
effects,
project
and
say
here-
go
serve.
C
C
A
Thanks
that
was
really
fantastic:
stuff
I'm
gonna
go
ahead
and
take
back
over
just
so
you
can
close
out
the
call.
But
folks,
if
you
haven't
checked
that
out,
it's
really
great
and
it
has
a
lot
of
neat
capabilities
that
don't
come
with
the
out-of-the-box
SharePoint
framework.
Yeoman
generator,
but
again
is
a
nice
extension
of
that
functionality
really
really
cool
work
there
and,
of
course,
you
know
open
to
contributions
as
well.
So
if
you
have
ideas
or
want
to
improve
that
or
help
with
that,
please
do
definitely
welcome
that.
A
So
no
time
today
for
the
Q&A,
unfortunately,
but
next
there
we
go
our
next
JavaScript
special
interest
group
meeting
will
actually
be
November
22nd,
which,
for
those
of
you
in
the
United
States,
is
Thanksgiving
typically
a
holiday.
We
will
have
a
call,
it's
likely
to
be
a
little
more
lightly
attended,
but
we
will
have
a
call
and
then
the
next
general
SharePoint
special
interest
group
is
next
Thursday,
November
15th,
so
I
look
forward
to
seeing
everybody
at
both
of
those
calls.