►
From YouTube: SPFx JavaScript SIG 20170119
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meeting
is
January
19th
2017.
If
you
missed
our
meeting
last
time,
let
me
say
happy
to
happy
New
Year
to
you
this
time,
we're
well
into
2017
now,
which
is
already
a
little
crazy
for
me
and
likely
for
most
of
you.
So,
let's
jump
into
our
meeting,
we
got
some
exciting
stuff
to
talk
about
today,
so
the
special
interest
groups
are
part
of
the
larger
SharePoint
patterns
and
practices
program,
which
is
now
under
SharePoint
engineering.
And
what
are
we
all
about?
A
So
we're
mainly
about
two
things,
which
is
open
discussion
and
learning
around
the
SharePoint
framework,
which
is
not
release
candidate
zero,
which
is
really
exciting,
love
to
see
that
out
there
folks
are
doing
some
really
cool
stuff
with
that
we're
getting
some
great
feedback
around.
That
base
is
going
to
talk
about
the
latest
with
that
here
shortly
and
we're
also
here
to
talk
about
building
these
JavaScript
core
components.
We'll
talk
a
little
bit
about
the
evolution
of
that
on
today's
call.
A
So
two
links
down
at
the
bottom,
the
AKMs
SP
P&P
community-
will
get
you
out
to
the
Microsoft
tech
community,
which
is
great
for
you
know.
If
you
have
questions
or
looking
for
resources,
things
like
that
and
then
dev
office
comm,
slash
SharePoint
is
your
landing
page
for
all
SharePoint
development,
so
whether
you
want
to
learn
the
new
SharePoint
framework
stuff,
whether
you
have
add
in
development
questions
whether
you
have
classic
server-side
SharePoint
development
questions,
that
is
your
one-stop
shop
and
there's
links
and
pages
to
all
the
various
bits
of
documentation
and
areas
there.
A
So
it's
a
great
starting
point
for
everything.
Sharepoint
development
so
definitely
check
that
out.
If
you
have
not
so
looking
at
our
agenda
for
today,
like
I,
said
updates
on
the
latest
for
SharePoint
framework
released
candidate,
zero
is
out
which
is
really
exciting.
It's
really
close
to
what's
going
to
be
final,
or
at
least
the
shape
of
what's
gonna,
be
final.
We're
gonna
talk
through
some
of
those
core
component
stuff.
B
Yes,
we
do
that,
then.
Let
me
unmute
myself
so
I'm
not
talking
to
myself
in
the
office
room.
So
there
we
go
I'm,
actually
stealing
the
presentation,
so
few
updates
on
this
one.
So
there
really
is
candidate,
let's
actually
start
going
on
through
the
slides,
so
the
release
candidate
went
out
last
week.
So
the
release
candidate,
like
mentioned
in
the
previous
special
interest
group,
call
there
were
some
breaking
chances.
What
we
wanted
to
do
with
release
candidate
is
rather
to
have
those
breaking
changes,
spotted
the
release
candidate
rather
than
when
we
go
to
GA.
B
We
are
actually
getting
pretty
close
to
the
general
availability.
So
if
you
haven't
had
a
time
to
have
a
look
on
the
SharePoint
framework
and
you've
been
kind
of
awaiting
whenever
it's
ready
to
be
used
in
production,
we're
actually
not
that
far
away.
So
we're
not
talking
about
months
and
months
and
months,
much
less
than
that,
so
the
release
candidate
is
already
pretty
close
on
what
we're
gonna
ship
as
a
ga.
The
certain
adjustments
there
here
and
there,
which
was
the
doing
like
easier
way
of
deploying
webparts
to
be
available
within
sites
we've,
been
adjusting.
B
Some
of
the
areas
after
the
release
candidate
in
production
as
well,
we
did
have
a
as
an
example.
We
did
have
some
issues
related
on
using
SharePoint
framework,
client-side
web
parts
in
classic
pages
and
last
week
an
earlier
this
week
and
that
has
been
out
tackled
in
production.
So
if
we
were
testing
released
candidate
in
SharePoint
Online
in
first
released
an
answer
or
a
dev
tenant,
you
were
able
to
use
them
only
within
the
modern
pages,
not
within
the
classic
pages,
and
that
has
been
now
result.
B
So
I
think
we
fixed
that
yesterday
in
the
production,
but
in
general,
the
API
layers
and
API
level
and
API
super
super
close
already
with
the
GA,
so
more
working
now
on
the
infrastructure
side,
making
sure
that
that's
fully
functional
what
else
under
shipment
framework
side.
So
we
were
looking
into
obviously
destiny
guidance
again
since
past
two
weeks
already
in
the
depth
of
stock
on
SharePoint
and
by
the
way,
please
do
remember
if
you're
a
SharePoint
developer,
you
should
no
longer
go
to
the
MSDN.
B
B
Sharepoint
development
topics
so
SharePoint
same
work,
of
wit,
hoops
is
in
here
SharePoint
framework
reference,
API
are
actually
in
the
depth
of
officer,
comes
the
SharePoint,
we're
moving
in
the
shape
and
adding
model
documentation
here
as
well,
which
slightly
off
the
topic
of
today,
but
still
and
we're
looking
into
moving
the
rest.
Api
documentation
there
as
well,
and
there
will
be
then
further
announcements
in
for
the
future
of
the
MSDN,
the
the
existing
MSDN.
As
an
example,
certain
are
clarified
that
statement.
B
The
existing
Emma
stay
in
is
super
super
super
super
super
old
technology,
and
it
requires
people
at
the
level
of
COBOL
to
maintain
that
information.
So
we're
looking
into
taking
advantage
of
more
modern
purposing
mechanisms
in
the
future,
so
that
the
community
can
also
contribute,
and
if
there's
any
issues,
they
can
actually
fix
that
or
they
can
submit
an
issue
and
pull
requests
in
a
key
tab
and
all
that
is
getting
reflected
in
the
in
the
US
as
well
assuming
to
be
released
documentation.
B
These
are
not
quite
yet
they're
out
there
in
the
table
of
contents,
localizing
localization
or
localizing
client-side
web
ports.
This
is
a
topic
which
we
did
a
webcast
together
with
Waldeck,
which
went
live
on
this
Monday
in
our
video
section
in
YouTube,
but
there's
the
actual
tutorial
is
going
to
be
released
on
that
one.
We're
gonna
release
a
Enterprise
guidance
documentation
for
SharePoint
framework.
So
thinking
about
what
is
actually
open
framework,
why
is
it
beneficial
animal
more
as
a
Enterprise,
Architect
level
discussion?
B
B
B
Some
of
this
I
actually
already
mentioned,
but
tutorials
and
labs
are
already
updated
at
the
release
candidate
level.
So
if
you
go
to
the
depth
of
that
comes
to
SharePoint
and
getting
started
with
with
webparts
our
let's
say,
setting
up
your
development
and
books,
all
of
that
is
already
in
the
release
candidate
level.
The
videos
are
going
to
be
updated
tomorrow
in
YouTube,
so
we
do
have
a
recorded
videos
of
those
tutorials
as
well.
B
So
if
you
prefer,
rather
than
reading,
you
want
to
see
me
explaining
what's
actually
happening
and
know
how
to
get
started,
how
to
create
your
first
client
side
web
for
those
videos
currently
today
are
still
in
the
August
level,
so
they're
in
a
trop
one
level,
so
they're
pretty
far
actually
behind,
but
there's
gonna
be
updated
tomorrow
in
YouTube,
which
is
a
good
thing
and
from
the
diffidence
that
comes
the
SharePoint
in
those
tutorial
pages.
There's
a
link
to
the
videos
as
well.
B
So
all
of
that
this
is
taken
care
of
and
by
the
way,
I
one
of
additional
video
kind
of
related
on
this
one.
So
I
did
do
a
recording
earlier
today
on
setting
up
your
development
environment
because
quite
often,
especially
for
classic
SharePoint
developers,
we
seem
to
get
the
feedback
that
hey
it's
super
super
complex
and
it
install
Noches,
NPM,
gulp
and
all
of
this
stuff.
I,
don't
know
how
to
do
that
and
though
it's
actually
documented
in
our
our
documents.
B
There's
a
video
available
on
that
one
starting
tomorrow
as
well,
and
for
ali
clean
machine,
Windows,
10
machine
I.
Think
it
took
me
like
10
minutes
to
get
to
environments
up
and
running.
So
it's
super
first
thing
as
well,
so
we
kind
of
a
reduced
the
reduced
the
time
to
set
up
SharePoint
framework
in
one's
quite
significantly.
Comparing
what
was
the
situation
with
the
Trop,
so
one
back
in
the
August
time
frame
what
else
sample
updates
ongoing.
B
So
some
of
the
sample
updates
are
already
in
the
release
candidate
level,
we're
looking
into
getting
them
to
the
release
candidate
level
first
and
then
to
the
Chie
level
whenever
we
get
to
the
GA-
and
this
is
gonna
happen
on
the
on
this
week
and
following
week
as
well,
getting
started
with
SharePoint
framework
training,
packets.
We
talked
about
this
one
a
few
times
in
the
special
interest
group
call
up.
We
went
through
the
attend
on
everything
else.
B
New
articles
are
kind
of
I
mentioned
this
one
already
so
localizing
SharePoint,
favorite
parts,
Enterprise
guidance,
team
development
coming
up
quite
soon,
actually
most
likely
tomorrow
or
next
week,
and
then
there
are
few
more
samples
in
the
shipment.
It
up
organization
related
on
client
side,
web
pods,
and
that
is
pointed
away,
a
crate,
crate
crate
resource
to
understand
how
would
I
do
x
and
y
and
C
using
react
or
angular
or
knockout,
and
there
are
simplistic
sample.
B
There
are
complex
examples
as
well,
so
it's
a
really
really
really
superb
resource
and
the
easiest
way
actually
find
all
of
these
samples,
one
URL
to
remember
again
a
kms
SPF
x
samples
you
learned
actually
in
the
deathbed
of
calm.
Yes,
less
that
the
PMP
catalog
sample
catalog
and
from
there
you're
able
to
then
have
a
look
on.
Are
we
interested
on
react,
components
or
angular
or
knockout?
B
And
you
can
see
all
of
the
samples
which
are
available
so
should
be
useful
resource
for
you
to
consume
as
well
now
kind
of
I
was,
since
we
are
closing
in
to
the
Chie
and
I
didn't
want
actually
do
a
demo
on
but
hey.
This
is
the
release
candidate
because
technically
there
is
a
really
isn't
there.
Certain
changes
in
API
level,
but
they're
not
really
significant
from
a
ooh.
That's
super
cool
perspective.
It's
more
around!
B
Hey,
don't
use
that
API
use
this
API,
but
I
wanted
to
quickly
have
a
chat
before
we
can
move
forward
on
patch
fix
area
or
more
on
the
p.m.
PHAs,
or
is
that
whenever
we
get
the
samples
updated,
we
have
two
tutorials
updated.
We
have
the
videos
updated.
We
have
the
additional
documentation
what's
needed
and
what's
actually
missing.
B
So,
let's,
let's
assume
that
we
are
GA
available
right
now
today,
if
we
have
existing
guidance
documentation,
some
samples
on
the
same
level,
what's
missing
from
your
perspective
as
the
community
members
to
get
started
on
on
implementing
client-side
web
parts
except
time.
Obviously
they
learn
to
do
that.
But
is
there
something
guidance,
samples
documentation
which
is,
in
top
of
your
mind,
kind
of
a
we
need
to
have
X
emergency,
otherwise,
I
can't
do
it
on
and
feel
free
to
use
the
iron
window
or
even
go
unmute.
B
The
difference
is
between
SPF
X
and
way
back
well.
Webpack
is
actually
used
by
SPF
X,
so
it's
a
it's
a
tooling
inside
with
which
were
using.
So
it's
it's
not
really.
There's
no
has
such
a
difference,
provisioning
webparts
onto
a
page
and
that's
a
good
comment
from
Lee
so
or
Dale-
it's
probably
Dale.
B
B
So
Nigel
is
saying
what
I
can
do
with
this
VFX
that
I
cannot
do
with
web
back.
What
care?
What
can
I
do
in
the
cloud
that
I
cannot
do
in
on-premises?
Okay,
that
so,
let's
clarify
that
slightly
so
web
pack
is
essentially
tooling.
What
SharePoint
framework
is
using?
It's
an
automation,
tooling
in
the
or
a
test
tooling,
and
we
use
that
heavily
as
well
shape
and
framework
is
providing
us.
B
A
B
is
based
on
baseline
classes
for
typescript,
which
are
then
integrated
into
the
SharePoint
and
Chevron
framework,
just
use
webpack
in
the
inter
tooling
as
well.
So
you
can
technically,
if
you,
if
you
don't
want
to
use
the
client-side
web
part
framework,
it
means
that
you
don't
have
property
pain,
you're,
not
actually
creating
a
web
part.
It's
as
such,
you
would
be
just
creating
a
script
array
the
web
part.
So
you
could
actually
write
your
stuff
without
a
ship
on
framework
as
well.
B
Then
it
wouldn't
be
a
SharePoint
framework
client
side
of
a
park
web
part,
but
you
could
use
web
back
as
the
tooling
for
automating
on
certain
tasks
there's
as
well,
but
it's
not
really.
They
then
they're
dependent
on
each
other,
but
it's
not
really
a
competition
webpack
handles
the
bundling
indeed.
So
how
do
we
actually
package
the
the
chava
script,
to
a
single
alter,
this
individual
chocolate
for
a
single
javascript
file
or
which
of
them
we
actually
package
an
ACS
verifying
that
as
well.
B
We
need
docs
on
how
to
import
external
types.
Yes,
that's
absolutely
good
point.
We
probably
should
clarify
that
for
some
people
that
might
be
super
clear
for
some
people.
That
might
not
be
super
clear.
So
if
you
have
a
look
on
top
updated
tutorials
on
the
jQuery
UI
implementation,
that's
where
we,
for
example,
Indian
installed
types
and
jQuery
and
jQuery
UI
to
the
client-side
web
part.
So
it's
nothing
more
than
actually
installing
those
types
into
the
solution.
B
The
way
to
exclude
external
libraries
from
being
bundled
is
not
very
easy
to
find
unless
you
find
that
in
other
guides
provided
good
feedback.
We
probably
should
be
more
specific
on
that
one,
because
that
that's
a
super
super
important
thing
to
understand.
When
do
you
reference
a
react
or
angular
or
whatever
JavaScript
from
a
CDN,
because
we
don't
wanna,
bundled
us
in
the
same
JavaScript,
because
otherwise
the
bundled
choice
would
get
super
super
big.
B
Docs
to
import
them
be
a
declaration.
Why
would
you
guys
have
that?
That's
a
typescript
thing!
Why
that
goop
dog
so
and
a
fair
point,
so
good
point
on
them,
so
we're
trying
to
kind
of
walk
on
the
line
of
what
does
the
SharePoint
classic
shape
on
developer
main
need
a
starting
point
and
obviously
will
wanna
more
concentrate
on
referencing
those
things
which
already
exists.
B
If
you
come
from
a
background
where
you
don't
have
a
web
stack
previous
knowledge
on
a
web
stack
and
that
might
feel
an
oversight,
it
might
feel
that
a
microscope
you're
not
giving
me
the
tools
how
to
do
my
job
on
the
ship
and
framework,
and
that's
why
we
actually
want
to
reference
some
of
the
stuff
and
help
people
to
actually
get
started
on
some
of
this
stuff
in
our
guidance
as
well.
But
again
we
don't
want
to
duplicate
documents.
That's
that's
a
fair
comment.
B
Recommendation
about
use
p.m.
PHAs
core
with
SharePoint
framework.
Well,
it's
an
option.
We
this.
This
is
a
classic
discussion
and
I
can
go
on
and
on
for
that
one
for
hours,
there's
no
such
things
as
best
practices
or
recommendations.
It
really
depends
on
what
are
we
trying
to
achieve
and
what
is
the
skillset
of
your
team?
What
is
the
skill
sort
of
years
self
and
just
choose
the
right
tool
for
you?
B
One
man's
best
practice
could
be
a
horrible
mistake
for
another
man
and
that's
why
we
don't
actually
explicitly
say,
recommendations
black
and
white
recommendations
or
best
practices
anymore,
because
quite
often
there
are
those
are
wrong.
Personally,
I
never
participate
on
any
seminar
sessions
with
our
best
practices
with
whatever,
because
you
can't
define
best
practices.
It
depends
on
the
Condor
context.
Whether
you're
trying
to
achieve
Joe,
has
a
good
point
on
the
on
the
bundling,
which
is
really
the
key
point:
people
forgetting
about
expert
libraries
and
then
the
page
size
is
crows.
B
B
Typical
web
part
to
creat
items
from
a
list,
for
example
from
a
ribbon.
We
do
have
a
sample
on
that
one.
We
do
have
a
sample
which
is
showing
how
to
do
crew
operations
using
PMP
check
or
a
react,
angular
and
jQuery,
and
without
any
framework,
so
we
do
have
an
existing
sample.
Maybe
we
should
have
then
a
tutorial
or
an
article
in
finding
those
differences.
There's
the
sample
itself
is
actually
there's
a
good
readme
file
on
the
sample
as
well.
B
But
maybe
the
problem
is
more
on
people
finding
those
samples
which
we
need
to
work
on,
which
is
actually
one
of
the
things
in
general.
What
we're
working
on,
but
that
will
still
take
some
time
is
there
is
the
better
and
more
compelling
a
sample
catalog
or
an
example,
poro
site
CM
site,
where
people
can
find
what's
real
and
for
them.
B
No
I
would
say
that
we're
working,
improving
the
story
in
the
Sabet
sense
that
pretty
soon
you
can
absolutely
call
your
external
services
to
handle
server-side
operations
and
combined
with
the
client-side
SP
FX
client-side
web
parts,
a
server-side
piece
without
any
additional
authentication,
and
we
get
all
of
that
clarified.
And
we
are
absolutely
aware
of
the
challenge
of
the
fact
that
if
we
have
10
different
webparts
and
all
of
the
10
different
web
parts
are
loading
10
different
libraries,
then
the
page
sizes
are
enormous.
It's
absolutely
true.
B
Moving
at
the
stuff
from
the
server
side
is
viable
solution
and
certain
things
to
the
server
side,
which,
by
the
way,
is
one
of
the
reasons
as
an
example.
Why
the
the
provisioning
logic
was
taken
away
from
the
PHAs
core,
because
technically
it
does
not
make
any
sense.
In
any
scenario
to
do
site
provisioning
using
javascript
unless
it
is
actually
done
on
the
server
side,
but
doing
that
in
a
client-side
is
not
really
an
enterprise
ready
solution.
So
and
that's
now
taking
to
another
library
and
that's
going
to
be
released
as
a
separate
package.
B
B
Joe
is
saying
some
months
ago:
I
implant,
this
to
a
provider
hosted
up
on
from
for
client
using
note
app,
although
it
was
really
hard
to
find
documentation
and
authentication.
Is
there
something
on
the
pipeline
for
bits
that
we
can
know
of?
That's
actually
a
good
point.
Maybe
we
should
provide
some
connectivity
between
that
one
and
having
a
strap-on
provider
hosted
adding
samples
on
a
noches
as
well
in
general.
In
the
ad
model,
we
will
have
investments,
engineering
investments
on
the
ad
model
as
well,
so
we're
looking
making
the
actual
add-ins
responsive
as
well.
B
So,
even
though
they
use
an
iframe,
they
would
be
responsive
and
that
you're
able
to
use
the
SharePoint
framework
inside
of
the
add-in
as
well.
But
the
adding
is
giving
you
the
security
isolation,
because
that's
being
asked
by
many
customers
as
well,
those
investments
will
happen
most
likely
during
this
spring.
It
really
depends
on
our
internal
priorities
and
schedules,
but
kind
of
related
on
adding
model,
but
I
think
what
she'll
is
more
referring
is
is
making
having
no
chairs
samples
using
the
SharePoint
our
implemented
a
shape
and
adding
which
just
makes
sense
as
well.
B
I
thought
Michael
was
Microsoft
was
telling
developers
to
get
their
code
off
the
SharePoint
servers,
as
if
the
code
crashes,
it
can
take
out
the
whole
farm,
whereas
use
the
client
code.
It
can
only
takes
out
the
client
absolutely
true.
So
we
are
telling
that
do
not
put
your
custom
code
on
the
ship
on
server.
Now
it
might
be
a
server
next
to
SharePoint
Server,
which
is
the
classic
provider,
hosted
adding
model
in
on-premises.
It
might
be
an
iis
server
or
noches
box,
which
is
serving
that
and
from
a
shippin
perspective.
It's
a
client.
B
The
client
is
hosted,
though,
outside
of
SharePoint
and
it's
using
the
remote
api's
to
call
in
to
the
SharePoint
and
doing
operations.
So
we
absolutely
want
to
go
away
from
the
fact
that
we
are
using
farm
solutions
because
those
are
problematic
to
maintain.
They
have
multiple
challenges,
everything
else
in
certain
scenarios.
Once
again,
this
is
not
a
black
and
a
black
and
white
statement.
In
certain
scenarios.
B
Absolutely
it
might
be
the
best
option,
or
only
option
if
you
are
in
on-premises
and
SharePoint
Online
No,
maybe
in
on-premise
days
you
want
to
align
more
on
the
shipment
on
the
client
side
development
as
well.
Whenever
we
ship
SharePoint
framework,
the
SharePoint
2016,
you
can
actually
have
a
one
implementation
again,
which
will
work
in
on
premises
and
in
cloud,
and
that
makes
a
lot
of
sense.
I.
B
Think
well,
Bill
is
having
an
awesome
comment.
I
think
it's
up
to
the
developer
to
decide
what
framework
to
use
the
developer
is
responsible
to
be
aware
of
the
consequences,
and
this
really
actually
comes
down
on
the
fact
that
personally,
as
well
I,
we
never
actually
tell
what
is
the
best
practice,
because
immediately
if
microcode,
Microsoft's
or
Microsoft
would
go
and
say,
hey,
it's
best
practice
to
use,
react
or
angular
or
BMP,
J's,
core
or
PMP
provisioning
engine
or
chip
and
framework
or
whatever
people
would
actually
take
that
as
the
P.
B
Those
are
saying,
that's
its
best
practice,
I,
don't
know
why,
but
it's
the
best
practice
and
they
wouldn't
actually
think
about
the
differences.
We
don't
want
to
do
that.
We
want
to
make
sure
that
people
make
a
knowingly
decision
to
do
this,
go
to
a
certain
direction,
with
the
advantages
and
disadvantages,
knowing
those
advantages
and
disadvantages
on
their
decision
as
well,
developer
can
choose,
they
cannot
know
about
the
consequences
because
they
aren't
once
putting
the
stuff
on
a
page
well
and
then
fair
point
for
Mike.
B
We
need
to
get
the
consequence
is
documented
as
an
example
document.
What
does
it?
Why
do
we?
We?
Why
did
we
use
real?
Well,
we
use
react
in
Microsoft
and
our
engineering.
What
is
the
impact
of
not
using
react?
Well,
there's
an
additional
JavaScript
library,
then
loaded
on
a
page.
Is
that
a
massive
deal?
No,
it
isn't,
but
thinking
through
the
bundling
impact
and
all
that
in
done,
I
think
it's
it's
more
under
education
and
making
sure
that
we
as
a
Microsoft,
we
document.
B
Why
and
the
impact
of
certain
actions,
that's
really
the
key
point
and
I
think
Mike
I
think
actually
Mike
and
Bill
are
talking
about
almost
the
same
thing.
Most
likely
bill
will
agree
on
that.
So,
if
the,
if
the
developer
is
done
aware
how
the
bundling
actually
works
as
an
example-
and
we
don't
educate
the
field
enough
on
the
bundling,
they
can
actually
cause
significant
chances
from
a
performance
perspective
and
we
as
Microsoft.
We
absolutely
want
to
have
the
sufficient
amount
of
documentation
on
that
and
Mike.
You
want
to
say
something
as
well:
yeah.
C
I
was
just
gonna
say
the
so
the
developer
doesn't
know
what
other
frameworks
are
going
to
be
running
on
the
page.
Their
web
part
gets
added
to
sure
and
the
developers
don't
know
the
consequences
either
because
they
don't
know
they
didn't
develop
all
of
the
parts
on
that
page
right
I
mean
it
could
have
been
from
seven
different
developers.
Yep.
D
D
B
They're
both
occurring
on
the
on
the
core
thing
and
I
am,
and
it's
it's
just
yes,
there
could
be
a
situation
where
the
developer
could
cause
challenges
and,
yes,
we
need
to
educate
the
developers
as
well.
In
the
end,
obviously,
the
service
itself
cannot
make
the
decision
that
they,
your
whip
artist,
is
loading
insane
library,
let's
ignore
de
and
that
won't
happen
so
yeah.
D
It's
just
the
same
as
if
somebody
develops
a
web
part
and
it's
very
inefficient
for
some
reason
you
know
that's
also
going
to
so.
That's
that's
a
consequence
of
choosing
a
not
having
the
same
version
of
the
libraries
that
everybody
else
is
using,
but
I
take
Mike's
point
out
is
yeah
there's
a
valid
case.
B
There
as
well
and
all
I
can
say,
is
saying
this
isn't
really
a
new
problem.
It's
a
classic
challenge
on
the
under
web
development,
going
back
on
the
I
am
window,
there's
a
few
questions
and
and
I
think
we
need
to
move
on
the
presentation
quite
soon,
but
there's
certain
questions
and
absolutely
fine
to
have
the
Q&A
at
this
point
as
well,
but
we
slightly
got
off
tracked
on
the
guidance,
samples
and
documentation
what's
actually
needed,
but
I'm
gonna
address
this
quickly.
So
ad
is
asking
around
any
update
on
the
policy
for
update
guidance.
B
So
how
do
we?
What
is
the
the
provided,
hosted,
versions
of
reactant
and
other
libraries?
No
updates
at
this
point
for
those
we're
still
fixing
stuff
in
the
are
seen
and
getting
there
and
then
hopefully
we
will
have
that
one
ready
for
Chie.
That's
absolutely
the
intention
now.
I
cannot
promise
that,
on
behalf
of
certain
persons,
but
looking
into
looking
into
absolutely
aware
of
Fisher,
and
we
need
to
get
that
one
and
document
that
easiest
also
commending
release
candidate
zero
implies
won't
be
the
last,
but
I've
heard
she
is
coming
very
soon.
B
Can
I
expect
more
release
candidates
priority
a
good
question.
We
we've
been
in
general
using
terms
release
candidate,
zero
or
release
candidate.
Most
likely
this
will
be
the
only
release
candidate
and
we'll
hits
into
the
chair
after
that.
Now,
theoretically,
we
might
still
change
our
stance
so,
but
we
are
looking
into
heading
to
the
Chi,
a
relative,
listen,
so
it
might
be
that
the
release
candidate
zero
is
the
only
release
candidate.
What
curse
actually
live
as
a
release
candidate
and.
B
B
A
D
A
Presentation
here,
so
everybody
should
see
the
PSP
TMP
j/s
core
component
slide.
Nothing's
really
changed
on
that,
oh
good.
So
as
always,
thank
you
to
all
our
contributors,
try
and
say
that
every
week
and
really
appreciate
we've
gotten
not
necessarily
contributions,
but
a
lot
of
great
feedback
on
the
2.0
code.
That's
in
the
dev
branch
still
so
really
appreciate
that
from
everybody,
that's
pointed
out
some
bugs
or
had
some
suggestions
on
improvements.
So
that's
super
valuable
one
dimension
is
always
opportunities
to
participate.
A
Demo,
a
SharePoint
framework
webpart
on
this
call.
You
can
demo
anything
related
to
the
the
J's
core
library
on
this
call
I'm
you
can
contribute
on
github
and
you
can
provide
feedback.
Of
course.
Those
are
also
welcome,
but
I
do
want
to
stress
again
we're
definitely
looking
for
folks
to
do
some
demos,
so
if
you're
doing
something
cool
with
release
candidate,
zero
or
something
cool
with
the
you
know,
J's
core
on
node
or
something
like
that-
would
love
to
get
folks
from
the
community
an
opportunity
to
demo
their
work
here
on
this
call.
A
That's
now
dependent
on
me
getting
the
blog
post
written
and
so
that's
going
to
include
a
bunch
of
great
bug,
fixes
some
new
features
and
it
incorporates
a
lot
of
the
great
feedback.
Again.
Thank
you
to
the
community
for
that
feedback.
It
really
makes
everything
grow
and
be
stronger
through
that
feedback,
and
then
the
updated
wiki
is
going
to
be
part
of
that
2.0
release.
So
we
talked
about
that
a
little
bit
on
the
last
call
and
we're
talking
about
that.
A
A
tiny
bit
more
on
this
call
and
I
also
going
to
touch
on
the
provisioning.
So
we've
got
the
code
out
to
the
new
repo
for
provisioning
and
want
to
stress
again.
That's
really
gonna
right
now
be
a
community
driven
project,
so
if
folks
from
the
community
have
interest
and
a
passion
around
provisioning,
that's
where
we
want
to
see
you
get
involved
and
contribute
to
that
provisioning
library.
A
The
thing
is
we
just
don't:
have
the
personnel
right
now
to
on
our
side,
commit
to
doing
that
and
also
we've
sort
of
are
invested
in
the
clients?
Are
the
the
Sison
toolchain,
so
the
managed
code
community
I'm,
sorry,
the
managed
code,
provisioning
stuff
which
is
fairly
mature
at
this
point,
and
so
that's
kind
of
where
a
lot
of
our
energy
is.
But
if
somebody
is
passionate
about
provisioning
on
node,
we
want
to
provide
that
opportunity.
A
A
Anybody
else
got
your
screen
perfect
great
thanks,
yeah
things
I
want
to
show.
So
these
are
part
of
the
2.0
release.
That's
coming
and
this
sort
of
goes
hand
in
hand
with
the
provisioning,
so
as
I
was
porting
the
code
over
provisioning
to
for
provisioning,
which
we'll
look
at
that
code
in
a
second
I
added
some
support
into
the
the
core
library
so,
for
example,
for
features
we
didn't
have
anything
previously
for
features
in
the
core
libraries.
A
So
now
you
can
add
and
remove
features
and
remove,
you
know,
add,
being
activate,
remove
being
deactivate
features
in
the
core
libraries.
So
that's
a
new
capability,
that's
going
to
be
part
of
2.0
and
it
follows
the
general
pattern
as
the
rest
of
the
pieces
do.
The
other
thing
I
wanted
to
mention
is
I,
updated
navigation.
A
So
we've
got
much
more
capabilities
instead
of
just
being
able
to
get
the
navigation,
you
can
now
add
navigation
nodes
to
both
the
quick
launch
and
the
top
bar,
and
you
can
use
this
move
after
method
to
reorder
those
nodes
and
that
operates
on
them
by
ID.
So
so
a
lot
more
capability.
You
can
get
two
nodes.
Children
and
of
course
children
are
then,
is
just
another
nodes
collection,
so
you
can
add
nodes
to
another
nodes.
A
Children,
obviously
folks,
are
familiar
with
that
kind
of
a
pattern,
and
you've
also
now
got
the
ability
to
update
and
delete
nodes
out
of
the
navigation.
So
we've
enhanced
the
ability
to
manage
that
which
was
a
capability
brought
over
by
a
need
from
need
in
the
provisioning
library,
so
I
sort
of
still
see
these
things
growing
hand-in-hand
and
sort
of
improving
a
little
bit.
You
know,
as
a
capability
is
needed
in
provisioning.
A
We
had
an
issue
reported
where
he
had
a
need
to
add
multiple
list
items
to
a
single
list
sort
of
rapidly
and
if
you
were
familiar
with
the
code,
one
of
the
things
you
have
to
do.
When
you
add
an
item
to
the
list
using
rest
is
you
have
to
have
the
list
item
entity
type
name
which
is
a
property
of
the
list,
and
so
we
had
code
that
would
go
out
and
get
that
and
what
that
essentially
did.
A
If
you
are
adding,
say
10
or
12
items
to
the
same
list,
it
doubled
the
number
of
calls
and
then
even
if
you're,
using
batching,
it
would
double
up
the
calls.
And
so
you'd
have
a
call
for
each
item.
You
added
it
would
go
and
then
again
get
the
list
item
entity
name.
So
now,
when
you
add
an
item,
you
can
actually
pass
that
in
yourself
and
the
way
that
looks
I'll
just
transition
over
here
to
the
wiki
to
show
you
guys
what
that
looks
like
here
is
say.
A
Another
thing
I
wanted
to
show
you
is,
as
part
of
the
to
auto
release,
I'm
working
on
a
set
of
articles.
This
is
the
first,
so
obviously,
I've
got
a
long
way
to
go
and
any
help
is,
of
course,
welcome
and
appreciated.
But
so
this
is
working
with
list
items.
So
this
is
going
to
be
stepping
you
through
how
to
add
items.
A
How
to
add
multiple
items
will
talk
about
batching,
we'll
talk
about
updating
the
leading
and
I
plan
to
start
trying
to
get
at
least
one
or
two
articles
like
this
out
each
week
for
the
functionality
I'm
going
to
start
with.
You
know
sort
of
list
items
kind
of
very
basic.
Everybody
needs
to
do
that
so
start
with
that
and
kind
of
branch
out
from
there.
So
folks
have
ideas
or
want
to
help
out
with
that
kind
of
documentation.
A
Certainly
welcome
that
as
well,
so
that's
kind
of
some
of
the
new
stuff
that
is
coming
in
2.0
and
that
leaves
a
little
bit
to
provisioning.
Actually
before
we
look
at
the
code,
let
me
real
quick
show
you.
So
this
is
the
new
repo.
If
you
haven't
been
here,
it's
github,
SharePoint,
PNP,
Jas,
provisioning
and
there's
nothing
in
the
master
branch,
so
go
to
the
dev
branch,
and
you
can
see
what's
here,
and
so
what's
here
to
be
very
clear
is
just
a
start.
A
This
is
me
taking
some
time
to
port
over
kind
of
what
we
had
and
simplify
it
a
little
bit
as
well
as
make
it
work
in
nodejs
and
then
also
work
with
a
lot
of
the
same
things
we
had
just
added
for
2.0
into
the
core
libraries,
such
as
the
ability
to
debug
and
some
of
the
simplified
gulp
tasks.
So
that's
all
in
the
dev
branch.
Welcome.
A
Everything
is
set
up.
This
will
look
very
familiar
to
you
if
you've
worked
with
the
Jas
core
before
got
the
debug
folder
the
gulp
tasks.
One
thing
that's
new
is
sample
schemas,
so
my
idea
is:
this
is
a
folder
that
we
could
add
sample
schemas
in
I've
got
one
here.
That's
the
one
I've
been
using
for
testing
so
at
as
I
was
going
through
and
building
out
the
various
pieces
of
functionality.
I
was
sort
of
updating.
This
schema
to
just
be
very
simple
and
for
a
way
for
me
to
test.
A
So
of
course,
you
can
have
much
more
complicated
schemas
a
note
on
the
schema.
This
does
not
match
at
all
the
the
JSON
produced
by
the
PNP
managed
code
provisioning
engine.
My
opinion
is
that
it
should,
but
to
be
super
honest
with
everybody.
I
just
didn't
have
time
to
go
through
all
that
as
I
was
sort
of
porting
this
over.
So
that's
one
thing:
I
think
the
community
could
really
do
is
begin
to
match
up
those
schemas
I,
don't
think
it'll
be
too
too
complicated,
but
just
wanted
to
be
clear
that
this
doesn't
match.
A
Necessarily
the
JSON
is
getting
output
from
the
manage
library
yet,
but
I
think
that
would
be
a
great
goal,
but
so
this
could
be
a
collection
of
sample.
Schemas
tests
got
no
tests,
but
with
the
framework
there
so
folks
can
build
out
tests
and
then
the
source
so
I
went
ahead
and
simplified
this
from
what
we
had
and
kind
of
cleaned
it
up
a
little
bit.
A
We
still
have
the
concept
of
handlers
and
I
won't
go
through
each
of
these,
but
it
follows
the
same:
what
we
had
in
the
provisioning
code
before
reprovision
a
set
of
objects
against
a
web,
and
this
in
this
case
this
is
a
composed
look,
but
what
I've
done
is
refactored
each
of
these
to
use
the
code
out
of
the
jas
core.
So
we're
calling
the
apply
theme
method
from
the
j/s
core
same
for
custom
actions,
and
we
can
look
at
features,
and
this
is
where
I
was
looking
at.
A
We
didn't
have
feature
capability,
so
we
added
that
to
the
core
library,
and
now
we
can
use
it
here
in
the
provisioning,
so
kind
of
a
symbiotic
relationship
between
those
two
libraries
and
you
can
go
through
these
other
ones.
Again.
These
are
not
done.
These
are
not
perfect.
These
are
absolutely
not
complete,
but
what
it
is
is
a
start
that
works
and
I
wanted
to
kind
of
get
that
over
here
as
a
starting
place
for
folks
that
want
to
evolve
this
and
develop
it.
A
So
I've
got
a
schema
which
is
sort
of
all
the
various
interfaces.
Folks
are
familiar
with
that
and
the
last
thing
that
really
is
kind
of
a
big
change,
I
made
and
again
as
a
starting
point.
This
will
absolutely
evolve
as
the
community
gets
involved
and
grows
this
stuff
as
this
idea
of
a
web
provisioner.
So
that
takes
a
web
and
it
takes
a
hash
of
these
handlers
and
it
takes
a
hash
of
that
is
the
sort
for
those
handlers.
A
A
This,
of
course,
can
all
be
edited
in
the
future.
So
again,
I'm
not
trying
to
say
this
is
the
end-all
be-all
of
things.
But
it's
a
start
and
to
kind
of
look
at
how
that
works.
I've
got
a
debug
file.
Setting
up
the
node
fetch
client
I've
got
a
helper
method
in
here
to
clean
up
all
the
sub-sites
as
I
was
testing.
A
This
I
ended
up
with
a
lot
of
sub
sites,
so
this
might
be
helpful
to
you
and
you
can
of
course
ignore
it
or
take
it
out
of
here
if
you'd
like,
but
then
so
the
example
is
just
a
very
simple
I'm
using
the
core
library
to
add
a
web
and
then
I'm
using
a
provisioner
to
take
that
web.
That's
just
been
created
and
then
applying
a
template
to
it.
So
I'm
importing
that
template
just
directly
here
this
template
could
come
from
doing
a
web
request
using
the
core
library
to
a
SharePoint
library.
A
It
could
come
from
a
using
some
of
the
file
system
stuff
in
node
to
read
a
template
so
stencil.
It
could
come
from
a
lot
of
places
and
this
apply
template
then
just
returns
a
promise,
so
you
could
actually
string
together.
Multiple
apply
template
calls.
Instead
of
having
one
giant
template,
you
could
have
several
small
templates
they're
a
little
bit
more
composable
and
then
do
multiple
chained
apply.
A
Template
can
you
know
calls
to
that
might
be
an
approach,
so
I'm
just
going
to
hit
f5
and
with
any
luck
this
will
run
and
what
we're
gonna
apply.
Is
this
very
simple
template
here,
where
we're
gonna
deactivate
a
feature,
we're
gonna
set
up
a
custom
action,
we're
gonna,
do
a
web
setting
and
we're
gonna
set
up
some
navigation
and
we're
gonna,
add
and
update
a
couple
of
lists.
A
A
A
You
can
see
here
it's
going
through
and
running
the
provisioning
I've
got
the
console,
logger
stuff
hooked
up,
so
it's
going
through
beginning
provisioning
of
the
web
and
then
this
is
it
just
dumping
out
the
results
of
that
provisioning.
So
if
you
look
at
my
example,
I've
then
just
this
was
again
just
be
testing
dumping
out
this
stuff
to
the
console
that
the
things
actually
happened.
That
look
at
make
sure
the
values
were
right,
but
a
little
bit
more
obvious
examples.
If
I
come
here
to
my
dev
site,
I've
now
got
a
provisioning
site
here.
A
So
that's
been
created
again.
It's
just
got
a
good
name
and
this
random
stuff
in
the
title,
but
you
can
see.
We've
got
our
navigation
nodes
here,
our
navigation
nodes
up
here
in
the
top
bar
we've
activated
the
tree
view.
We've
got
our
list
added
and
if
we
go
look
at
the
documents
list
and
if
we
look
at
that
document
or
that
library
settings,
you
can
see,
I've
updated
the
description
so
very
basic
start,
but
I
think
this
is
a
good
start
for
folks
that
are
interested
in
provisioning.
A
This
can
run
from
node
did
get
a
great
question
around.
Are
we
blocking
folks
from
using
this
in
the
browser?
And
the
answer
to
that
is
we
aren't
taking
steps
to
block
the
use
of
this
out
of
the
browser?
It's
just
not
something
we
would
necessarily
recommend
we
do
have.
The
gulp
package
still
exists,
I
kept
that
here.
So
that's
going
to
use
webpack
to
package
up
this
code.
You
can
see.
I've
got
some
some
linting
errors.
A
I
need
to
take
a
look
at,
but
this
will
package
everything
up
right
now,
I'll
tell
you:
it
includes
the
JavaScript,
the
the
pattern
practices
G
has
core
library
in
that
web
pack.
There's
reasons.
That's
good,
there's
reasons
that
that
that
are
that's
bad
I'm,
not
gonna,
sort
of
have
that
discussion
right
now,
but
so
this
could
be
deployed
and
used
out
of
a
browser,
and
it
would
work
just
fine,
but
I
do
want
to
stress.
That's
not
necessarily
or
not
necessarily
is
not
our
recommendation.
A
The
recommended
pattern
for
provision
is
still
for
now
going
to
be
calling
out
to
a
micro
service
whether
that
micro
service
is
hosted
in
node
and
uses
sort
of
this
JavaScript
provisioning,
or
whether
that
micro
service
is
hosted
in
dotnet
or
dotnet
core
and
uses
the
managed
code
provisioning
model.
It
could
also
be
something
that
has
PowerShell
involved
that
lots
of
options,
but
the
manage
code
stuff
is
way
ahead
of
what
we've
got
on
this
client-side
provisioning
stuff,
it's
much
more
mature.
It's
got
many
more
features.
A
So
that's
still
a
recommendation,
but
I'm
excited
to
see
what
the
community
can
do
and
how
the
community
wants
to
grow.
What
we've
you
know
started
out
here
in
terms
of
you
know
having
some
kind
of
node
based
or
JavaScript
based
provisioning,
I.
Think
there's
a
lot
of
opportunity
there,
but
I
do
think
you
know
it's
it's
going
to
come
down
to
really
what
the
community
and
the
energy
the
community
wants
to
put
into
growing
that
so
coming
off
that
demo.
A
That's
a
quick
preview
like
I
said
we're
gonna,
try
and
get
to
dotto
out
Friday
or
Monday.
If
I
had
to
guess
I
would
say
Monday
and
then
I
did
want
to
touch
on
one
thing.
There
was
a
question
earlier
that
asked:
is
it
a
recommendation
to
use
the
JavaScript
core
library
in
your
SharePoint
framework
projects,
and
this
is
100%
right?
It's
not
a
recommendation.
It's
not
a
thing
you
have
to
do,
or
even
necessarily
should
do,
but
our
hope
and
building.
A
It
is
very
much
the
same
hope
that
went
into
the
managed
code
library
that
it
helps
make
things
easier.
So
there's,
of
course,
no
requirement
to
use
the
managed
code,
library
and
you're
in
your
applications,
but
doing
so
makes
things
very
much
easier,
and
our
hope
is
that
it
will
have
the
same
role
and
folks
will
choose
to
use
it
if
it
makes
sense
in
their
project,
because
it
makes
things
easier
and
it
takes
out
a
lot
of
the
sort
of
repetitive
work
of
sort
of
building
up.
All
those
rest
queries
and
things
like
that.
A
So
do
encourage
its
use.
But
of
course,
absolutely
not
required.
Is
it
possible
to
use
xml
templates
like
office
PM
p
core
in
the
jas
provisioning?
If
somebody
wants
to
build
it,
it
is
absolutely
possible
right
now.
No,
but
it's
it's
really
like
I
said
it's
gonna
now
the
provisioning
on
the
JavaScript
side,
at
least
for
now.
We
could
suddenly
have
a
whole
lot
more
folks
join
the
team
tomorrow.
Maybe
that
would
happen
and
be
amazing
and
they
might
take
that
up.
A
But
for
now
it's
really
gonna
be
what
the
community
wants
to
drive,
I,
think
sort
of
the
echo
bills,
point
I,
think
JSON
is
easier
to
operate
with
in
a
JavaScript
environment
just
because
it's
JSON
and
you
don't
have
to
parse
a
bunch
of
XML.
But
of
course,
if
somebody
from
the
community
wanted
to
build
xml
support
into
the
provisioning
library,
it's
certainly
not
something
we
would
reject.
A
I
mean
again
we're
really
looking
for
that
provisioning
library
to
be
very
much
community,
driven
both
on
contributions
and
direction
and
sort
of
see
where
the
community
wants
to
take
that,
like
I
said,
what's
there
now
is
just
a
very
early
start.
You
know
something
that
I
wanted
to
get
out
there.
That
would
at
least
work
that
people
could
test
and
start
to
develop
against.
But
it's
gonna
really
fall
on
the
shoulders
of
the
community,
at
least
for
now
to
grow
that
we
can
get
the
DDF
files
back.
A
A
B
We
are
part
of
the
core
team.
We
are
the
same
guys
actually
doing
the
seat
or
implementation.
Now,
there's
a
managed
engine
and
there's
a
JavaScript
implementation
of
the
engine.
The
technologies
are
different.
Objectives
are
exactly
the
same.
There
are
use
cases
for
both
engines
and
that's
what
we
want
to
do
a
wave.
If
people
are
using
no
J's,
they
cannot
use
manage
C
sharp
version
of
the
engine,
so
we're
looking
into
just
reaching
to
the
audience
and
making
sure
that
the
the
thinking
the
remote
provisioning
engine
thinking
is
available
across
technologies.
I.
A
Think
a
lot
about
the
provisioning
is
there's
been
at
least
like
a
year,
maybe
a
year
and
a
half
of
solid
work
by
a
lot
of
folks
to
grow.
That
and
so
in
terms
of
maturity.
The
JavaScript
stuff
is
obviously
very
much
behind
in
both
capabilities
and
features
and
just
usage
out
in
the
world
and
experience
so
like
I,
said
our
recommendation.
A
My
recommendation
remains
I
know
we're
not
supposed
to
say
recommendation,
but
would
point
you
towards
using
the
managed
code
library
for
provisioning,
at
least
for
now,
but
this
is
another
option
because
we're
all
about
folks
having
options
and
working
in
the
way
they
want
to
work.
There's
a
lot
of
interest
right
now
around
node.
So
it
makes
sense
that
if
folks
want
to
grow
a
node,
provisioning
library,
I
think
that's
fantastic
and
I
would
love
to
see
that
happen
and
would
love
to
help
support
that.
D
Yeah
I
agree,
but
probably
the
main
workhorse
will
be
the
PowerShell
approach
for
the
time
being,
at
least
for
provisioning,
can
I
ask
a
question
about
Patrick
about
the
2.0
release
of
the
core
library?
Is
that
going
to
include
that
fix
for
the
promises
typings,
which
ran
into
a
bit
of
a
problem
when
you
try
to
put
a
use,
the
jazz
core
library
inside
an
SP,
FX
West
part?
Yes,.
A
Great
question
that
was
actually
the
last
milestone
to
do.
The
2.0
release
and
I
had
the
dependency
on
waiting
for
the
release.
Candidate,
zero,
so
I
could
make
sure
that
was
fixed
and
I
can
confirm,
that's
fixed
and
should
work
just
fine
with
SharePoint
framework.
That's
absolutely
our
goal
is
that
you
can
do
NPM
install
and
it
works
no
other
steps.
So
if
you
see
any
problems,
please
report
it
and
we'll
jump
right
on
that,
but
as
of
2.0,
that
should
all
be
fixed.
Yeah.
A
A
Yep,
so
we're
getting
close
to
the
end
of
the
hour.
I
thought
this
was
a
really
great
call.
I
want
to
thank
everybody
for
their
time,
appreciate
the
great
discussion
on
all
the
topics.
It's
it's
great
to
hear
everybody's
feedback
and
and
see
that
interest
and
see.
You
know
folks
minds
work
about
how
they
want
to
start
using
the
tools
and
getting
out
there.
You
know
and
getting
this
stuff
working
so
really
exciting
stuff.
Thank
you,
everybody
for
joining.
Thank
you
for
your
time.
Our
next
meeting
will
be
February,
2nd.
A
Of
course,
you
reach
out
to
us
on
any
of
the
various
social
channels
do
if
you're
interested,
please
let
myself
or
vaison
know
if
you're
interested
in
doing
a
demo
again
would
love
to
give
folks
an
opportunity
to
show
off
their
work
here
to
the
community.
So
just
let
us
know,
and
we
can
make
time
for
you
on
the
call.
So
thank
you.
Everybody
have
a
great
weekend
and
talk
soon.