►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 17th of January. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
Demos:
- David Warner II - How to optimize SharePoint Framework extension performance with dynamic loading of CSS styles
- Stefan Bauer - PnP/SPFx 1.7 Jest, webpack analyzer, style linter
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
Welcome
everybody:
this
is
to
SharePoint
framework
and
JavaScript
special
interest
group,
and
this
is
the
PI
weightless
sync,
we
kind
of
talked
about
SharePoint
framework
and
JavaScript
and
JavaScript
type
development
in
the
context
of
SharePoint
or
in
the
context
of
office
365
in
general,
and
basically
the
topics.
What
we're
covering
through
here
is
all
around
SharePoint
framework
and
JavaScript
based
customizations
in
the
SharePoint
Online,
and
then
we
have
a
separate
special
interest
group
call
for
all
of
the
rest
of
the
topics
so
on
the
separate
channel
in
general
SharePoint
at
depth.
A
Special
interest
group
we're
talking
about
stuff
like
provisioning,
see
some
seasoned
core
which
is
coming
by
the
way,
but
Nadia
and
Flo
and
power
apps
and
all
of
those
kind
of
customization
site,
designs
and
and
column
formatting
and
all
of
those
in
here
we
concentrate
on
the
SharePoint
framework,
which
is
absolutely
de
facto
way
of
doing
a
UI
customizations
in
SharePoint,
and
then
the
other
side
is
also
the
additional
JavaScript
customization
models.
Now
the
structure
always
in
this
course
is
pretty.
Let's
say,
static,
well,
not
static,
but
we
always
go
through
quickly.
A
The
engineering
updates
on
a
SharePoint
framework
and
then
we
go
through
the
actual
updates
on
the
open
source
project,
so
that
means
P
NP
chase
updates
office,
365
CLI
updates,
SPF
X,
reusable
controls,
BMP
yeoman,
generator
updates.
If
we
have
owners
of
these
projects
in
the
call
they
will
actually
culture
the
slides,
if
you
don't,
we
are
gonna,
go
through
the
slides
or
whoever
is
presenting
now
and
then
we
always
have
at
least
two
community
demos,
while
they
might
be
engineering
demos
as
well,
but
at
least
through
demos,
and
then
hopefully
time
for
the
Q&A.
A
Good
socialites,
I'm
working
I'm
double
checking
on
that
I
am
discussion,
what's
actually
happening
there.
Now,
let's
actually
move
on
on
the
topics,
and
let
me
activate
that
slides
and
here
we
go
so
few
reminders,
opportunities
for
participating
on
the
BMP,
TAS
or
BMPs
BFX,
well,
the
SharePoint
framework
and
JavaScript
special
interest
group.
A
So,
if
you're
interested
on
doing
a
live
demo,
here,
please
reach
out
and
actually
technically
are
already
our
next
SPF
X
call
is
already
fully
booked,
but
we're
looking
into
obviously
booking
you
a
10
to
15
min
a
spot
to
do
a
live
demo
I'm,
showing
something
cool,
showing
our
contribution,
showing
something
what
you've
done
for
the
community
as
an
example
in
SPF,
X
context
or
in
the
p.m.
PJs
context.
What
then
contribute
in
a
key
top?
A
If
you
don't
feel
that
will
if
you
don't
feel
that
you
want
to
actually
actually
do
a
live
demos
in
those
of
course,
you
can
always
contribute
in
a
github
on
the
existing
samples
or
provide
new
samples
as
well,
and
the
most
important
thing
always
provide
feedback.
So
you
don't
be
the
person
who
it's
just
frustrating,
because
something
isn't
working
tell
us.
What
are
you
looking
for
and
used
the
community
channels
and
also
our
SPF
github
issue
lists
for
telling
if
something
is
program,
so
we
can
actually
help
you.
That's
super
important
as
well.
A
Moving
on
are
things
so
this
is
the
chiffon
framework
section
where
I
will
hand
over
encodes
the
the
the
speaking
turn
at
today
saw,
which
is
also
me,
but
in
this
case
now
that
Patrick
is
still
having
problems
of
getting
in
I
will
take
over
one
verse
with
this
one
and
the
other
sections
as
well.
Please
remember
to
mute
yourself
by
the
way
record
knows
which
is
causing
some
challenges.
A
Here
we
go
so
a
quick
updates
on
the
SharePoint
framework
engineering
science,
so
nothing
too
traumatic
all
here,
but
I
wanted
to
actually
quickly
update
on
the
resources.
What
we
were
having-
and
we
actually
did
really
is
something
really
cool.
Just
15
minutes
before
this
call
so
SharePoint
abducts,
akms,
SPF,
Docs,
SharePoint
videos,
a
km
SSP
their
videos
and
upon
dev
issues,
a
game
SSP
dev
issues.
That
should
be
relatively
easy
to.
Remember
remember:
those
are
then
getting
redirected
on
the
latest
URLs
where
we
are
collecting
that
information.
A
So
that's
the
the
learn:
how
to
do
SharePoint
framework
development
and
see
the
demos
of
SharePoint
framework
development
and
then
also
report
any
developer,
oriented
issues.
Please
use
the
issue
list
which
we
have
in
Akita
and
the
main
point
of
that
one
is:
please
use
the
issue
list
in
the
SP
dev
Docs,
where
that
URL
is
redirecting,
because
if
you
go
to
a
random
repo
in
the
SharePoint
github
organization,
just
like
60
repositories
there
and
then
you're
adding
an
issue
in
a
random
repository.
It
might
be
that
we
are
not
aware
of
your
issue.
A
So
that's
why
we
recommend
people
to
use
two
SP
dev
dogs
as
a
centralized
location
for
all
of
your
input,
now
something
what
I
promised
something.
What
I
mentioned
already
that
something
really
cool
which
we
announced?
Actually,
ten
minutes
before
this
call
so
I
pushed
out
the
blog
post,
which
had
a
small
type
line,
indent
which
is
now
fixed,
but
we
released
a
new,
very
updated
ship
on
framework
developer
training
package,
which
is
now
available
for
you
to
take
advantage.
Sandviches
and
that's
probably
Patrick
Patrick.
A
A
So
what
are
those
and
how
do
we
actually
work
and
then
leveraging
marks
of
Graff
and
third
party
API?
So
it's
really
cool
about
this
bucket.
Is
that
we're
now
providing
a
set
of
videos
for
all
of
those
modules,
we're
providing
you
hands-on
labs,
we're
providing
you
demos
and
for
the
modules
and
obviously
the
presentation.
A
So
you
can
either
use
this
material
to
learn
by
yourself,
but
if
you
are
actually
a
trainer
or
if
you
one,
if
you
are
a
senior
team
lead
and
you
want
to
teach
a
material
on
or
let's
say,
SharePoint
framework
development
for
your
team
members,
you
can
absolutely
do
use
this
material
as
well.
So
this
is
all
for
you
to
reuse
any
way
you
want.
So
so
that's,
basically
you
can.
You
can
use
it
and
the
material
in
conferences.
You
can
use
it
in
your
trainings.
A
You
can
redeliver
this
training
anyway,
one
and
it
likes
that
there
are
videos
available
and
they
will
show
you
how
to
redeliver
or
if
you're
going
through
them
only
to
learn
the
SPX
development.
Those
videos
are
extremely
useful
for
you
as
well.
So
videos
are
in
YouTube
most
likely.
We
will
actually
put
the
videos
in
the
Microsoft
virtual
academia
at
some
point
as
well,
and
just
this
is
super
super
fresh
from
the
oven
today
released
maturity
of
those
videos,
those
six
months
for
the
six
modules
and
I
think
we're
looking
into
I.
A
Think
it's
roughly
45
minutes
per
module
six
times.
45
minutes
is
like
six
hours
or
six
and
a
half
hours,
or
something
like
that.
If
my
math
is
even
close
correct
now,
so,
if
you're
looking
into
getting
started-
and
this
will
be
highly
beneficial
for
you
and
and
so
have
a
look
on
that-
give
us
feedback
and
if
something
is
missing
a
no-bail.
So
we
keep
on
updating
this
material
in
a
quarterly
basis
as
well
and
and
we
will
keep
on
adding
new
modules
to
this
package
as
well.
A
So
everything
should
be
up
to
date
and
again,
a
reminder.
Please
meet
yourself.
We
once
again
cut
a
background
noise
from
somewhere
I
can't
find
a
reason
for
the
background
noise.
Oh
there,
it
is
okay!
Thank
you!
Oh
yeah,
so
yonas
comment
there.
So
technically
it's
not
a
typo.
It's
it's
a
reminder
for
myself
to
update
that
section
and
I
forgot
about
updating
that,
because
I
was
trying
to
get
ready
for
this
call,
the
the
section
has
been
updated,
but
funny
enough
and
I'm
pretty
sad
about
this
one.
A
This
is
a
sad
story
which
I
shouldn't
tell
there
is
a
caching
in
the
in
the
SharePoint
dev
blog
and
it
will
take
a
while
to
actually
get
that
section
updated.
So
the
update
is
already
pushed
out,
but
there
is
a
caching
which
is
delaying
that
final
piece
on
the
on
the
already
called
getting
updated.
So
that's
on
me
and
that's
fine
now
take
advantage
of
this
one
give
us
feedback.
We
will
keep
on
evolving
this.
We
need
to
know
what
you
need.
A
That's
that's
the
super
important
thing
to
let
us
know
so
anything
related
on
which
we
should
be
improving
around
the
SharePoint
community
community
work,
the
material
documentation,
and
all
of
that
please,
please,
please
let
us
know,
and
we
can
actually
address
those
unless
we
know
we
do
not
know
how
we
can
help
you.
Thank
you
now,
quick
update
on
on
the
numbers,
so
on
the
SharePoint
framework
site.
Obviously,
there
was
a
big
chop
during
holiday,
which
is
completely
understandable.
There
was
a
holiday
break
and
a
relatively
long
holiday
break,
which
was
around
two
weeks.
A
We
were
kind
of
in
this
Christmas
and
New
Year
section
in
the,
and
that
obviously
is
causing
the
top,
but
now
we're
back
online
and
it's
pretty
interesting
to
see
that
the
growth
on
the
left
side,
which
is
to
users
for
users
per
user,
is
completely
linear.
Linear,
from
the
perspective
that
we
would
be
theoretically
able
to
predict
what's
happening
or
where
the
numbers
are
by.
Let's
say
end
of
June
or
something
like
that,
and
but
the
users
is
growing
tremendously.
A
The
tenants
usage
is
growing
tremendously,
there's
a
growing
interest
of
using
SharePoint
framework
and
getting
shape
on
framework
on
the
store.
We
are
actively
working
on
that
one
as
well.
So
if
you're,
an
ISV
or
individual
developer,
you
are
able
to
in
the
future
to
push
stuff
and
your
components
to
the
app
source
and
also
the
actual
store
where
people
are
equal
to
then
install
them
good.
A
A
This
is
not
advanced,
so
you're
able
to
catch
on
how
to
do
that
kind
of
a
development
how
to
do
share
one
framework
now
the
final
thing
which
I
updated
that
slide
this
line
just
slightly,
let's
see
if
somebody
can
actually
spot
the
section
and
which
are
updated,
it's
more
a
for
a
smiles
but
I
didn't
there's
no
actual
news
since
the
two
weeks
ago.
So
the
SharePoint
SharePoint
is
one
is
their
SharePoint
framework.
1.8
is
gonna,
go
live
for
the
first
quarter
of
this
calendar
year.
A
We're
looking
into
I
would
say:
it's
gonna
go
for
the
last
third
of
the
first
quarter,
which
basically
then
means
roughly
on
March
so
but
I
can
give
you
an
exact
date
at
this
point,
because
obviously
we
have
a
target
date,
but
we
don't
want
to
tell
you
that,
because
so
that
you
wouldn't
actually
take
that.
That's
a
promise,
and
if
we
delay
for
a
week
or
two
you
will
feel
bad,
but
it
will
be
roughly
on
March
timeframe
and
I
can't
be
more
precise,
like
that.
A
The
main
point
in
the
1.8
is
the
development
and
GA,
so
public
availability
of
Microsoft
teams
tab
development
using
SharePoint
framework.
So
we
are
currently
executing
a
kind
of
a
in
da
preview
program
with
some
of
our
partners,
making
sure
that
everything
is
actually
up
to
date
and
working
properly
and
and
it's
gonna
be
released
as
part
of
1.8.
If
there's
no
last-minute
massive
critical
surprises
and
then
obvious,
the
store
thing
is
bubbling
under
ship
and
framework
apply
for
a
package
support
coming
at
some
point.
We
already
have
plans
from
1.9.
A
You
can
predict
that
the
1.9
version
will
be
roughly
released.
There
is
a
few
big
conferences
coming
up
on
the
on
the
later
the
spring,
the
SharePoint
Conference
2019
mean
being
at
the
most
important
forum
for
SharePoint.
So
you
can
pretty
much
predict
at
one
point.
Nine
will
be
released
right
about
that
timeframe.
Is
it
before?
Is
it
after
I
can
promise
anything
at
this
point,
but
it's
coming
anyway,
updates
are
coming
now,
I
think
that's
it
for
engineering
updates.
B
Thank
you
so
quick
updates
across
the
PNP
libraries
and
we'll
get
to
those
demos
certain
vase
of
mentioned
earlier
in
the
call
the
PJs
client-side
libraries,
a
one
to
eight,
was
released
last
Friday,
so
check
that
out
update.
If
you
get
a
chance
and
we
do
continue
beta
releases
pretty
regularly,
usually
on
Fridays,
but
sometimes
midweek.
If
we
find
an
issue
and
there
are
trying
to
help
somebody
out
so
keep
an
eye
out
for
those
a
reminder,
we're
thinking
about
the
to
ATO
roadmap
issues
or
roadmap,
you
know
planning.
B
So
if
you
have
ideas
for
to
datos,
that's
a
good
opportunity
for
us
to
make
some
breaking
changes.
Very
much,
encourage
your
feedback.
There's
I!
Think
for
now
issues
in
the
list
marked
with
the
roadmap
label.
You
can
certainly
comment
on
those
or,
if
you
have
your
own
ideas,
absolutely
welcome
those
as
well
just
submit
an
issue
mention
you
know
it's
a
roadmap
idea,
we'll
get
it
make
sure
it
gets
labeled
correctly
and
include
that
in
our
planning
and
we
do
not
have
a
target
date.
B
Yet
for
that,
so
we're
not
in
a
super
big
hurry,
but
it'll
be
sometime
in
2019,
we'll
probably
do
a
2.0
release
just
a
reminder
if
you're
submitting
issues
please
do
please
just
share
as
much
as
you
can
about
the
issues.
I
think
we
say
this.
We
say
that
a
couple
times
a
year
but
we're
starting
to
get
a
few
issues
that
come
in
and
you
know
folks
are
just
sort
of
saying
it's
broke.
B
I
expected
the
call
to
work
right
and
that's
just
not
really
enough
detail
for
us
to
to
dive
in
and
help
you
out
and
fix.
So
please
share
as
much
information,
especially
the
actual
code.
That's
running
can
be
a
big
help
with
us
fixing
issues,
because
we
want
to
help
and
remember
your
your
coming
to
us
and
asking
for
help
and
we
want
to
help.
B
B
Don't
reopen
open,
a
new
issue
and
we'll
be
sure
to
get
you
sorted.
So
sorry
about
that
definitely
was
confusion
on
my
part
or
a
misunderstanding,
and
not
me,
you
know
trying
to
ignore
folks.
So
sorry
about
that,
but
please
just
open
a
new
issue
if
you're
still
having
the
same
trouble
and
we'll
make
sure
to
get
that
addressed
and
then,
as
always,
I
want
to
say
thank
you
to
everybody
that
has
contributed
really
seen
a
great
jump
in
the
contributions
and
really
appreciate
that
from
everyone,
the
link
down
there
to
the
documentation.
B
So
we've
got
the
documentation.
There
are
P
and
P
github
got
I
Oh,
/p,
n
PJs,
hash
tag
p.m.
PJs
on
Twitter
and
then
at
mediocre.
Bowler
is
me
on
Twitter,
if
you'd
like
to
follow
me,
I
generally
I'm
just
posting
about
p.m.
PJs
related
stuff.
So
you
can
follow
me
for
the
latest
updates
there
and
to
Vincent's
point
I
didn't
I
went
looked
and
I
did
not
see
an
issue.
I'm
sorry
I
see
a
setting
to
control
that
so
maybe
I
missed
it.
B
B
You
sure,
but
I
didn't
see
a
setting,
so
if
somebody
knows
about
a
setting
I'm
happy
to
get
that
flip,
so
folks
can
reopen
their
issues
but
anyway,
sorry
about
that
for
the
open
issues,
thanks
to
everybody,
for
the
contributions
very
much
appreciate
it
and
look
forward
to
continuing
the
journey.
B
So
office365
CLI
update
new
version.
1.13
zero
is
now
updated
and
building
on
all
the
previous
versions
and
adding
the
ability
to
add
users
to
microsoft
teams
teams
so
folks
can
join
a
team.
You
can
add
folks
to
a
team
in
progress.
You
can
listing
sites
associated
with
hub
sites,
retrieving
site,
script
from
lists
and
then
more
commands,
of
course,
and
always
waiting
for
your
suggestions.
B
Of
course,
Waldeck
and
team
is
very
open
to
hearing
from
you
in
the
CLI
and
that's
across
all
our
projects,
of
course,
always
appreciate
the
feedback
and
ideas
you
can
install
the
latest
version
by
NPM
install
G
at
PNP
office,
365
CLI.
You
can
follow
the
AKA
ms3
65
CLI,
link
for
more
information
and
details
on
the
documentation.
You've
got
a
hashtag
office,
365
CLI
on
Twitter,
there's
a
git
er
Channel
and
as
well
that
linked
to
the
documentation
for
the
CLI.
B
So
if
you
haven't
used
a
CLI
check
that
out,
it's
a
great
cross-platform
solution
for
folks
that
maybe
can't
use
PowerShell
prefer
not
to
use
PowerShell
for
whatever
reason
so
check
that
out
a
lot
of
great
capabilities
and
that's
a
great
place.
If
you're
looking
for
somewhere
to
get
involved
in
the
PEP
program,
it's
a
great
place
to
jump
in
is
each
command
is
fairly
atomic,
so
you
can
work
on
a
single
command
and
really
get
that
polished
up
updates
on
the
reusable
components.
No
big
updates.
B
Since
the
last
call,
we
do
have
some
issues
out
there
and
some
things
that
will
get
worked
on
shortly.
We've
had
folks
have
had
some
conflicting
priorities
and,
with
you
know,
things
like
real
job,
so
that
is
been
the
focus
for
folks,
but
will
be
coming
back
and
getting
some
updates
in
over
the
next
couple
of
weeks
for
the
reusable
controls.
But
if
you
haven't
check
these
out
be
sure
to
for
your
SP
FX
projects,
it's
really
gonna
save
you
a
whole
ton
of
time.
There's
two
sets
of
controls.
The
first
are
property
controls.
B
These
work
great
in
the
Edit
pane
for
your
webparts
and
you've
got
content
controls
which
work
great
in
the
body
of
your
webparts
to
display
data,
display
images,
maps,
graphs,
things
like
that,
so
very
cool,
very
powerful
and
all
styled
using
the
office
UI
fabric.
So
you're
gonna
get
a
nice
out-of-the-box
to
look
around.
B
You
know
your
controls
are
gonna
blend
in
very
nicely
with
the
out-of-the-box
stuff,
without
a
lot
of
work
on
your
part,
so
you're
just
gonna
get
that
right
out
of
the
reusable
controls
box,
and
some
recent
highlights
was
added
to
map
control,
some
truck
controls
and
working
on
constant
improvement.
So
if
moved
for
performance
and
excuse
me
and
usability
on
the
controls,
so
definitely
check
these
out
two
links
down
at
the
bottom
for
more
information,
SP
dev,
FX,
property
controls
and
SP
dev
effects.
Controls
react
so
be
sure
to
check
those
out.
B
C
So
they
released
version
1.6,
and
this
has
a
lot
of
new
capabilities
like
we
already
have
got
tasks
in
there
for
the
Deaf
back
panel
analyzer
for
the
linting
of
the
CSS
styles
that
we
have
in
your
web
part.
We
include
the
styling,
which
is
a
tool,
that's
pretty
popular
in
the
web
development
world,
and
now
you
can
actually
do
linting
on
your
CSS
and
on
your
sass
files
to
be
more
specific
what
they
have
in
there.
C
We
also
have
upgraded
the
reference
for
F,
P,
P,
P,
P
chess
to
one
point
two
point:
eight
and
the
property
controls
for
all
projects
are
still
currently
in
one
point:
thirteen
point
one
because
there's
nothing,
there's
no
new
version
out
there,
and
especially
for
react.js
projects.
What
we
actually
do
is
thanks
to
the
help
of
invokana
land
and
verrano's.
We
now
include
directly
presets
for
chest
unit
testing
of
your
react.js
reference
and
for
the
in
progress.
What
we
actually
plan
in
in
the
future
is
that
we
have
support
that
you
add
this.
C
Functionality
is
also
to
existing
projects
and
I
will
talk,
is
in
the
end
in
my
demo,
a
little
bit
later
when,
when
you
actually
see
how
this
all
works
and
fit
together,
what
we're
actually
planning
the
in
the
future.
So
the
install
this
generator
just
use,
NPM,
install
G
@
PP,
generator
st
effects,
and
if
you
want
to
have
more
documentation,
you'll
find
more
information
on
our
github
page,
and
that's
all
for
my
side.
For
now,.
B
D
D
Fantastic,
alright,
so
here's
my
contact
information
I
know
a
lot
of
you
folks
on
here
so
feel
free
to
reach
out
to
me.
If
you
have
any
questions,
but
let's
jump
right
in
so
today,
I'm
gonna
demo,
how
you
can
combine
the
SharePoint
framework
and
dynamic
CSS,
specifically
on
optimizing
SP
effect,
extension
styles,
so
I'm
not
sure
if
there's
any
new
new
ones
on
the
call
feel
free
to
chime
in.
D
If
this
is
your
first
time,
if
you're,
fairly
new
to
SharePoint
framework
development,
but
good
good
to
know
we're
gonna
cover
some
of
the
high-level
basics:
real
quick
CSS
versus
sass,
and
some
of
that
we're
gonna
see
how
within
sass
you
can
have
modules
versus
non
modules
and
then
specifically
we're
going
to
see
how
we
can
optimize
those
Styles.
So
we're
gonna,
look
at
some
targeted,
CSS,
hash
lists,
class,
name,
preservation,
boy!
That's
a
mouthful
but
it'll
make
perfect
sense.
D
Once
we
show
it
to
you,
then
we're
gonna
say
we're
gonna
optimize,
the
bundling
of
our
Styles.
Now
that
sounds
weird.
What
styles
doing
a
J
s,
if
you're
new,
that
may
sound
kind
of
fall
for
him,
but
we'll
see
exactly
how
that
works
and
they're
gonna
see
how
we
can
dynamically
load
those
styles
so
that
we're
not
overloading
our
clients
browser.
So
what's
the
use
case
that
we're
going
to
use
this
strategy
and
there's
lots,
but
a
few
of
them,
and
today,
specifically
we're
going
to
see
an
application.
D
Customizer
extension
we're
gonna,
look
at
how
we
can
utilize
some
pseudo
styles
of
pseudo
styles,
if
that
sounds
unfamiliar
to
you
or
styles,
that
you
use
for
things
like
hover
and
active,
so
we're
gonna
highlight
today
how
we
can
use
shadows
and
glows.
You
can
also
use
them
for
animations
the
use
cases,
strategies
where
you
can
use
them
list,
formatting
we'll
see
that
today
specifically,
but
you
can
also
use
them
in
your
custom,
webparts
other
extensions
AKA,
specifically
where
you
own
the
HTML.
D
D
I've
got
a
list
of
some
PNP
community
members,
and
this
is
using
a
view,
style
definition
and
it's
just
styling
some
information
in
the
list,
but
what
we
would
like
to
do
is
we'd
like
to
add
some
Styles
that
allow
us
to
provide
some
of
those
hover
States
to
things
like
these
buttons
here.
So
we've
got
these
little
buttons
here
that
are
generated
by
our
view,
definition
and
we're
gonna
highlight
specifically.
D
We
know
that
if
I
come
in
here
and
look
at
the
element,
we
can
see
that
I've
got
this
PNP
hover
button
style
right
down
here,
so
we're
gonna
Keyon.
That
element-
that's
gonna,
be
part
of
our
CSS
today
and
we
want
to
apply
some.
Some
nice
effects
apply
them
I'll,
let
them
mute!
Thank
you
will
apply
some
nice
effects
to
these
when
we
hover
over
them
and
we'll
use
an
extension
to
do
that.
So
let's
go
ahead
and
hop
into
visual
studio
code.
D
Now,
what
we
see
is
just
a
basic,
very
basic
out-of-the-box,
scaffolded
extension
application,
customizer
extension
and
over
here
in
our
Styles
folder
of
creator,
Styles
folder
we've
got
a
collection
of
style
files,
some
plain
CSS,
some
sass,
some
modular
sass,
some
non
modular
and
we'll
see
what
that
means.
So
we're
gonna
start
we're
gonna
move
through
some
of
the
basics,
real
briefly,
just
for
those
that
are
maybe
new.
So
you
have
a
good
foundational
understanding
and
we're
gonna
start
with
our
button
shadows.
D
Css
now
is
just
a
plain
CSS
file
and
you
can
include
plain
CSS
files
in
your
extension.
If
you'd
like
not
the
most
robust,
there's,
definitely
some
limitations,
but
all
of
our
Styles
follow
pretty
much.
In
this
example,
the
same
concept
we've
got
things
like
section
body,
section,
header,
site
body,
site
header.
As
you
can
imagine,
those
are
fairly
basic
names.
It
could
very
likely
conflict
with
another
third-party
style
or
some
other
web
part
or
some
other
extension.
There
could
be
a
collision
there,
and
so
we'll
we'll
see
how
we
can
fix
that.
D
Then
we've
got
a
little
bit
more
of
a
verbose
style
here
in
our
PNP
button,
hover
style-
and
this
is
specifically
the
one
that
we
want
to
see
applied
to
our
list.
Formatting
definition
because
we'd
like
to
be
able
to
see
a
glow
or
a
shadow
or
something
like
that
applied
when
we
hover
over
so
we'd
like
it
to
inherit
that
so
we'll
jump
back
and
we're
gonna
go
ahead.
D
Just
show
how
to
import
the
plain
CSS
so
we'll
go
up
into
our
import
section,
and
we
will
just
save
now
pay
attention
to
the
dist
folder
right
over
here
for
those
that
are
new
when
you
create
and
import
styles
they're
actually
going
to
get
become
part
of
the
generated
part
of
the
generated
JavaScript.
And
so
that's
what
was
just
generated
right
here
is
our
java
script,
which
will
then
insert
those
styles
into
the
head.
D
So
if
we
come
on
over
to
the
generated
file-
and
we
do
a
search,
then
we
we
see
all
of
our
styles
now
add
it
there's
a
lot
more
Styles,
obviously,
in
that
file
than
then
I
showed
I
have
most
of
them
down
to
the
bottom
and
and
that'll
be
a
point
made
here
soon,
but
we
see
it's
now
included
them,
but
this
is
just
plain
CSS.
We
don't
really
take
advantage
of
the
sass
again.
What
about
our
collisions?
We
we
might
want
to
include
variables
so
obviously
not
the
best
option
but
unavailable
option.
D
So
let's
go
ahead
and
close
our
j/s
and
we'll
go
ahead
and
take
a
look
at
our
non
module
sass
file.
Now
this
is
a
little
different
in
that
we're
because
it
is
a
sass
file,
we're
now
able
to
utilize
variables.
So
you
can
see
I've
created
a
variable
here,
very
simple.
These
are
very
simple
examples,
just
to
kind
of
illustrate
the
purpose
I've
defined
a
shadow
color
and
then
I've
used
this
down
here
in
my
hover
declaration,
so
that
can
be
applied,
and
now
these
could
come
from
other
files.
D
We
can
have
multiple
much
more
robust
architecture
here,
and
so
what
we
want
to
do
is
we
want
to
now
include
this
replace
the
CSS
and
so
I'll
just
go
ahead
and
paste
in
the
importation.
It's
going
to
look
pretty
much
identical,
with
the
exception
of
calling
in
the
non
module
and
I'll
go
ahead
and
save
now,
when
we,
when
we
generate
this,
and
this
gets
generated.
Of
course,
what's
going
on
in
the
background
through
my
gulp
serve,
is
that
it's
being
web
packed
and
it's
going
to
be
generated
again
in
here?
D
So
again,
though,
we
have
our
problems
where
there
could
be
a
collision
on
these
very
basic
named
CSS
class
names.
So
we
want
to.
We
want
to
fix
that.
I
want
to
take
advantage
of
a
more
robust
importation
strategy
and
that's
where
these
modules
come
in
you'll
notice.
The
only
differential
between
the
name
and
the
non
module
and
the
module
is
a
dot
module,
so
we'll
go
ahead
and
include
that
replace
these
and
we're
gonna
include
both
of
them.
D
Now
we're
going
to
include
both
the
non
the
shadows
and
the
glows
and
we'll
go
ahead
and
click
Save.
Now,
what's
going
to
happen,
is
it's
going
to
do?
What's
called
hashing,
it's
going
to
add
on
a
dynamic
name
to
the
end
of
our
class
names.
So
that
way
we
don't
actually
have
any
collisions.
So
now,
if
I
come
back
in
and
as
soon
as
it's
finished
web
packing,
which
it
has
go
ahead
and
search
for
me
now
you
see
there's
this
mapping
that
occurs
right
so
now,
what's
actually
being
utilized.
D
Is
this
this
hashed
version
of
all
of
our
styles,
so
great
so
now
there's
no
more
collision?
Necessarily
we
see
that
there
here
section
body
is
now
section
body
and
blah
right,
so
we
don't
have
to
worry
about
a
collision,
but
this
is
not
exactly
the
most
robust
way
for
our
use
case
within
a
list
format
and
we
actually
might
want
to
reference
them
in
a
better
way.
D
And-
and
so
if
you
were
actually
writing
HTML
in
this
or
if
you
were
doing
this
inside
of
a
web
part,
then
you
might
actually
be
writing
HTML
down
here
at
the
bottom
and
and
we
could
name
these
modules,
so
I
could
come
in
and
change
this
to
be
button
from
and
now
you
can
see
that
it's,
including
it
and
I,
can
actually
come
in
here
and
say:
Styles
button,
shadows,
dot
and
it'll.
Give
me
access
to
all
those.
D
So
if
I
was
writing
HTML
in
here
and
needed
to
access
the
styles
that
that's
a
way,
I
could
do
it
and
there's
some
really
good
documentation,
so
I
won't
go
too
deep.
This
has
all
been
very
basic
documentation
or
information
that
you
can
get
already
in
the
documentation,
just
good
for
some
some
newbies,
but
in
this
case
in
in
list
formatting
we
actually
want
to.
D
We
want
to
preserve,
maybe
that
more
robust
style,
name
or
class
name
that
we
saw
inside
our
modules
files
for
shadows
and
buttons,
we're
okay,
hashing
these
guys,
for
example,
in
this
particular
situation,
because
they
are
basic,
so
there's
a
very
cool
feature
and
sass
that
you
can
wrap
Styles
around
that
you
want
to
have
preserved.
So
it's
:
global-
and
you
just
do
this,
so
you
see
I'm
wrapping
these
styles
that
I
want
to
have
preserved
in
:,
global
and
I'll.
Save
that
one
come
in.
Do
the
exact
same
thing.
D
That's
up
there
so
now,
we've
done
that
to
both
our
button
glows
and
our
button
shadows
and
we'll
go
ahead
and
let
webpack
come
in
and
if
we
go
back
into
our
customizer
and
do
a
search
there,
you
go
it's
already
taking
it
to
us
and
it's
ordered
fresh.
We
see
we
still
have
the
hashing
on
our
there
we
go.
D
We
still
have
the
hashing
on
our
generically
named
ones
that
we
were
ok
providing
that
hashing
to,
but
we
don't
have
it
on
our
PNP
hover
style,
button,
hover
style
so
now
I
could
still
use
this
more
verbose.
Name,
that's
likely
to
have
no
conflict
right.
You
can
name
them
more
verbose,
Li,
so
that
there's
a
very
virtual,
no
chance
of
having
a
conflict
with
another
another
style,
solution
or
web
part,
or
something
like
that
now.
D
What
if
we
wanted,
though,
to
dynamically
call
in
right
so
in
this
case
we're
using
a
couple
of
glows
shadows.
These
are
both
as
you
can
see,
that
there's
a
lot
more
Styles
being
loaded
in
here
and
we
only
want
one
or
the
other.
We
only
want
to
include
the
glows
module
or
we
want
only
want
to
include
the
styles
or
the
shadows,
module
so
we'll
come
back
in
and
we
can
actually
utilize
properties
within
our
extension,
so
I've
already
created
one
here
called
included
Styles.
D
D
Go
ahead
and
save
that
there
we
go
should
be
saving
fine
and
it's
looking
for
whether
or
not
I'm
going
to
pass
button
styles
or
button
glows
and
and
the
problem
is
that
we
can't
actually
do
an
import.
It's
giving
an
error
in
the
wrong
place.
But
it
should
be
giving
an
error
on
the
import
here.
So
we
could
change
that
actually
to
require.
D
A
D
D
D
Yeah
see
this
is
the
power
of
the
community
right.
Okay,
so
now
it's
included
and
if
we're
to
come
into
here,
we
can
see
that
if
I
do
a
search
here,
we
can
see
that
it's
still
there.
Everything
is
what
packed
we
even
see
a
new,
a
new
hash
value
there,
but
the
problem
is
that
it's
twice
the
size,
so
this
will
actually
work
if
I
were
to
go
over
and
pass
this
property
as
a
passed
as
this
value
as
a
property,
it
will
load
one
or
the
other
button
shadows
or
button
glows.
D
But
if
we
come
over
to
our
dist:4
and
reveal
this
in
our
Explorer
and
go
here,
we
can
see
that
it's
still,
including
both
CSS
or
sass
collections
of
styles
right
here,
and
so
we
don't
actually
want
to
do
that,
because
we
only
want
to
load
one
of
the
other.
It's
only
going
to
load
one
of
the
other,
but
is
still
including
it
in
the
bundle.
So
there's
a
very
cool
feature
called
a
type
skip.
Try
excuse
me
type
script,
import
expression.
D
If
we
change
these
to
import
instead
of
require-
and
we
save
pay
attention
to
the
distribution
folder
over
here,
what's
gonna
happen,
is
it's
not
going
to
split
those
out
into
multiple
files?
We've
seen
this
done
in
a
web
part
before
like
when
we've
clicked
on
a
button
or
something
like
that.
But
now
you
can
see
what's
happened,
is
it
split
them
individually
into
multiple
files?
D
So
now,
if
we
come
back
to
our
distal
der
here,
we
can
see
we've
got
smush
smaller,
multiple
files,
much
smaller,
and
these
can
then
be
called
into
the
browser
dynamically
based
on
our
value
being
passed
in
the
property
right.
So
let's
take
a
look
and
see
how
that
looks
actually
in
the
browser.
So
let's
go
back
we'll
close
this
one
we'll
bring
up,
so
we
can
actually
see
the
network
go
localhost
so
that
it
filters
on
localhost
and
what
I've
done
is
I've
already
pre-populated.
D
The
arguments
needed
here
to
include
those
files,
so
I've
got
included
styles
and
button
shadow,
so
I'm
gonna
go
ahead
and
refresh
it's
gonna.
Let
me
know
it
wants
me
to
authorize
loading,
my
scripts
so
we'll
say
yes
and
now
we
can
see
that
it's
loaded,
just
the
0.04
shadows
and
if
I
hover
over
our
warrior,
Horse
Whisperer
Chris
can't
write
our
buttons
are
working.
We
got
myself
low
the
show
and
now
that's
working
and
it's
only
loading
the
0.0.
So
we
can
go
up
and
change
that
to
glow
I'll
change
it
to
button
glows.
D
And
we'll
load
the
debug
script,
and
now
you
can
see
it's
bringing
in
1.1,
so
it's
not
bringing
in
the
shadows
and
if
I
hover
over
email
warrior
horse
whisperer
right,
then
it's
working
and
it's
only
loading
in
the
necessary
ones,
and
so
let's
go
ahead
and
let's
actually
send
a
message
over
to
our
favorite
warrior
horse
whisperer.
We
need
some
help.
I'll
go
ahead
and
load
that
here
and
if
we
have
any
three
amigos
fans
we
we
know
his
warrior
horse.
D
Whisperers
are
very
great,
so
we
want
him
to
come
to
Santa
poco
put
on
show
it's
not
the
famous
infamous
el
guapo,
because
we
all
know
what
infamous
means
more
than
famous
and
the
warrior
horse.
Whisperer
is
needed.
So
a
pretty
cool
feature
here.
You
know
again,
you
can
use
these
in
multiple
ways
within
a
webpart
extensions
and
there's
lots
of
ways
that
creative
this
sample
was
just
very
basic,
just
to
illustrate
that
the
value
of
things
like
the
import
expression
or
the
global
option
within
SAS
there
to
to
provide
a
targeted
hash
list
opportunity.
A
A
C
A
C
Generator
one
point:
six
so
generate
the
P
and
P
generator
generator.
Spf,
1.6
and
I
started
right
before
the
call
the
PR
41.6.
So
after
the
meeting
I
will
publish
it
and
all
the
test
has
been
hassled.
Nothing
is
in
the
way,
but
now
so
what?
Actually?
When
you,
when
you
start
a
new
project
now
and
let
me
go
over
here
to
start
a
new
project
and
we
make
the
screener
the
bigger
real
at
P
and
P.
Slash
has
two
effects
then
in
this
case
it
still
states
it's
the
pepper
three.
C
But
it's
not
that
because
that's
my
version
that
I
have
installed
and
I
haven't
published
it.
Yet
so
you
have
the
handlebars
web
generator.
You
have.
The
Gucci
has
generator
angular
elements
still
in
here.
Yes,
now
the
enhanced
SP
FX
generators,
the
react.js,
knockout
and
no
framework,
but
you
don't
have
the
default
ones
anymore,
because
I
will
explain
it
in
a
bit
why
these
enhanced
SPF
X
January
person.
Here
and
now.
C
Let
me
try
start
a
new
react
chest
projects,
so
we
have
now
the
same
thing
that
it
was
in
in
the
previous
version
as
well.
So
you
can
directly,
if
you
jquery,
you
can
directly
include
team
PJs,
the
property
controls
you
can
actually
use
in
all
the
projects
that
you
can
create,
those
as
defects,
but
the
reusable
controls
are
just
specific
for
the
reactions
projects,
the
property
controls,
because
the
side
part
that
you
actually
get
in
in
in
indian
SPF,
x,
pro
chest
and
on
your
web
part
is
actually
already
react.
C
Chest
control,
so
you
can
uncheck
them
in
there.
So
jQuery
which
working
do
you
want
to
have
3.0?
And
then
you
get
some
new
options
for
wetting
your
code.
So
one
thing
is
the
epic
pendulum
vilasa
that
helps
you
to
identify
where
you
have
small
libraries
as
big
libraries
in
there
that
actually
blow
up
your
your
package,
and
you
also
have
in
here
a
new
option,
which
is
a
styling
that
helps
you
to
linear'
or
evaluate
if
everything
is
correct,
some
technical,
correcting
your
CSS
styles
and
for
react.
Yes,
projects.
C
What
we
also
have
in
here,
we
already
created
in
there
a
test
framework
which
is
chest
which
is
heavily
used
by
alias
proof
or
Andrew.
Connell
actually
wrote
a
blog
post
about
this
and
we
directly
include
this
in
any
new
bro.
Every
new
project
that
you
create
so
now
with
this
is
the
default
reactors.
C
If
ex
generated
a
you
have
in
here,
so
it
asks
you
for
solution,
name
in
my
case,
I
just
used
the
demo
160
I
want
to
build
a
solution
for
the
shipment
online
and
the
latest
version
I
used
the
current
folder
I
don't
want
to
deploy
it
as
a
tenant
at
me.
I
just
want
to
create
the
web
part
and
what
is
the
web
part
name
yet
the
world
description,
and
then
it's
done
wait
so
now
it
creates
a
project.
C
C
You
get
you
a
lot
of
more
tasks
which
we
have
in
here
too,
but
the
epic
tunnel
analyzer,
which
is
documented
in
a
in
a
on
talks
that
microsoft.com
how
you
actually
implement
this
in
your
generator
I,
add
to
your
project.
But
we
do
this
already
for
you
another
gap
test
that
we
had
a
few
years
so
styling
the
definition
that
creates
a
subtask.
Whenever
you
build
your
project
and
I
tries
to
find
some,
some
issues
may
be
near
success.
C
Actually
what
you
need
to
have
when
a
youth
chest
you
always
need
to
target
to
a
specific
reactivation,
and
this
is
now
targeted
to
react
with
16,
because
I
said
in
my
project:
I
want
to
create
a
new
ship,
an
online
project
that
has
the
react,
16
library
included,
and
so
you
get
everything
ready
to
test
it
for
the
chest
testing.
Actually,
you
have
to
deploy
some
additional
files
that
we
also
do
for
you.
C
So
when
you
ever,
you
want
to
change
your
chest
configuration
you
have
here
chest
off
convict,
but
JSON
file,
which
is
actually
where's
your
root
directory
for
your
source
code
and
which
appreciate
preset
that
it
should
be
used.
There
is
in
an
upcoming
cycle.
Actually
Andrew
Connell
explains
a
little
bit
more
about
the
chest
integration
and
how
we
do
this
out,
how
we
can
unit
test
your
you
know
generator.
C
C
So
in
line
614
we
actually
have
a
0
and
with
PX
we
can
remove
the
savely
because
we
actually
went
when
you
have
a
serial
unit.
You
don't
need
to
have
a
unit
next
to
it,
and
it
saves
some
coding
us
on
some
bits
in
your
code,
in
your
style
and
now
we
do
it
again.
So
we
have
an
until
you
see
what
we
have
in
here.
So
we
have
here.
C
C
C
Once
we
saved
our
file
again,
we
actually
have
now
styling
the
message
here,
so
it
lands
at
our
code
and
everything
is
fine
now
from
from
this
perspective,
so
we
actually
fixed
all
the
issues
that
we
have
in
here.
Other
things,
for
example,
that
you
have
might
have
or
to
keep
your
scissors
consistent
when
you
have
something
like
this
color
hash,
FFF
save
it,
then
it
says:
hey
hidden
in
the
in
the
config
based
configuration
is
defined
that
all
the
values
for
colors
should
have
only
lowercase
characters.
C
Okay-
and
there
are,
there-
are
a
lot
of
definitions
on
this
you'll
find
more
on
this
on
the
styling
tool
I
of
website.
So
actually
they
have
160
built
rules
that
you
can
check
and
support
for
different
frameworks
and
defines
so
support
for
different
favors.
How
you
write
your
CSS
that
you
do
can
include
afterwards,
but
the
stallion.
Therefore,
the
SPF
X
is
already
here.
The
major
so
for
the
web
pick
bundle
analyze
of
what
I
need
to
move
over
to
the
temp
folder
and
what
we
have
in
here
there's
a
new
folder.
C
That
only
appears
when
I
have
the
back
panel
analyzer.
So
we
directly
write
the
result
was
ever
built
to
the
temp
folder
in
the
stats
folder.
So
we
have
in
here
the
demo,
16
dot,
stats,
dot,
HTML
and
when
I
open
up
my
workbench
and
say
in
here,
let's
stead
of
temps
that
then
it
was
demos,
168
of
HTML
I,
guess
wrong:
nope,
that's
not
HTML!
That's
what
I'm
missing.
C
You
see
all
the
results
from
so
the
index
sigh
index.
The
chance
actually
has
certain
put
23
kilobytes
4.6
kilowatts
is
what
this
javascript
file
takes:
the
CSS
loader
2.1,
and
if
you
have
things
like
moment,
chairs
or
jquery
included
in
here,
you
will
also
see
this
in
the
result,
and
you
can
then
identify
these.
Is
these
pieces
in
your
code
and
and
try
to
optimize
them
before
you
actually
ship
your
package
yeah
this?
C
C
When
you
create
a
reaction
product,
then
you
already
get
the
grout
file
from
your
from
from
the
default
generator
and
we
actually
need
to
inject
our
code
for
web
hacker
bundle,
analyzer
for
styling
team
directly
in
the
inside
the
gal
file
and
what
we
actually
did
in
the
in
the
yeoman
generator.
We
have
here
in
the
app
with
just
the
main
generator.
Then
we
have
two
templates
faster.
All
the
templates
faster
to
deploy
are-
and
we
have
fear
stalin
thing,
which
is
actually
it's
just
a
golf
task
that
we
inject
in
our
gal
file.
C
Just
for
the
stalin
thing,
we
have
two
epic
panel
analyzer,
which
is
only
the
code
that
we
inject
in
the
gal
file.
In
case
you
selected
the
web.xml
analyzer,
and
this
is
the
actual
default
gal
file
and
what
we
inject
in
here.
So
we
have
here
our
checks
when
you
actually
select
that
the
PMP
vetting
and
select
advaithic
panel
analyzer,
then
it
pushes
it
to
the
guard
task
and
down
here.
C
So
basically,
what
you
chosen
from
the
from
the
project,
generator
creation-
would
be
automatically
injected
here
at
the
custom
tasks
are
those
deaths
that
then
will
be
added
later.
For
example,
when
you,
when
you
select
handlebars,
template
a
blue-cheese
template,
these
will
be
automatically
injected
also
in
the
scalp
file
and
ended.
Then
in
your
projects
from
gout
from
in
here.
So
in
case
you
have
yeah.
C
In
so
in
case,
if
you
have
some
gout
tests
that
think
of
beneficial
for
all
the
people,
please,
you
can
share
those
with
us
for
examples
and
DevOps
tasks
or
whatever
you
think
or
using
your
development,
and
you
think
it's
a
valid
option
for
the
generator.
So
we
are
really
willing
to
see
what
what
with?
What
are
you
actually
working
for?
And
if
you
want
to
have
this
done,
please
open
up
the
give
up
issue
and
then
we
can
check.
How
are
we
actually
integrate
this
in
in
the
generator
pretty
easily
and
because
okay.
A
C
A
Now,
that's
that's,
actually
a
really
cool
stuff
in
the
future
as
well
know
the
stuff
were
to
show
it
related
on
the
the
yeoman
generator
inside
of
the
yeoman
generator
just
to
be
clear
on
the
on
the
new
people,
because
those
quarterly,
quite
again
a
new
amount
of
new
people
in
the
here,
without
any
previous
knowledge,
on
SPF
X.
This
isn't
what
you
need
to
actually
know
the
stuff.
A
What
Stephan
showed
inside
of
the
SPF
X
BMP
generator
is
for
those
people
who
actually
want
to
contribute
on
the
generator,
and
that
will
be
a
relatively
small
amount
of
people
yester
fun.
So
the
number
one
thing
when
I
think
people
should
be
getting
out
of
this
one
is
that
the
BMP
SPFs
generator.
First
of
all,
it
extends
the
OtterBox
generator.
A
It
extends
the
the
engineering
provider
generated
100%,
supported
by
SharePoint
engineering,
which
is
us
on
Microsoft's
own,
and
this
one
extends
that
by
having
then
an
open-source
layer
on
top
of
it
and
using
the
Stephan's
generator
and
not
Stephan's,
to
narrate
the
community
generated.
Let's
call
it
community
generator,
Stephan
has
been
leading
the
effort,
and
you
can
actually
then
get
more
ready
to
use
development
experience
in
the
solutions
now
Stephan.
A
C
A
C
A
A
So
basically,
what
you
can
do
is
always
use
this
as
your
de
facto
generator,
when
it's
an
act
produce
your
solutions,
because
this
one
actually
is
using
a
guard
box
generator
under
the
hood,
but
it's
offering
decorated
additional
capabilities
on
top
of
it.
So
and,
like
said,
I
think
the
number
one
of
us
are
the
big
thing
here,
which
people
are
always
asking.
Well,
it's
based
on
1.71,
which
is
an
important
thing
and
angular
element
support
is
here,
so
you
can
actually
it
creates
nicely
angular
element
solution.
A
So
I
helped
on
contributing
on
that
one
and
there's
enhanced
SPF,
X,
knockout
and
and
JavaScript
projects,
and
that
means,
if
you
do
to
enhanced
react.js,
which
probably
quite
widely
used
as
well.
It
is
using
the
out-of-the-box
once
again
out-of-the-box
general
right
under
the
hood,
but
if
you
select
that
one
Stefan
these
options
are
the
decorated
ones
so,
basically
now
you're
able
to
then
add
additional
projects
and
dependencies
automatically
to
the
solution
as
a
default
starting
one.
So
why
wouldn't
you
use
BMP
appropriate
controls
because
they
actually
really
reduce
the
development
costs
for
your
team?
A
It
makes
a
lot
of
sense
to
use
them
or
the
PNP
reusable
controls
if
you're
using
a
react
based
component,
so
you
can
get
all
of
that
dependence
inside
of
the
solution
immediately
when
you
start
creating
the
solution
so
highly
beneficial
cool,
sorry
Stefan,
that
was
just
for
a
recapping
hole,
the
value
of
the
of
the
solution
for
those
who
are
not
necessarily
super
familiar
one
more
time.
What
was
the
URL,
where
people
can
actually
get
information
on
this
one?
A
C
The
it's
going
to
github
it's
you
find
it
on
the
PMP
repo.
C
A
It
in
dalian
window,
so
it's
a
further
reference
for
those
who
are
looking
into
that.
So
if
you-
and
it
is
actually
beneficial
to
use
that
as
the
default
generator,
because,
like
said
in
this,
using
gotta
cook
generator
under
the
hood
Thank
You
Patrick
for
flipping
back
on
the
slides
you
want
to
close.
Or
how
do
we
do
this.
B
Yeah
sure
so,
thanks
to
David,
thanks
to
Stephane
for
the
great
demos,
thanks
for
basic
covering
at
the
beginning,
for
me
not
being
able
to
load
Skype
and
thanks
for
all
of
you
for
joining
the
call.
Our
next
call
will
be
January.
31St
2019,
my
god,
January
2019
is
almost
over
the
next
general
development.
Sig
will
be
next
Thursday,
January
24th
so
definitely
join
us,
then,
as
well.
Look
forward
to
seeing
everybody
on
both
of
those
calls,
learn,
reuse
and
share.
Thank
you,
everybody
out
there.
Thank
you
for
making
all
of
this
work.