►
From YouTube: PWA Community Update Aug. 8th, 2019
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
All
right,
hello,
hello,
everyone
good
morning,
good
afternoon,
welcome
to
another
community
sync
update,
as
you
can
guys,
can
tell
if
you've
been
with
us
before
the
majority
of
us.
All
of
us
are
working
from
home
today
because
of
Adobe
office
moves.
So
that's
why
you're
going
to
see
great
video
of
babies
desk
hammocks
everything
else,
so
we
have
a
few
updates
today
to
get
started.
We'll
talk
about
one
of
the
major
updates
from
this
week,
which
was
the
move
of
the
github
repository
for
Magento
research
over
to
Magento,
and
so
we'll
talk
through
that.
A
Why
we
kind
of
made
those
changes
and
then
any
of
the
details
and
Andy
will
present
that
we
have
mr.
zetlen
who's
joining
right
now,
who's
gonna
walk
through
some
of
the
latest
PRS
related
to
the
venya
concept
and
library
changes
and
then
we'll
kind
of
open
up
for,
of
course,
questions
or
demos
from
the
community
and
I
think
that's
about
it
on
the
agenda
and
we'll
so
we'll
follow
up
after
that,
you
could
wrap
them
there
so
Andy.
Maybe
maybe
you
want
to
kick
us
off
sure.
B
B
Try
to
improve
some
things
like
basically
inviting
more
people
in,
and
you
know,
hopefully
improve
things
for
everybody.
So
another
another
benefit
of
this
I
guess
moving
to
Magento
is
we
can
get
promoted
a
little
bit
easier,
so
I
think
I,
don't
know
if
we're
one
of
the
pinned
repositories
in
the
Magento
org
right
now,
but
if
not,
we
will
be
soon
so
just
getting
more
eyeballs
on
the
project
that
kind
of
stuff.
So
that's
that's
kind
of
the.
Why
of
of
it?
Here's
the
issue
we
were
kind
of
working
through.
B
We
did
a
whole
bunch
of
stuff
before
the
move.
Yesterday
we
actually
did
the
move,
and
then
we
have
you
know
a
list
of
cleanup
tasks
and
things
to
do
now
that
now
that
the
move
was
taking
place,
I
did
want
to
highlight.
We
have
a
few
known
issues
here
that
we're
keeping
track
of
so
our
coveralls
coverage
report
for
our
unit
tests
is
not
working
right
now
now,
dot
SH
in
the
CLA
check
are
both
I
think
they're
working
but
they're
not
respond.
They're,
not
reporting
their
statuses
correctly.
B
So
we
have
to
figure
that
out
and
then
the
other
big
one
is
that
the
PWA
studio
died.
Oh
I'm
used
to
just
redirect
to
github
pages
site
from
that
was
published
from
the
old
repository,
and
so
that
is
404.
Now
that
we've
moved
the
repository,
so
PWI
studio
geo
will
point
to
the
new
doc
site,
but
you
may
have
to
you
know:
just
wait
for
your
cache
to
get
busted
or
whatever
to
actually
pick
up
that
redirect.
B
So
if
you
have
a
saved
bookmark
or
something
like
that
to
the
doc
site,
you
probably
are
going
to
need
to
update
that
because
it'll
404
now,
but
it's
a
quick
fix
instead
of
Magento
research.
Actually
I
could
probably
go
there
right
now,
so
PWA
studio
to
I/o
so
yeah,
so
mine
is
still
cache.
So
this
is
going
to
Magento
research
and
the
fix
is
really
just
to
switch
this
to
Magento
and
then
you're
right
back
at
the
doc
site.
B
So
I
probably
need
to
update
some
bookmarks
there,
but
we
were
hoping
that
would
we
did
some
things
ahead
of
time
to
try
to
get
out
in
front
of
that,
but
didn't
end
up
working.
So
just
some
manual
steps
for
folks
to
do.
I
guess
I
would
say,
keep
reporting
issues,
we're
monitoring
the
community
slack
for
any
issues
that
folks
are
running
into
you.
B
All
your
get
traffic
your
HTTP
SSH
fetches
pulls
pushes
all
that
stuff
should
be
redirected
automatically
for
you,
but
in
the
short
term,
in
the
long
term,
you
probably
do
want
to
update
your
remote
to
point
to
the
new
location
in
the
Magento
organization,
but
not
something
you
have
to
do
right
now,
although
I
might
encourage
it
since
we're
talking
about
it
and
thinking
about
it.
So
yeah,
that's
about
it
for
the
update
on
the
move.
C
B
A
C
C
No
darkness
yeah
I
was
trying
to
share
my
screen
on
mobile
because
that's
what
I'm
on
right
now,
but
it
looks
like
my
phone-
is
not
cooperating
with
that.
But
I
can
tell
you
guys
if
somebody
wants
to
give
me
a
hand,
because
I
am
still
waiting
for
my
computer
to
restart
then
share
the
screen.
Go
to
pull
requests
and
I
would
appreciate
that
and
I'll
tell
you
when
I
can
take
over
sorry
about
this
Andy.
Would
you
mind.
B
C
Go
to
the
v4d
one
that
has
been
most
recently
closed.
This
is
the
beginning
of
the
final
chapter
of
the
create
PWA
CLI
saga.
So
I
wanted
to
share
this
first
and
say
this
is
the
the
first
step
of
five
steps
that
are
each
publicly
available
for
the
community
to
inspect
that
demonstrate
how
we're
going
to
move
our
posit
Ori
structure
and
system
to
a
much
more
modular
future
framework
that
enables
both
easy
project
creation
and
better
extensibility.
C
So
the
first
step
is
really
small
and
enough
luckiest,
which
is
a
small
refactor
of
the
venía
code
to
stop
using
root
relative
imports.
So
that
was
necessary
because
pretty
soon
most
of
the
venía
code
is
going
to
be
library
code
code
that
you
would
import
from
NPM
and
when
you
import
code
from
NPM.
Typically,
when
it's
not
application
code,
then
that
code
needs
to
work
independently.
C
The
code
can't
rely
on
a
specific
web
pack
configuration
and
we
also
do
have
expectations
that
the
code
makes,
but
it's
a
lot
easier
to
import
this
code
when
it
isn't
expecting
specifically
to
be
running
in
the
context
of
Benia.
So
this
makes
these
modules
capable
of
running
in
systems
outside
then
yet
don't
have
route
relative
imports
from
source
because
they're
going
to
import
sibling
modules
that
aren't
actually
route
relative
to
source.
So
these
relative
imports
wouldn't
work.
Fortunately,
our
team
was
really
fast
and
merged.
This
PR
super
super
quickly
and
Andy.
C
B
C
Okay,
so
once
the
route
relative
imports
were
merged,
which
they
are
the
next
big
step
was
to
introduce
a
build
pack
API
so
that
we
can
take
all
of
the
Veni.
A
specific
web
pack
configuration
it's
all
over
that
would
pack
config
j/s
file
and
put
it
behind
an
abstraction.
So
that's
we
don't
have
to
ask
you
guys
to
replicate
and
copy
over
and
take
over
that
whole
file.
Every
time
you
make
a
new
project.
So
if
you
look
in
here,
probably
the
most
relevant
file
to
observe
is
web
pack
and
fig
j/s
itself.
B
C
All
right
so
on
the
Left,
we
have
what
the
venía
WebP
a
config
file
used
to
be
lots
of
very
specific
tweaks
and
changes
to
the
web
pack
system.
Lots
of
specific
integration
of
build
pack
features,
and
so
this
constituted
a
tight
and
complicated
coupling
between
the
venía
code
and
the
build
pack
code
so
effectively,
nothing
would
work
unless
you
had
your
web
pack
and
figure
this
specific
way,
and
it
took
hundreds
of
lines
to
do
so.
C
So
we
have
automated
this
and
put
it
all
into
a
simple
function
called
configure
web
pack
and
function
is
still
being
documented,
but
in
the
text
of
the
pull
request
itself,
there's
an
explanation
as
to
what
it
does
now
over
on
the
right.
You
can
see
that
now
that
we
have
a
configure
web
pack
function
that
we
can
import
from
build
pack,
then
we
generate
a
web
pack
config
with
one
call
to
configure
web
pack
that
calls
asynchronous,
because
it
may
need
to
do
a
little
bit
of
filesystem
work.
C
If
we
base
everything
on
that
route
context
in
der
name
and
that's
on
line
5
of
the
right
side
of
the
diff,
then
it's
a
lot
easier
to
make
sure
that
web
pack
builds
function
reliably,
no
matter
what
your
working
directory
is
really
nice
for
things
like
running
in
a
docker
container,
etc.
So
that's
the
reason
for
that
argument.
The
next
argument
is
a
list
of
libraries
that
we
want
web
pack
to
try
and
put
into
a
synchronous
a
vendor
bundle.
So
these
are
libraries
that
would
be
used
commonly
across
the
system.
C
B
C
B
A
C
Now
so
there's
some
documentation
here
in
the
pull
requests
description,
which
is
not
good
enough.
Of
course
that's
going
to
have
to
end
up
in
the
documentation
folder
proper,
but
this
pull
request
is
only
a
few
days
old,
so
you
can
observe
it
and
get
a
little
sneak
preview
of
it
while
it
is
developing
into
a
place
where
it
can
be
merged.
So
we
looked
at
the
vendor
configuration
and.
C
Okay,
where
was
we
and
then
down
here
placeholder?
You
can
see
that
there
is
a
new
argument
called
special,
probably
gonna
have
to
work
on
that
name,
but
the
idea
is
that
this
is
an
object
that
refers
to
the
configuration
of
modules
that
are
in
NPM
that
this
prod
special
and
treat
specially
in
the
web
pack
build.
So
if
we
go
and
view
this
directory
a
little
bit,
there's
this
file.
C
Buildpack
looks
for
features
like
es
modules,
CSS
modules
and
graph
QL
queries
and
he
uses
them
to
set
up
tests.
So
these
tests,
sorry
not
in
unit
tests
but
tests
for
rule
configurations.
So
when
you
specify
that
a
package
has
CSS
modules,
then
webpack
is
going
to
include
it
in
this
loader
processor,
which
means
that
it's
going
to
combine
it
with
the
rest
of
the
CSS
modules
and
then
the
style
over.
So
this
is
just
kind
of
a
shorthand
for
configuring
web
pack.
This
way
you.
C
Look
at
the
draft
documentation.
That's
in
the
description.
You
can
kind
of
see
what
the
available
flags
are,
though
they're
not
all
obviously
used
in
this
pull
request.
There's
es
modules
as
we
discussed.
Those
are
going
to
attempt
to
pull
in
ES
modules,
which
allows
web
pack
to
tree
shake
them.
There's
CSS
modules,
which
we
discussed,
there's
graph
QL
queries,
which
means
that
they're
going
to
be
passed
through
the
graph
QL
loader,
which
pre
compiles
the
queries
and
then
also
can
pull
queries
out
of
the
file
system.
C
So
when
we
merge
this,
this
is
going
to
add
the
web
pack
configuration
function,
but
by
itself
that's
all
it's
going
to
do
because
we're
keeping
these
pull
requests
as
separate
as
possible.
Once
that
webp
a
configuration
function
is
in
there,
then
it
becomes
possible
to
move
venía
components
to
a
library.
So
this
PR
number
three
looks
terrifying.
What
is
going
on
here?
Thousand
changed
files,
I
know,
but
guess
what
almost
all
of
those
file
changes
once
we've
gotten
past
the
big
stuff
actually
I,
don't
think.
C
Is
different
correctly?
Is
this
based
on
the
wrong
yeah
I?
You
know
what
it
I
I
think
it
yeah,
it
hasn't
been
updated,
but
here's
most
of
the
files
is
there
renames
files
renamed
without
changes.
So
all
that's
happening
is
that
these
files
are
being
copied
from
venía
concept
to
a
new
folder
called
Linea
UI.
C
C
Apparently,
it's
not
showing
up
the
right
folder.
Sorry
about
this.
You
might
notice
that
now
that
we
have
an
additional
vania,
UI
folder,
the
venía
concept,
folder
has
gotten
a
little
bit
barren.
There
aren't
many
components
in
there.
There
are
not
root
components.
There
are
not
templates
they're,
not
graph.
Ql
queries
instead
inside
the
venía
concept,
folder
all
the
dependencies
that
we
want
to
be
adjustable,
we
do
have
them
stored
here
in
veneers,
dev
dependencies
package.
C
We're
gonna,
try
and
shrink
that
a
bit,
but
you
might
notice-
maybe
most
importantly,
that's
we're
depending
on
the
venía
UI
library,
and
that
library
is
at
version
1.
This
is
the
first
library
which
will
ultimately
constitute
many
other
venía
libraries,
as
we
continue
to
refactor
this
out,
and
so,
where
do
we
use
many
a
UI
inside
venía
concept?
Well,
we
still
have
an
index
and
that
index
imports
the
app
from
venía
UI.
C
It
has
a
store
that
we
declare
locally
so
that
someone
who
creates
a
project
based
on
this
can
easily
modify
store
behavior,
but
it's
importing
all
of
the
pieces
of
the
store
from
the
vania
UI
library.
So
now
that
the
Vinnie
a
concept
folder
is
fairly
small.
What
you've
done
is
you've,
let
us
on
the
core
team
and
the
community
folks,
maintaining
the
core
team
start
maintaining
more
component
code.
A
C
Okay,
so
now
we
have
our
own
app
component
and
then
in
our
index
file
which
imports
that
app
component,
we
would
import
the
context
provider
from
Magento
of
any
IU
I
still,
but
we
would
import
app
from
source
components
or
now
I'm
sorry,
here
in
this
folder,
you
can
still
do
the
route
relative
imports
because
we
got
rid
of
route
relative
imports.
Just
so
we
could
move
most
of
the
venía
stuff
to
Vinnie
a
UI.
C
We
want
to
make
route
relative
imports,
convenient
and
accessible
and
easy
for
you,
but
that's
the
cost
of
Vinnie,
a
UI
stuff
that
we're
maintaining
needing
to
do
relative
imports
instead,
not
a
big
deal,
and
since
the
folks
on
this
call
and
your
core
maintainer
z--,
you
need
to
know
about
it,
but
this
ought
to
be
invisible.
So
this
is
how
you
would
do
that
and
now,
let's
take
a
look
at
what
changes.
B
C
C
The
next
step,
once
the
venía
concept,
folder,
has
been
shrunk
down
to
a
small
set
of
kind
of
top-level
files
that
take
the
venía
UI
and
then
render
it
into
the
dom.
Then
that
makes
it
possible
to
use
the
vinny
a
concept
folder
as
a
reasonable
basis
for
a
template.
But
right
now
we
kind
of
make
you
copy
the
entire
folder
into
your
own
project
in
order
to
start
work,
but
now
that
bené
bené
a
concept
contained
the
entire
implementation
of
the
store
that
felt
like
taking
over
too
much
code.
C
Now
that
we've
put
all
that
store
stuff
into
the
UI
library,
you
can
copy
and
paste
venía
concept
into
a
new
folder
and
change
some
things,
but
also
that
seems
kind
of
annoying
to
do
still.
So
we
are
adding
a
concept
first
previewed
and
imagine
for
creating
a
new
project
based
on
a
template,
scaffold
the
first
one
being
venía
itself.
C
C
Ok,
that
is
a
wrong
path
to
fix.
You
might
also
notice
that
we
now
have
kind
of
a
convention
where
almost
all
the
code
from
modules
is
in
the
Lib
directory
for
library.
This
is
a
way
of
indicating
that
this
code
is
used
directly
by
NPM.
Dependents
doesn't
need
to
get
compiled
into
dist,
because
we
have
the
expectation
that
your
venía
UI
code
and
the
code
from
modules
you
import
will
be
compatible
with
your
local
babel
preset.
So
lib
is
where
everything
is
instead
of
SRC,
if
it's
not
in
your
actual,
consuming
app
itself
anyway,.
B
C
C
C
What
might
be
most
important
to
you
is
understanding
how
you
would
actually
automatically
generate
a
scaffold
based
on
this
overriding,
a
component,
something
I'd
like
to
show
you
it
right
now,
I
think
in
the
current
state
of
the
PR.
It's
not
working,
but
I
think
we
can
still
at
least
show
off
the
scaffolding
creation.
So
let's
do
that.
B
Hey
James
I
have
a
quick
question
about
the
stats
that
were
just
shown
before
you
move
on.
So
if
I
go
to,
does
that
mean
that
if
my
website,
a
that,
you
know,
is
serving
our
stuff
and
website?
B
is
serving
our
stuff
that
if
I,
if
I
hit,
if
a
consumer
hits
website
a,
they
would
download
all
those
bunder
vendor
bundles
and
then,
if
they
go
to
be
website
B,
they
wouldn't
have
to
download
those
again.
Those
would
be
caches
all
right
that.
C
Is
something
we're
aiming
at
eventually?
That's
a
really
really
good
question
right
now:
that's
not
something
we
can
guarantee
yet,
but
we
really
want
to
write
about
right
now.
We
cannot
you
kind
of
have
to
balance
between
the
being
able
to
customize
your
bundles
for
your
sites
on
progressive
load
and
being
able
to
see
the
end
them
so
that
it
doesn't
have
to
load
for
your
individual
site,
I.
C
Think
as
we
work
we're
gonna
figure
out
what
the
most
common
bundle
combinations
are
and
we'll
end
up
with
some
sort
of
modular
configurations
for
web
pack,
so
you
can
choose
to
use
a
bunch
of
bundles
that
will
be
served
from
our
CDN,
but
I
think
that's
a
little
bit
in
the
future.
It
is,
however,
a
really
good
performance
enhancement.
Definitely,
okay,.
C
C
A
C
C
But
it
looks
in
the
build
pack
directory
the
dot
build
pack
directory,
which
is
a
new
convention
that
we
want
to
promote,
or
that
we
want
at
least
to
get
some
review
and
feedback
on
where
any
folder
that
has
a
dot
build
pack
directory
in
it.
Build
pack
will
try
to
interpret
as
a
template
to
generate
a
new
project
from,
and
the
create
j/s
file
in
here
is
where
many
a
concept
in
specific
describes
how
it
is
to
be
copied.
C
You're
gonna
want
to
change
its
name
because
it's
not
Benia
anymore.
You
might
want
to
update
some
of
the
build
scripts,
and
so
this
actually
specifies
that
stuff.
You
have
the
ability
to
return
a
visitor
and
the
name
each
file
that
you
want
to
treat
with
certain
custom
behavior.
In
this
case
we
say
if
you're
copying
package.json,
do
this
instead
weed
it
out
of
this
path
and
copy
it
in,
and
this
is
what
we're
getting
some
kind
of
bug,
not
really
sure
what
it
is,
we'll
go
ahead
and
debug
it
later,
but
I
do
have.
C
C
The
Creator
it
actually
copies
over
some
of
any
astac
adjacent,
but
not
all,
and
then
you
have
a
brand-new
project
which
depends
on
the
Vinnie,
a
UI
library,
and
it
has
a
new
name
and
it
has
a
new
basic
description.
It
has
a
new
license
and
it
has
some
basic
scripts
to
set
up,
and
this
is
what
the
future
holds
instead
of
calling
PW
a
studio
repository.
So
thanks
for
your
patience,
but
the
upshot
of
it
is
that
we
have
some
v4
pull
requests.
C
There
here-
and
there
are
named
in
order,
p2,
p3,
p4
and
p5
and
I-
am
really
excited
to
see
you
guys,
thoughts
on
it
and
feedback.
I'm
sure
they're
gonna
get
iterated
on
a
lot
more
before
we
merge
them,
but
that
is
going
to
represent
kind
of
the
next
phase
of
extensibility
and
repository
structure
for
a
project,
and
that's
all
I
got
thank
you
for
helping
me
be
mindful
of
timing.
So
questions.
D
C
C
So
this
is
going
to
come
out
as
the
4.0
0.0,
and
you
know
we
have
a
better
QA
process
than
ever,
though
you
wouldn't
think
it
to
see
my
demo,
and
so
we
can
say,
live
with
fairly
high
confidence
that
when
4.0
0.0
hits
that
we
are
hoping
that
people
will
start
using
this,
this
stuff
immediately
I.