►
From YouTube: PnP SPFx and JavaScript SIG Weekly Meeting 20161208
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
Whoa,
this
is
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meeting
for
December
8
2016.
It's
been
a
while,
since
we've
met,
we
skipped
a
week
due
to
the
thanksgiving
holiday
here
in
the
States,
but
we're
back
and
it's
december
eight
and
we're
excited
to
talk
about
some
good
stuff.
A
That's
coming
up
for
the
library
today
we
got
a
lot
to
go
over,
so
we'll
jump
right
in
the
folks
that
might
be
new
to
the
call
always
good
to
review
kind
of
who
we
are
and
what
we
do
were
part
of
the
larger
sharepoint
patterns
and
practices
program
and
within
that
program,
there's
a
lot
of
different
stuff
going
on,
and
so
we
came
up
with
the
idea.
A
Oh
gosh,
it's
been
maybe
almost
a
year
now
of
having
this
these
ideas
of
special
interest
groups-
and
this
was
the
first,
the
client,
scripting
or
client-side
development.
Special
interest
group
and
we've
now
expanded
that
to
include
the
SharePoint
framework,
which
is
getting
closer
and
closer
every
day
to
general
release
or
general
availability,
and
we
have
open
discussions
and
conversations
around
the
SharePoint
framework
and
those
patterns
and
and
development
practices
and
things
you
can
do
with
the
SharePoint
framework.
We're
gonna
keep
expanding
on
that
as
we
get
into
and
beyond.
A
A
Stop
shop
for
all
things:
sharepoint
development,
a
lot
of
great
information
on
getting
started
with
the
SharePoint
framework
there,
as
well
as
information
on
ad
in
development
and
classic
sharepoint
development.
So
it's
a
great
starting
point.
If
you're
new
to
SharePoint
all
up
or
if
you're,
just
new
to,
for
example,
the
SharePoint
framework,
that's
a
great
place
to
get
started,
and
it
will
walk
you
through
doing
your
first
project.
Getting
your
development
environment
setup
and
those
sorts
of
activities
so
really
great
resources
there.
A
So
moving
on
what
are
we
going
to
do
today?
We're
going
to
talk
about
the
latest
on
the
SharePoint
framework?
We've
got
based
on
the
call
with
us
to
get
an
update
there,
we're
going
to
talk
about
the
JavaScript
core
component
and
we're
going
to
do
a
community
demo,
and
you
might
notice
we've
got
a
20
number
there.
A
So
we'll
talk
through
what
that
means,
and
then
we'll
have
plenty
of
time
at
the
end
for
open
discussion,
questions
comments,
whatever
you'd
like
to
provide
feedback
on
really
that's
a
big
part
of
this
call,
as
well
as
open
it
up
to
the
community
and
getting
the
great
feedback
from
everybody,
and
if
we
could
just
double
check
everybody's
on
mute.
For
me,.
B
So
I'll
take
it
away,
so
I'll
be
relatively
short
today,
so
I
don't
have
any
fancy
slides.
It's
just
one
slide
to
get
everybody
up
to
date
on
where
we
are
with
SharePoint
framework.
So,
first
of
all
the
shipment
framework
chop
number
six.
We
actually
haven't
covered
this
in
the
past
when
y
1
20
second
of
November,
so
that's
was
around
the.
What
was
it
that
the
holiday
in
the
US
come
on.
Thanksgiving
thing
is
with
rest
of
the
world
have
right
here
and
the
the
turkey
Liberation
Day.
Wasn't
that
the
thing
Patrick
just.
B
So,
anyway,
drop
out,
six
is
live
from
22nd
of
November
and
one
of
the
things
what
we
released
as
part
of
that
is
that
the
online
workbench
is
now
available
under
the
sharepoint
online
sites.
So
you
no
longer
have
to
upload
the
work
pants
explicitly
to
your
site,
where
we
actually
using
that
and
at
the
same
time,
at
the
Developer
Preview,
was
extended
from
the
Deaf
tenants
to
first
little
previous
tenants.
B
One
thing
to
notice
on
this
one:
you
need
to
have
a
first
where
this
tenant,
so
it
doesn't
it's
not
enough
that
you
assign
an
individual
person
to
be
in
the
first,
please
note
or
mode.
The
tenant
itself
has
to
be
in
the
first,
where
this
situation
and
after
that,
you
can
then
use
the
SharePoint
framework
and
developer
preview
to
develop
stuff
in
the
in
depth
tenant
as
well,
and
really
important
to
realize
that
the
drop
number
six
is
not
yet.
B
Let's
say
final
one,
which
means
that
it's
not
ready
for
production
used
its
there
will
be
still
pregnant
changes
and
I
would
say
that
the
biggest
breaking
changes
are
coming
actually
pretty
soon,
so
really
pretty
soon.
I.
Don't
want
to
even
speculate
this
and
pretty
soon
we
will
come
up
with
a
release
candidate,
the
first
release
candidate,
and
this
will
be
announced
when
we
care
to
a
certain
threshold
of
the
tenants
in
server
sites
to
be
with
the
latest
version.
B
So
in
sharepoint
online
we
need
to
remember
that
ship
alone,
one
is
actually
massive
amount
of
servers.
So
how
we
do
our
patching
on
the
server
side
is
that
we
push
updates,
for
example,
for
server-side
SharePoint
framework
requirements
gradually
for
a
ten
percent
and
twenty
percent.
Then
thirty
percent
of
the
tenants
worldwide.
B
Still
when
we
hit
the
ten
percent
by
a
marker
around
that
time,
we
will
actually
do
announcement
that
the
release
candidate
is
coming
soon
and
it
will
be
working
gradually
within
the
first
release.
Tenants
whenever
the
the
latest
versions
are
lending
the
tenants
themselves
and
whenever
we
do
this
announcement.
B
If
you
pull
down
the
latest
packages
from
the
NPM,
it
might
be
that
those
packages
only
work
in
a
local
workbench.
But
after
your
tenant
has
been
upgraded
to
the
latest
version
within
days.
Not
within
weeks,
then,
the
online
workbench
is
working
a
propyl
as
well.
There
will
be
breaking
changes,
the
one
thing
what
we
wanted
to
do
in
here,
because
we're
still
in
the
Developer
Preview.
We
want
to
do
the
breaking
changes
or
burst
before
we
go
to
the
ga.
Ga
means
general
availability,
which
means
the
version
number
our
version
1.0.
B
So
there
will
be
pregnant
changes
as
part
of
the
release
candidate,
which
is
coming
out
soon,
like
mentioned,
but
will
pinpoint
those
needed
changes
within
the.
If
you
have
done
in
a
development
on
a
client-side
web
bots,
we
are
pretty
close
to
GA
with
the
release
candidate.
There
are
some
known
issues
which
will
be
them
call
bulbs
whenever
we
can
go
closer
to
the
ga.
B
Ga
is
happening,
well
won't
be
happening
too
far,
either,
which
is
a
good
thing,
and
we
know
immediately
when
the
release
candidate,
0
results
will
refresh
the
tutorials
the
tutorial
videos
and
also
all
of
the
samples
what
we
have
available
within
a
catan.
So
every
single
sample
will
be
out
creative
to
the
release
candidate
0
level,
because
then
you're
able
to
pull
them
down
and
they
will
work.
B
One
hundred
percent
within
your
deployment
right
now
we're
in
a
kind
of
a
disaster
situation
where
we're
chasing
always
the
latest
rope
and
then
there's
another
trope
and
then
there's
another
critical
thing
which
we
need
to
concentrate
and
we
never
get
over
all
of
the
samples
or
tutorials
in
a
fully
polished
situation.
Now
that
we're
hitting
closer
to
GA
and
we'll
do
a
bigger
push
on
updating
everything,
and
that
should
actually
make
things
fine
what
else
new
samples
under
sharepoint
kita
balkanization?
They
showed
this
different
aspects.
B
So
in
the
key
top
/
a
point,
we
have
the
SPF
FX
webparts,
so
she
open
framework
quick
pots.
There
are
new
samples
there.
I
have
a
list
on
the
following
slide
on:
what's
actually
coming
and
we're
still
all
sort
of
queuing
up
additional
articles
in
the
stuff.
That
comes
a
point
where
we
have
all
of
the
SharePoint
framework
articles,
tutorials
and
everything
else.
Whenever
the
release
candidate
0
comes
out,
it
will
take
few
days
for
us
to
really
refresh
that
guidance
as
well
making
sure
that
everything
is
up
to
the
right
level.
B
But
that's
going
to
happen
relatively
Stern.
A
few
pointers
on
the
shipment
framer
examples
and
webcast
throw
from
a
samples
perspective.
There's
few
new
angular
angular
samples
from
a
community
site
which
have
pins
up
in
it.
There's
one
new
knockout
sample,
which
is
submitted
from
a
community
site
and
then
quite
a
few
reacted
samples.
B
We
will
follow
up
on
a
certain
naming
convention
if
you
want
to
contribute
your
client-side
web
part
sample.
Please
have
a
look
on
the
on
the
contribution
guidance.
It
will
actually
tell
you
all
of
the
namings
or
the
guidance
how
how
to
submit
your
samples
available
for
other
ones
as
well
and
then
on
the
video
site.
B
There's
a
building
a
real-time
news,
feed
web
part
with
SharePoint
framework
and
maybe
the
building
Mulder
view
web
parts
with
angular
are
the
really
the
new
ones,
the
one
on
the
middle,
where
we
as
the
PMP
core
team,
talk
about
the
future
of
sharepoint
development
is
actually
pretty
interesting.
One
as
well.
I
will
pose
with
us
to
ship
one
framework
on
that
topic
and
that
discussion
as
well,
but
that's
pretty
much
the
latest
on
the
samples
and
webcasts
I'd
giving
is
asking.
B
How
do
we
want
to
handle
upgrading
the
contributed
samples
for
rare
is
candidate
Sarah?
Do
you
upgrade
all
the
samples?
So
they
do
you
notify
contributors.
So
if
contributors
are
upgrading
them,
that's
fine
as
well.
We
will
upgrade
all
of
the
samples
if
contributors
do
not
have
time
to
do
that.
So
and
it's
just
matter
of
of
having
that
discussion,
maybe
I'll
I
haven't
actually
decided
how
to
have
that
discussion.
B
Maybe
I'll
go
back
on
the
original,
pull
requests
and
add
comments
and
ask
if
people
are
people
when
upgrade
or
should
we
upgrade
either
way
huge,
but
that's
really.
The
objective
is
to
get
all
of
the
samples.
Pretty
fast
on
the
right
level
and
we'll
go
choose
at
the
same
time
the
documentation
of
the
samples
and
double
check
all
of
the
additional
settings
on
them
as
well,
so
they're
up
to
date
and
we
actually
or
and
then
we
will
have
a
easy
search
tool
for
the
SPF
examples
quite
soon
as
well.
Right
now!
B
Well,
it's
still
pending
for
final
fine-tuning,
so
you
can
actually
use
a
tool
within
the
deathbed
of
calm
to
find
all
of
the
sharepoint
framer
of
samples
which
are
out
there
rather
than
going
to
the
top
and
trying
to
find
what's
right
for
you,
but
that's
pretty
much
from
a
SharePoint
framework
site.
So
I'll
keep
it
back
to
Patrick.
A
Thank
you
know
great
stuff,
so
we're
gonna
go
through
a
little
bit
here
on
the
core
component
and
talk
about
some
updates.
Their
first
is
always
wanted
to
thank
everybody.
Dis
contributed,
Tommy
Tavella,
you've
got
a
pull
request
out
there.
I
did
want
to
mention
on
this
call
in
case
you're.
Listening
I
do
see
it
and
will
process
it,
but
I
haven't
yet
because
of
some
of
those.
A
The
work
I'm
going
to
talk
about
here
in
a
little
bit,
I've
been
focused
on
that,
and
so
don't
think
I'm
neglecting
your
pull
request
and
as
well.
Andrew
I
see
yours
as
well
so
we'll
get
to
those.
But
thank
you.
Everybody.
That's
contributed
very
much
appreciated,
so
it
really
keeps
the
project
really
alive
in
the
community
to
see
so
many
folks
joining
in
and
you
know,
participating
and
contributing.
So
what
are
some
opportunities
to
participate
in
the
SPF
X
or
the
JavaScript
special
interest
group,
so
demo,
a
SharePoint
framework
web
part
on
this
call.
A
We've
seen
that
on
the
last
few
calls.
So
if
you're
working
on
a
SharePoint
framework
web
part
and
you'd
like
to
do
a
demo,
please
just
get
in
touch
with
myself
or
visa
and
we'll
get
you
on
the
schedule.
It
might
not
be
the
next
call
necessarily
depending
on
what
else
is
you
know
in
the
in
the
pipeline,
but
we'll
definitely
get
you
an
opportunity
to
demo
your
work.
It's
really
valuable,
I,
think
for
us
and
for
everybody
to
see
what
other
folks
are
doing
with
the
framework
and
really
learn
from
each
other.
A
We've
already
seen
some
really
cool
demos
from
a
lot
of
different
folks
demo,
NE
SharePoint
pjs
related
projects,
so
we've
seen
a
great
demo
on
node
authentication
from
Sergei
two
or
six
weeks
ago.
Maybe,
but
that
was
really
neat,
but
it
wasn't
necessarily
SharePoint
framework
specific,
but
it
was
really
neat
to
see
the
usage
of
that
so
encourage
those
kind
of
demos
as
well
absolutely
contribute
on
github,
whether
it's
submitting
issues,
whether
it's
submitting
cool
requests,
things
like
that,
a
great
way
to
get
involved
and
that's
across
all
of
the
patterns
and
practices
projects.
A
Of
course,
whether
you're
interested
in
client-side
development
or
not,
and
then
of
course,
provide
feedback,
and
the
way
to
do
that
is
on
these
calls
via
issues
in
github
via
jitter
via
the
microsoft
tech
communities.
Stack
exchange
are
all
great
places
to
provide
feedback,
so
we're
all
very
receptive
to
that
feedback
and
really
try
and
be
responsive
to
the
feedback
we
get
from
folks
on
ways
to
improve
what
we're
doing
and
improve
not
just
the
library
but
the
overall
ecosystem
and
I
think
folks
that
have
been
active
in
the
SharePoint
framework.
A
Discussions
will
really
see
that
the
engineering
teams
are
very
responsive
to
that
feedback.
Pardon
me
very
responsive
to
that
feedback
and
and
really
like
to
get
that
from
the
community.
So
thank
you
so
what's
been
happening
kind
of
a
lot
so
as
the
SharePoint
framework
moves
to
GA
I've
in
the
background
been
looking
at
all
making
sure
our
library
is
aligned
very
much
to
what's
going
to
happen
with
GA.
A
So,
in
that
sense,
I've
started
updates
that
will
become
library
version,
2,
dot,
0,
and
what
that
means
in
terms
of
the
versioning
in
December
sense
of
things
is
that
it's
a
breaking
change
its
going
to
be
a
breaking
change
from
the
10
stuff.
But
it
should
not
I,
don't
think,
be
a
breaking
change
to
folks
who
are
using
the
library
in
projects.
A
So
some
of
the
things
that
are
going
to
occur
NPM
package,
the
lib
folder-
is
now
going
to
be
es6
modules,
as
opposed
is
five
and
we're
going
to
look
at
all
this
stuff
here
shortly
in
the
demo
section.
But
I
did
want
to
kind
of
talk
through
it
a
little
bit
and
then
show
it
to
you.
So
the
whole
build
pipeline
for
all
the
gulp
commands
has
been
fully
updated
and
then
that's
going
to
really
simplify
things.
I
think
for
both
developers
and
for
myself
and
others.
A
When
we
package
the
library
we've
replaced
tight
dock
with
jas
dock
and
that's
not
to
say
type
doc,
isn't
great,
but
it
doesn't
seem
to
be
getting
updated
as
best
as
I
can
tell.
I've
been
waiting
for
a
few
releases
now
for
it
to
support
of
typescript
20
and
that
doesn't
seem
to
be
coming
any
time
soon.
So
there's
actually
pull
request
sitting
out
there
for
the
type
doc
library
that
haven't
been
accepted.
So
we've
replaced
that
with
jas
doc.
We'll
look
at
that
I've
updated
the
folder
structure.
A
A
Those
actual
the
packaged
libraries
are
now
bundled
with
web
pack
and
transpile
ts5
using
Babel,
so
a
little
bit
different
approach
than
we
were
taking,
but
I
think
overall,
moving
to
web
pack
away
from
browser
Phi
and
some
of
the
other
things
has
been
a
good,
a
good
change
and
allowed
us
to
do
some,
some
better,
more
consistent
work,
I
guess,
I'll,
say
and
really
simplify
things.
So,
let's
jump
right
into
that
demo
and
I'm
going
to
try
and
get
my
desktop
presented
here.
Somebody
just
ping
the
IM
chat
there
when
that
becomes
visible.
A
Okay,
great
so
jumping
right
in
if
we
look
at
this
is
the
core
library.
The
first
thing
you're
going
to
notice
here
in
Visual
Studio
code
is
99
plus
changed
files.
So
let's
take
a
look
at
what
that
really
means
and
what
those
changes
are
whoops.
So
in
the
vs
code.
The
first
thing
we
did
is
some
updates
here
specifically
to
debug
and
so
you'll
see
that
we've
got
a
debug
task
that
now
points
to
a
specific
debug
file,
and
so
we'll
walk
through
that
here
in
a
second.
A
So
that
was
one
of
the
updates,
so
we've
got
debugging
support,
so
f5
debugging
support
Visual
Studio
code,
and
if
we
look
at
the
debug
TS,
so
this
is
sort
of
a
starting
point
for
our
debugging,
because
we
need
an
entry
point
for
these
things,
and
so
for
us,
this
debug
TS.
Is
that
entry
point
and
what
that
means
is
when
I
hit
f5.
This
is
what's
going
to
run
and
you
can
see
we've
imported
an
example
and
our
example
test
is
here.
So
it's
very
simple.
This
is
just
an
example
to
sort
of
show.
A
A
And
so
we're
getting
our
output
here,
and
so
you
can
see
we're
using
the
internal
consoles
and
we're
setting
up
the
logger
and
then
we're
going
to
run
our
example
task
here.
If
we
look
in
the
debug
console,
we
have
now
been
able
to
get
here's
our
webs
title
and
you
can
see
this
is
the
response
from
the
site.
So
you
guys
have
seen
me
do
that
a
lot
of
times.
The
real
power
now,
though,
is
I
can
actually
set.
A
My
debug
points
here
in
the
actual
you
know
code
as
well
as
go
into
the
source
folder,
and
you
can
see
already
the
the
hierarchy
is
changed
here,
but
I'm
going
to
go
into
sharepoint
and
I'm
going
to
go
into
them.
Sorry,
I'm
not
going
to
SharePoint
I'm
going
to
logger
and
I'm
going
to
look
for
the
console
logger
and
I'm
going
to
place
a
break
point
right
here.
A
So
now
I
can
actually
hit
f5
again
and
this
is
going
to
run
and
I'm
able
to
actually
debug
live
the
the
library
itself
against
sharepoint
using
the
node
request,
client
and
immediately
get
feedback
on
changes
I
might
be
making.
So
here
we've
hit
our
break
point,
for
example,
and
step
into
that,
and
then
we'll
get
to
our
break
point
in
the
logger.
So
I
can
look.
I
could
look
at
the
full
object,
I'm
getting
back
here
all
the
properties
of
that
object.
A
I
can
look
at
logger
and
all
these
different
things
and
I
hit
can
hit
go
then
I
actually
get
my
break
point
here
in
the
console
listener.
So
I
can
look
at
what's
coming
into
that.
That's
a
very
simple
example:
I
just
wanted
to
show
on
the
call
very
quickly
the
ability
to
debug
the
actual
library
as
you're
working
on
it.
So
if
you're,
adding
a
function
say
you're,
adding
something
to
web
too
I,
don't
know
create
a
group
or
something
you
can
actually
debug
that
in
real
time
now,
as
you're
working.
A
So
the
method
for
that
we've
actually
got
a
new
wiki
page.
This
is
out
there,
but
it's
not
listed
in
the
table
of
contents.
Yet,
but
it's
going
to
walk
you
through
how
to
do
this
debugging
and
set
this
up
in
your
own
environment,
and
so
the
way
I've
done
it
is
for
each
debugging
scenario
you'd
like
to
create,
you
would
add
a
file
to
this
debug
folder.
A
So
this
steps
you
through
that
entire
process
got
an
example
here
to
ensure
a
list
and
demonstrate
that
and
then
how
to
update
the
debug
TS
as
well.
So
we
also,
of
course,
still
support
in
browser
debugging.
So
we
want
to
show
that
real,
quick
and
that
is
still
supported
via
gulps
herb,
that
command
itself
hasn't
changed.
But
what
has
changed
is
we're
now
doing
this
with
web
pack
and
the
web
pack
development
server,
which
has
actually
created
a
much
more
solid
pipeline
for
when
I,
make
updates
to
my
files.
A
Web
pack
is
watching
all
my
source
files
will
rebuild
the
project
Andrey
serve
it
so
I'm,
actually
just
going
to
leave
that
running.
I'll
show
you
why
here
in
a
second
and
then
we've
got
a
section
down
here
on
debugging
in
SharePoint
framework,
so
one
really
cool
thing
you
can
do
in
SharePoint
framework.
If
you
haven't
already
is
you
can
have
external
references,
so
we've
actually
set
it
up.
You
can
set
the
external
reference
to
be
the
local
host
of
this
P&P
j/s.
That's
getting
served
soaps
partner!
Sorry!
A
So
if
you
look
we're
serving
this
at
localhost
assets,
p
and
pjs-
and
if
I
come
over
here
and
I'm
going
to
do,
I've
got
a
SharePoint
framework.
Just
vanilla
web
part,
hello,
world
project
setup,
that's
actually
just
using
sorry
just
using
a
the
library
to
show
a
random
set
of
characters.
So
we'll
get
that
running.
A
All
right
cool,
no
questions
for
me
great
so
is
this-
is
spinning
up
you've
all
seen
this
before
so
here's
my
workbench
and
I'm,
going
to
add
a
hello
world
web
part.
So
there's
my
random
string
that
super
impressive,
but
what
I
wanted
to
show
you
is,
if
I
actually
come
all
the
way
back
and
I'm
back
in
my
JavaScript
library,
local
project
and
I'm
using
the
get
random
string
method.
A
So
what
I'm
going
to
do
is
I'm,
just
going
to
say,
charge
is
charged
x
20,
so,
instead
of
getting
six
or
eight
or
whatever
I
was
doing
before
I'm
going
to
say
20
and
if
I
go
look
you'll
see
web
pack
is
now
saying
the
bundle
is
invalid.
It's
going
to
rebuild
the
bundle,
is
now
valid
and
if
I
come
back,
I'll
refresh
my
workbench
page
and
you
can
instantly
see
the
change
in
the
SharePoint
framework.
A
A
Folks,
who
you
know
are
trying
to
develop
on
both
are
trying
to
work
with
both
or
maybe
add
a
new
feature
to
the
library
that
they
want
to
work
in
SharePoint
framework
to
work
very
closely
together
and
then,
of
course,
if
I
hit
f12
you've
got
all
the
source
maps,
so
you
can
debug
the
original
typescript
and
things
from
the
library,
as
well
as
all
the
SharePoint
framework
stuff.
The
way
this
is
now
set
up
so
a
way
to
debug
everything
in
the
browser.
A
All
is
one
unit
which
I
think
is
a
really
great
improvement
to
kind
of
some
of
the
stuff
we
were
doing
before
so
I'm,
just
going
to
kill
these
servers
and
moving
on
actually
before
we
move
on.
Let
me
delete
that
so
that
doesn't
accidentally
get
left
in.
So
next
thing
I
want
to
talk
about
is
the
simplifying
of
all
the
gulp
tasks
so
you'll
see
here
a
few
of
them
have
gone
away
and
a
lot
of
them
are
still
here.
A
Some
of
you
might
remember
the
gulp
file
used
to
have
a
lot
of
different
settings
getting
plugged
into
the
global
object
and
and
honestly
that
got
a
little
confusing,
and
so
what
we've
done
is
move
this
into
a
single
configuration
file
here
under
the
gulp
tasks
older.
So
again
we're
still
building
the
banner
from
the
package
we're
still
getting
the
settings.
We
haven't
really
changed.
A
If
you
remember
each
of
the
build
configurations
was
different
using
different
TS
config
options
and
there's
a
lot
of
sort
of,
let's
be
honest,
with
ourselves:
hacking
going
on
to
kind
of
make
things
work,
so
we've
really
cleaned
that
up,
and
so
these
are
all
of
the
built
tasks.
A
But
but
one
of
the
key
differences
is
all
of
this
is
keyed
off
of
the
same
TS
config
file,
so
I
think
that's
a
really
important
improvement.
I
think
it
really
cleans
things
up
from
some
of
the
stuff
that
we
were
doing
before.
So
you
can
see
all
the
build
tasks.
Clean
has
been
changed,
but
generally
is
the
same
as
just
deleting
some
files.
Doc's
I'll,
come
back
to
in
a
second
I've
added
this
index,
which
is
actually
requiring
all
the
files,
the
gulp
tasks
folder.
A
So
if
we
actually
look
at
the
gulp
file,
j/s
we're
just
requiring
out
of
gulp
tasks,
so
this
gulp
file
itself
is
very
clean,
so
we
can
add
stuff
by
just
updating
this
index.
Linting
pretty
much.
The
same
note:
redic
changes
their
packaging
is
a
big
change.
If
you
guys
remember
the
packaging
folder
used
to
our
packaging
task
used
to
be
very
big,
had
a
lot
of
kind
of
happy
things
going
on
in
it.
So
we've
done
a
nice
bit
of
cleanup
here.
A
The
first
one
we're
packaging
up
the
definitions
so
to
make
that
happen
sort
of
cleanly.
We
still
have
to
modify
that
TS
config
a
little
bit.
This
is
the
only
place
we
have
to
do
that,
but
then
we're
running
the
gulp
source
pipeline.
You
know,
as
you'd,
expect
getting
the
Taipings
putting
them
into
the
dist
folder
and
then
now
the
big
changes
we're
using
webpack
to
package
these
things
and
with
web
pack
we're
actually
using
a
web
pack.
A
If
you
haven't
used
it
originally,
we
had
chosen
browse
if
I,
basically
at
random,
I
suppose
there
wasn't
really
a
great
reason,
one
way
or
the
other,
but
as
we've
moved
forward,
we're
doing
a
little
bit
more
now
around
web
pack
and
it
seems
to
be
a
little
bit
more
feature-rich
and
have
a
little
bit
more
flexibility
and
a
little
bit
more
sort
of
support
out
there
in
the
community.
So
not
a
knock
on
brow
safai
at
all,
but
just
sort
of
a
move
towards
web
packs.
A
I
think
it
fits
what
we're
trying
to
do
a
little
bit
better.
So
you
can
see
we're
actually
keen
everything
off
of
the
lib
folder
now
so
we're
building
everything
based
on
the
TS
config,
using
typescript
to
move
to
javascript
and
then
we're
using
webpack
to
package
JavaScript
into
a
single
javascript
file,
we're
still
producing
a
UMD
module,
we're
still
producing
the
same
variable
name.
So
this
is
what
I
meant
when
I
said
this
should
not
change
folks
who
are
consuming,
for
example,
p
and
pjs.
A
Their
life
shouldn't
change,
so
you
shouldn't
have
a
breaking
change
to
the
like
a
production
in
place.
We're
using
this
we're
still
transpiring
down
to
es5
using
babel.
One
side
effect
is.
This
has
made
the
files
a
little
bit
bigger,
but
not
so
much
bigger
that
it's
not
worth
I.
Think
the
overall
simplicity
of
configuring
things
through
these
config
files
so
update
to
the
package
task.
The
serve
task
has
also
been
updated
and
we're
now
using
webpack
along
with
the
web
pack
development
server.
Those
of
you
are
familiar
with
that
I've
become
a
big
fan.
A
You've
seen
me
demo
it
on
that
sort
of
example,
testing
project
I've
used
for
a
long
time,
but
the
web
pack
development
server
is
what
allows
us
to
do
gulp
serve
and
it
watches
the
files.
Re
serves
them
out
and
that's
all
again
powered
by
a
single
configuration
file,
helping
things
out
sort
of
making
things
a
little
bit
more
config
file,
based
as
opposed
to
sort
of
hacks
within
the
task
based
sink
still
works
exactly
as
it
did
before.
A
So
you
can
now
use
a
client,
ID
and
secret,
or
you
can
use
the
username
and
password
exactly
as
you
are
doing
before,
so
not
a
breaking
change
in
sync,
but
cleaned
up
a
little
bit
and
then
testing
has
a
bit
updated
slightly
and
we've
also
got
then
oops
on
deployment
and
then
I
have
not
written
it.
That's
why
that
article
is
not
there,
so
we're
going
to
have
an
updated
article
on
testing
and
how
to
do
that.
A
Make
that
a
little
bit
more
clear
for
folks,
because
I
think
there
are
some
confusion
before
with
running
just
certain
tests
or
running
all
the
tests.
Oh
and
the
other
page
I
want
to
show
you
is
we've
now
got
a
page,
and
you
can
see
these.
These
are
live
like
I
said
they're,
just
not
in
the
table
of
contents.
A
Yet
it
describes
each
of
these
gulp
tasks
to
help
folks
as
they're
getting
into
the
library
on
how
to
run
tests
and
how
to
run
a
single
part
of
the
tests
or
to
run
all
the
tests
and
so
as
well.
The
rest
of
the
commands
are
described
in
this
article,
so
we'll
be
updating
the
documentation
along
with
this
2
dot,
0
release.
A
So
that's
the
full
redo
of
the
build
pipeline.
One
of
the
key
differences
is
that
it
really
Keys
everything
off
of
the
lib
folder,
so
we're
getting
a
very
standardized
approach
to
everything:
sort
of
working
off
of
the
lib,
which
comes
from
straight
from
the
typescript
compiler,
which
I
think
is
a
nice
improvement
and
will
be
a
little
bit
cleaner
in
terms
of
what's
going
on
there.
A
So,
let's
talk,
then
about
I,
said
we'll
skip
over
docks,
so
we've
gone
to
j
s
dock
and
if
we
look
at
sorry,
if
we
look
at
the
docks
task,
you'll
see
it's
a
trunk.
It
been
cleaned
up
a
little
bit
and
we've
got
the
jas
dock
config
so
again
we're
moving
to
config
files
versus
having
the
stuff
buried
in
the
tasks,
and
this
is
very
simple.
I
actually
just
did
this
change
yesterday.
A
A
If
we
looking
docs,
we've
got
all
our
files
here
and
we
can
open
the
index,
and
so
you
can
see
we've
built
up,
here's
our
read
me
and
then
you
can
look
at
the
individual
classes
and
things
again.
This
is
the
default
template.
This
is
going
to
be
another
opportunity.
I'm
going
to
highlight
for
folks
to
really
help
out.
If
you
want
to
help
make
us
a
really
cool
template,
we're
going
to
have
a
separate
patterns
and
practices,
a
JS,
doc
template
project
in
github-
that's
not
there!
A
Yet
I'm
still
working
with
visa
to
get
that
established,
but
we'll
use
that
for
the
template
here
and
perhaps
other
projects,
but
that's
a
great
opportunity
for
folks
to
get
involved,
and
I
think
this
is
honestly
a
little
bit
simpler
than
type
doc
and
having
to
do
all
the
handlebars
stuff
and
whatnot,
so
we're
generating
the
docs
again
that'll
go
out
with
the
two
dot
o
release.
We
hadn't
been
able
to
update
the
docs
for
a
few
releases,
which
is
not
really
ideal.
A
So
we've
got
the
docs.
You
can,
of
course,
look
at
the
lib
folder
and
you
can
see,
for
example,
if
we
look
at
isles
no,
it's
not
really
great.
If
you
look
at
SharePoint,
so
you
can
see,
this
is
es6,
we've
got
classes
and
things
like
that
defined
so
very
much
more,
the
es6
style
of
in
the
lib
folder.
A
This
is
actually
going
to
be
a
nice
Vantage
when
webpack
20
comes
out,
there's
something
we
had
talked
about
a
long
time
ago
when
we
started
the
library
called
tree
shaking
Mike,
Morrison
I
think
was
the
one
that
brought
this
up
originally
and
at
the
time
it
was
a
great
idea,
but
it
didn't
really
have
wide
support.
So
we
didn't
really
do
much
with
it.
A
We
didn't
aim
to
not
support
it,
but
we
were
sort
of
blocked
from
supporting
it
because
node
at
the
time
we
were
on
three
dot
whatever
for
whatever
for
the
long
term,
support
version
didn't
do
es6
modules
we've
now
we're
on
node
6.9
is
now
the
long-term
support
version
and
it
does
support
es6
modules
who
are
able
to
make
this
change.
So
these
run
in
node,
exactly
as
you
would
expect,
and
then
they
will
run
when
they're
packaged
up
and
transpile
down
es5.
A
They
should
run
in
the
browser,
just
as
you
would
expect
so,
a
change
there
when
it
folks
to
be
aware
of
that.
You
will,
if
you've
got
an
older
version
of
node,
need
to
upgrade
to
six
dot
nine
dot
whatever
the
last
number
is,
when
you
do
move
to
20
once
we
release
that
to
work
with
it
locally,
but
I
am
going
to
one
of
our
wiki
articles
is
going
to
be
an
upgrade
or
a
transition
guide
for
how
to
update
your
development
environment
around
the
move
to
20.
So
talk
about
that.
A
So
let's
talk
about
the
updated
folder
structure,
so
the
big
update
the
folder
structure
is
in
sourced
sharepoint.
You
might
remember
there
used
to
be
a
rest,
folder
and
I've
gotten
rid
of
that,
because
we've
gotten
rid
of
the
provisioning,
so
it
made
sense
to
just
bounce
everything
up
a
level
and
I
did
the
same
thing
in
tests.
Everything
has
bounced
up
a
level
so
we're
out
of
that
rests
folder
that
really
shouldn't
affect
anybody.
A
But
if
folks
happened
for
some
reason
be
referencing
things
directly,
you
might
need
to
update
a
path,
but
did
want
to
make
folks
aware
of
that
as
you're.
Looking
for
things,
sorry,
I'm
in
lib.
So
if
we
look
at
source,
if
you're
looking
for
things,
it's
moved
up
a
folder.
Otherwise
everything
else
is
more
or
less
exactly
where
it
was
before.
A
So
we've
got
pardon
me
as
we
talked
about
before
great
debugging
support.
So
now
I
wanted
to
talk
about
provisioning.
As
you
can
see,
we've
dropped,
provisioning
out
of
the
core
library
and
I
wanted
to
talk
through
that.
So
folks
sort
of
understand
why
we
made
that
decision
and
what
is
is
the
future
of
provisioning
with
the
jas
core?
So
there's
a
future.
Let's
start
with
that,
but
the
reason
we
made
that
decision
is
because
we
have
a
provisioning
project
that
is
in
the
manage
c-sharp
code.
That's
been
worked
on
for
years.
A
We've
had
lots
of
great
contributions
to
that
and
is
very
mature
and
is
widely
used
and
has
a
lot
of
great
features,
as
well
as
the
partner
pack
and
other
great
examples,
and
it
works
very
well
and
sort
of
the
micro
service
format.
So
if
we
wanted
to
call
that
from
a
client-side
web
part,
for
example,
that
would
sort
of
be
the
pattern
would
be
to
put
something
in
a
queue
somewhere
and
you
could
have
a
provisioning
service
pick
that
up.
A
The
other
part
of
that
is
there's
a
very
rich
template,
a
definition
that
is
supported
by
that
sison,
provisioning
that
the
javascript
stuff
just
did
not
support.
So
we
needed
a
way
to
really
a
sort
of
take
a
step
back
and
see
what
we
wanted
to
do.
In
terms
of
you
know,
the
JavaScript
provisioning
support,
and
so
it
made
sense,
we
were
all
talking
the
the
core
team
last
week,
so
it
made
sense
to
remove
provisioning
from
here
from
the
core
library.
A
We
were
already
building
it
into
separate
JS
files
for
distribution,
which
was
a
little
confusing
and
I
think
had
a
little
bit
of
unnecessary
overlap
in
some
places,
but
we,
you
know
that
was
really
to
save
on
size
and
some
other
some
other
things
from
discussions.
You
know
way
earlier
in
the
project,
but
what
we're
going
to
do
moving
forward,
because
we
do
think
there
is
a
story
that
we
want
to
support
around
folks
that
want
to
do
provisioning
from
node
and
I
want
to
be
very
kind
of
specific
about
that.
A
We
do
not
think
and
do
not
encourage
or
recommend
provisioning
in
quotes
from
a
browser
session.
For
example,
most
of
those
things
just
take
too
long.
Folks
might
navigate
away
from
a
page
who
knows
right,
so
this
would
really
be
around
provisioning
from
node.
So
if
you
wanted
to
make
a
node
service,
you
call
back
to
to
do
provisioning,
so
we're
going
to
have
a
separate
library
and
github
for
provisioning
and
so
I've
preserved
all
that
code.
A
We're
gonna
art
with
that
as
a
starting
point,
but
our
goal
with
that
is
going
to
be
a
parity
in
the
sense
as
much
as
possible
with
the
the
sea
psalm
provisioning
library.
So
our
aim
would
be
to
support
the
same
types
of
the
same
templates
and
do
as
much
of
the
same
actions
as
we
can
in
the
same
ways.
A
That's
going
to
be
challenging
and
I'm
going
to
sort
of
challenge
the
community
a
little
bit
that
we
are
looking
for
folks,
who
are
interested
in
being
heavily
involved
in
that
effort
to
write
out
that
provisioning.
It's
something
it's
going
to
take
time
and
we're
going
to
need
help
to
do
it.
So
if
the
community
is
interested
in
it,
we
like
I,
said
we're
going
to
create
this
library
that
separate
that's
gonna.
You
know
again
have
an
NPM
release
all
these
things
and
will
enable
that
infrastructure.
A
But
we're
really
going
to
be
looking
for
the
community
to
jump
in
get
involved
and
really
help
expand
the
provisioning
story
in
the
JavaScript.
If
that
something
people
are
interested
in
having
and
using
so
we're
kind
of
going
to
let
people
vote
you
know
with
their
with
their
pull
requests
in
this
sense.
It's
not
something
that
right
now
the
core
team
has
folks.
We
don't
really
have
folks
in
general,
but
the
folks
on
the
core
team
aren't
going
to
have
time
to
100%
build
this
out.
A
The
folks
that
are
doing
provisioning
are
already
in
spending
that
time
in
the
sea,
psalm
library.
So
I'm
going
to
put
that
challenge
out
to
the
community
that,
if
folks
are
want
that
provisioning
story
for
node
in
javascript
help
us
build
that
out
and
we
will
support
it
and
you
know
help
with
the
infrastructure
and
those
sorts
of
things.
So
you
know
do
please
give
us
feedback
on
that
idea.
A
Let
us
know
you
know
if
you
want
to
help
absolutely
want
to
get
you
lined
up
to
help
and
we'll
get
that
new
repo
set
up
here
in
the
coming
weeks,
so
we'll
get
that
set
up
helm.
So
the
provisioning
is
not
going
away,
we're
not
just
dropping
it
cold,
but
we
are
removing
it
from
the
core
library
so
yep.
That's
all
I
have
to
really
say
about
that.
If
you
have
questions
or
comments
like
I
said,
get
er
any
of
the
other
feedback
channels
are
great.
A
So
a
couple
of
things
that
I
haven't
mentioned:
we
used
to
have
a
thing
about
adding
use
strict
to
all
the
files.
That's
no
longer
needed,
so
I've
taken
that
out
everywhere.
Just
a
little
note,
so
don't
worry
about
that.
We're
updating
the
wiki
articles,
one
thing,
there's
an
issue
out
there
and
it's
something:
I've
been
working
with
the
product
group
on
now
for
a
little
bit
is
there?
A
So
if
you
were
to
add
right
now
the
library
to
a
SharePoint
framework
project,
you're
going
to
get
some
build
errors
around
duplicate
types
around,
like
things
related
to
fetch
response
and
an
HTTP
in
it,
and
things
like
that,
so
that
is
still
being
worked
out,
but
we're
going
to
get
that
worked
out
one
way
or
another
for
to
auto
of
our
library
and
GA
of
the
SharePoint
framework,
such
that
when
SharePoint
framework
is
at
GA
and
we're
at
20,
you
will
be
able
to
just
install
and
use
the
core
library,
and
that
issue
will
not
be
an
issue
anymore.
A
So
just
a
heads
up
I
wanted
to
sort
of
mention
that,
because
that
issues
been
out
there
for
a
while
that
it
hasn't
fallen
off
the
radar,
and
so
that's
the
demo
and
that's
the
conversation
of
everything
so
now
I'll
just
open
it
up
to
questions
comments,
feedback
things
like
that.
I
know:
I've
just
talked
about
a
lot
of
changes
and
I
know
it's
not
in
I.
Haven't
committed
it
yet
so
folks
haven't
had
a
chance
to
look
at
it
but
open
to
any
questions.
10
20
be
available.
A
So,
to
not
oh
very
soon,
and
really
the
only
blocker
is
what
I
just
talked
about,
which
is
working
out
that
issue
with
the
Taipings,
so
that
when
you
install
the
library
and
a
SharePoint
framework
project,
it
just
works.
That's
an
active
discussion
I'm
having
with
the
engineering
team,
were
we
I
think
we
know
what
we
need
to
do
it's
just
a
matter
of
getting
it
going.
Can
you
provide
a
github
link
to
the
debugger
documentation?
I
can?
A
But
if
you
go
to
the
wiki,
it's
actually
just
in
the
wiki
you'll
have
to
do
expand
the
pages,
and
you
can
see
debugging
like
I
said
it's
not
in
the
table
table
of
contents,
but
there's
the
link
for
you
there.
Hopefully
you
can
see
that
and
then
and
we'll
update
the
table
of
contents
I'm
going
to
kind
of
refresh
the
whole
wiki
with
the
two
da
no
release.
A
Yes,
that's
kind
of
when
I
found
time
to
do
a
lot
of
this
stuff
so
but
I
think
valuable
for
the
community
to
kind
of
get
this
done
and
one
other
thing
I
can
mention
on
the
wiki
article.
We've
also
got
a
deployment
article
now
that
talks
a
little
bit
more
explicitly
about
deploying
these
things
to
production,
so
talks
about
bundling
in
CD
ends
and
then
I've
also
added
a
part
here
about.
If
you're
again
mention
those
externals
and
SharePoint
framework,
you
could
set
the
spp
and
pjs
appointed
hour,
CloudFlare
CDN,
so
you'll
notice.
A
A
A
B
Unfortunately
unchanged
we
it
well
at
least
for
now
in
the
release
candidate
2017,
there
won't
be
any
native
capability
for
clients
at
backbones.
Unfortunately,
it's
a
decision
on
the
visual
studio
side.
So
so
we
would
strongly
recommend
to
learn
those
few
of
those
neutrals
they're.
Not
our
super
super
difficult
to
learn
anyway,
but
things
are
what
they
are.
Yes,
I
do
agree
on
that
comment.
Ooh
yeah,.
B
A
The
so
Kevin's
point
I
really
hope
the
node
provisioning
get.
Some
traction
will
be
happy
to
contribute.
Like
I
said,
we
are
fully
supportive
of
it
getting
subtraction,
but
it
is
going
to
really
rely
on
the
community.
I
wanna,
again
sort
of
put
that
out
there
and
challenge
folks
that
if,
if
the
node
provision
is
something
you're,
you
know
once
and
passionate
about
we're
going
to
be
relying
heavily
on
the
community
to
build
that
out.
A
You'll
have
our
support
like
if
you
have
questions
about
how
something
in
the
seesaw
stuff
works
or
something
about
the
the
template
structure.
Things
like
that
I
mean
we're
here
to
help,
but
it's
not
something
anyone
the
core
team
is
right
now,
I
mean
unless
we
get
our
mythical
staff
given
to
us
which
fingers
crossed
every
day
that
I
get
a
staff
that
shows
up
hey
you.
A
Number
of
times
people
ask
if
I
could
get
by
spike
my
team
to
work
on
something
I
kind
of
look
around
my
room
here.
I
go
okay,
but
you
know
it's
something
like
I
said:
we're
not
dropping
it
cold.
We're
gonna,
create
this
other
repo.
Get
it
set
up,
get
the
NPM
package
make
sure
it
works.
You
know
with
the
library
things
like
that,
so
we
will
support
that,
but
it
is
good,
rely
very
heavily
and
entirely
on
community
wanting
to
and
building
that
out.
A
So
that's
that's
going
to
be
the
state
of
that.
So
folks
are
interested.
It's
going
to
be
a
thing
and
if
nobody
cares
to
contribute,
unfortunately,
it's
it's
going
to
kind
of
languish
for
a
little
while,
that's
just
that's
just
to
be
the
truth
around
that
question
from
tech
community
will
see
some
system
that
update
we
changed
not
start
or
closed.
I,
don't
know.
B
Lisa
I'll
unmute
myself.
Yes,
so
there
is
a
separate,
a
separate
method.
So
there
is
a
as
part
of
the
November
release.
We
introduced
the
system
update
without
the
version.
Whatever
the
method
name
is,
if
you
call
that
one,
it
doesn't
start
work
force,
the
update
itself
does
and
actually
system
update.
Actually
does
that
it's
it's
pretty
weird
thing.
We
have
actually
tree
item
update
methods
nowadays
in
the
client-side
object
model
in
server
side,
I
think
we
have
even
one
more
in
the
concert
object
model.
B
We
have
the
typical
update,
we
have
system
update
and
then
we
have
this
new
one,
which
was
released
as
part
of
the
November
to
address
that
explicit
scenario,
but
your
Russell
are
asking.
So
how
do
we
actually
update
item
without
causing
a
new
version
to
be
created
and
that
it
doesn't
actually
start
to
work
flow
and
that
you
can
still
overwrite
the
modified
by
you
modify
that
and
all
of
that,
the
information?
If
you
have
sufficient
permissions.
B
Yes,
well,
technically,
what
we're
doing
is
that
we're
just
exposing
existing
methods
which
are
on
the
server
side.
Client-Side
object
model
is
just
the
wrapper
on
calling
existing
methods,
we're
not
actually
implementing
anything
new.
So
if
we
still
have
one
more
systematic
efforts,
we
have
an
exposed.
That's
always
an
option.
A
Twenty
second,
I'm
not
actually
working
that
day,
but
I
am
going
to
join
this
meeting
because
that's
how
much
I
care-
and
so
the
vase
I
can't
make
fun
of
me
for
having
another
day
off
this
year,
and
then
we
will
be
that'll,
be
our
last
meeting,
obviously
for
the
year
and
then
we
will
reconvene
in
2017,
which
is
scary,
just
say
that
so
but
next
meeting
december,
twenty
second,
which
will
be
the
beginning
as
per
the
normal
schedule.
A
So
I
know
we
skip
the
last
meeting
prior
to
this
one,
but
the
next
one
would
be
on
schedule
as
expected.
So
see
you
guys
december
twenty
second
and
then
that's
all
I've
got
for
this
week.
So
thanks
everybody
keep
the
great
feedback
coming
we're
looking
forward
to
the
two
dot
o--
release
and,
like
I,
said
the
provisioning
stuff
and
all
that
do
look
forward
to
hearing
your
feedback.
A
I'll
probably
get
a
pull
request
submitted
around
all
my
20
changes,
so
folks
can
have
a
look
and
give
feedback
by
the
end
of
this
week,
but
won't
merge
it
until
we're
able,
like
I,
said,
to
resolve
the
type
stuff
on
sharepoint
framework.
So
that's
all
got
for
this
week.
So
thank
you.
Everybody
have
a
great
weekend
and
talk
soon.