►
From YouTube: Magento PWA Community Update July 19, 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,
yeah
happy
Friday
everybody,
so
we
are
relatively
light
on
content
today,
but
we'll
get
started
and
worked
through
some
demos
for
a
simple
code:
repo
for
mr.
Cal
cube
and
I'll
talk
about
some
road
map
updates
and
then,
if
we
get
mr.
Zeppelin
back
on
the
line,
we'll
get
some
kind
of
general
updates
on
some
of
the
work
that
he's
been
doing
around
app
creation
and
app
starting
in
scaffolding
and
then
we'll
kind
of
wrap
from
there.
So
we
will
kick
it
to
mr.
B
All
right
so
for
my
demo,
I'll
be
showing
up
temple's
preview.
This
last
time
we
think,
basically,
it's
just
a
repository
of
small
boat
samples
focus
on
the
functionality
of
the
different
pieces
of
the
Beauty
Studio
into
the
showing
off
like
a
single
application
like
been
here.
It's
just
going
to
be
smaller
examples.
B
You
can
see
some
of
these
examples
in
Peregrin,
documentation,
I've,
embedded
them
using
code.
Sandbox
I
can
say
that
there's
an
air
barrier
here
that
you
can
modify
and
also
run
the
actual
container,
that
the
actual
server
and
you'll
see
a
running
instance
and
the
example
shown
in
the
code
here.
B
The
neat
thing
about
this
is
you:
can
you
can
open
this
in
the
actual
code,
sandbox
and
they're
full
browser
window
and
work
it?
So
you
can
modify
it.
You
can
also
do
all
the
other
examples.
I
have
you
search
for
him
and
use
a
query?
Result
I'm
currently
working
on
to
use
query
example
and
we'll
be
filling
this
out
as
we
make
them
available.
A
D
Can
hear
you
that's
delightful
I
just
wanted
to
thank
you
for
the
code
sandbox
this
James,
although
I
had
to
do
two
restarts
and
three
blue
jeans
crashes
to
get
here
and
that's
the
last
I'll
speak
of
it.
I
know
what
you
just
demoed
and
I
am
super
duper
thrilled
with
it
and
I'm
wondering
if,
like
code
sandboxes,
can
become
the
lingua
franca
through
which
we
share
each
other's
code,
samples
etc.
D
B
B
D
It's
weird:
does
anyone
remember
the
old,
like
apocryphal
urban
internet
legend
of
the
bug
that
only
happened
on
Tuesday
is
because
I
think
I
have
a
bug
that
only
happens
on
Fridays
and
it
has
to
do
with
this
community
sink
meeting
so
I'm
a
fried
egg
lake,
but
yeah
I
mean
I
can
talk
briefly.
We
just
got
the
story
working
again
that
had
a
regression
with
the
now
dat
SH
build
yesterday.
D
D
We
are
really
excited
for
the
next
big
round
of
things
to
show
you
and
I
thought
it
important
to
show
that,
as
we
add
features,
and
as
we
do
refactor
stored
newer
concepts
like
hooks
and
peregrin
that
were
also
working
hard
to
keep
the
internal
structures
of
the
project
simple
and
where
it's
possible
to
simplify
them.
We're
continuing
to
do
so.
Let's
show
an
example
of
that
in
a
pull
request
that
we've
all
been
working
on
and
reviewing
called,
remove
the
mid
compilation
and
add
a
battle
preset.
Can
you
guys
see
my
screen?
We
can?
D
Oh,
my
goodness,
that's
two
things
working
in
a
row,
so
this
total
quest,
perhaps
most
notably
removes
more
code
than
it
adds
which
has
been
super
rare
for
me
in
my
career
it
looks
like
it
changes
a
lot
of
files,
but
the
vast
majority
of
those
files
are
actually
simple,
renames
and
obviously,
there's
been
some
additions,
but
mostly
it's
moving
code
around.
So,
if
you
scroll
through
this,
there
really
isn't
that
much
code
change.
D
It's
all
just
moving
files
from
one
directory
to
another,
and
you
can
see
that
the
majority
of
those
changes
are
moving
files
without
touching
them
from
the
Peregrine's,
SRC
or
source
directory
to
the
Peregrine,
Li,
B
or
library
directory.
That's
a
new
director,
essentially
we're
just
renaming
the
source
directory
and
get
represents
that
as
a
bunch
of
file
news
and
the
rest
of
the
move.
Changes
are
doing
the
exact
same
thing,
but
in
buildpack,
PWA
buildpack,
slash,
SRC,
it's
hard
to
see
the
PWA
buildpack
/lib.
The
reason
we've
done.
D
D
So
if
we
do
a
mid
compilation,
we
would
be
doing
something
as
simple
as
like
running
a
couple
of
babel
rules
on
it,
so
that
it's
in
a
more
laura
in
a
more
broadly
consumable
format
and
that's
what
we
were
doing
when
Paragon
was
compiling
TSM
that
so
that's
not
great,
because
it's
it's
just
an
arbitrary
decision
between
what
kind
of
code
we
write
in
the
source
files,
this
weird
middle
point
and
then
finally,
the
code-
that's
fully
transpiled
and
bundled
into
venía.
So
we've
gotten
rid
of
that.
D
But
now
how
do
we
make
sure
that
all
of
the
code
that
comes
into
Vania
is
using
the
same
set
of
rules
that
the
Builder
can
understand
and
that
Babel
can
transpile?
What
we've
done
is
we
have
added
a
priest,
that's
for
Babel,
that
we
use
commonly
across
the
project
instead
of
having
a
single
Babel
configuration
at
the
root,
and
what
that's
done
is
we've
moved
a
lot
of
the
existing
Babel
configuration
that's
down
there
at
the
bottom,
which
is
where's
that
will
config.
Let
me
try
to.
D
D
That's
just
using
a
preset
called
Magento
paragon.
Now
we
called
it
Paragon
because
Paragon
is
written
in
accordance
with
this
Babel
preset
and
every
other
library
or
function
or
component
that
you
bring
in
is
going
to
be
compiled
through
this
same
pipeline.
It's
important
that
they
come
from
raw
source
through
that
same
pipeline
for
tree-shaking,
like
I
mentioned
before,
so
now
that
our
root
directory
is
just
using
a
preset
that
we've
generated,
you
too
can
use
that
preset
by
adding
it
as
a
dependency
in
your
package.
D
So
now
that
we
have
that
babel
preset
all
the
other
packages
that
expect
to
be
compiled.
That
way,
our
just
declare
that
battle
preset
in
their
dependencies,
which
I'm
trying
to
find
a
good
example
of,
but
because
all
of
these
packages
are
expected
to
be
built
inside
our
repository.
Maybe
they
are
not
so
now
that
we
have
a
Babel
preset
and
all
of
those
libraries
use
that
Babel
preset.
We
no
longer
need
to
compile
venía.
So
we
can
take
all
of
the
build
steps.
D
Sorry
I
said
we
don't
have
to
compile
video,
we
don't
have
to
compile
Peregrine's
because
we're
just
using
uncompelled
Paragon
modules.
In
the
final
compilation,
so
we've
removed
all
of
the
build
steps.
We
don't
need
to
run.
Babel
intermediately
and
we've
removed
the
Babel
dependencies
from
Peregrine's,
because
it's
much
simpler
now,
instead
of
having
that
Babel
dependency,
Paragon
just
expects
the
presence
of
Magento
Peregrine,
the
babel
preset,
and
then
it
works
in
the
same
place.
D
We
have
build
pack
being
renamed
from
source
to
live,
and
this
also
represents
that
build
pack
used
to
have
a
build
process
just
so
that
we
could
conveniently
use
some
future
es6
features
and
then
compile
them
back
to
a
version.
That's
compatible
with
no
well
node
is
now
native
async/await
native
destructuring
and
native.
D
Okay
doesn't
have
native
static
methods,
but
but
most
of
the
things
that
we
do
in
the
build
pack
codebase
are
now
native
to
node.
So
there's
no
longer
a
need
for
that
compilation
step,
so
we
done
remove
it
now.
There's
only
one
build
process
in
the
whole
EWS
did
in
the
repository
and
that's
venya,
the
final
endpoint,
and
that
simplifies
things
a
great
deal
now
when
you
run
a
build
you're
no
longer
gonna
run
into
the
problem.
D
D
That
is
not
meant
to
be
built
as
part
of
this
current
package,
like
you're,
not
running
a
build
process
that
produces
an
app,
then
you
put
that
code
in
Lib,
so
there
should
be
only
one
repository
or
one
project
with
an
SRC
folder
and
that's
the
final
app,
which
makes
sense
because,
if
you're
importing
something
from
an
external
library,
it's
library
code.
So
now
that's
the
rule.
D
If
the
code
is
not
supposed
to
be
transpiled
like
in
the
case
that
build
Packer
up
for
Jas,
or
it's
only
supposed
to
be
transpiled
by
a
consuming
app
downstream
like
Peregrine,
then
you
put
it
in
a
Lib
folder
and
we're
going
to
codify
this
and
explain
it
in
the
wiki,
as
well
as
the
new
rule.
But
once
this
is
merged,
it's
just
gonna
be
a
couple
of
directory
renames
and
then
you'll
find
that
the
build
process
is
faster
and
simpler.
I
wish
it
had
been
merged,
but
we
just
had
a
couple
of
regressions.
D
D
D
We
have
the
new
battle
preset
Peregrine's,
but
just
like
some
of
our
other
packages,
it's
just
naturally
inserted
into
the
dependency
scheme
via
package.json.
We
don't
depend
on.
You
know,
James
correct
me
if
I'm
wrong,
but
we
don't
describe
and
defend
the
use
of
each
of
these
dependencies
right.
We
know
yeah,
so
Magento
Peregrine
is
just
another
dependency.
It's
the
dependency
on
the
new
babel,
preset
that
we've
written
and
we're
not
inhaling
any
kind
of
project.
D
D
B
D
A
C
A
A
How
do
we
make
sure
that
that's
updated,
but
in
the
meantime,
I
think
it
was
appropriate
to
give
just
a
quick
update
on
our
roadmap,
what
we're
working
on
where
we're
headed
and
then,
obviously
our
goal
is
to
make
sure
that
all
of
this
information
is
public,
transparent
and
that
we
are
actively
communicating
when
things
are
changing.
I
think,
obviously,
for
everyone,
that's
in
that
involved
with
trying
to
implement
their
own
pwace
to
do
projects.
A
The
primary
focus
that
we've
had
if
you've
been
in
our
backlog
has
been
on
peregrine
and
the
switchover
from
kind
of
venya,
purely
as
the
implementation
to
using
peregrine
and
react
hooks
and
that's
been.
The
primary
focus
for
the
team
is
kind
of
the
refactor
work
needed
to
to
create
all
the
necessary
focus
and
build
on
Peregrine.
So
we've
been
moving
through
piece
by
piece
throughout
the
application
right
doing.
A
So
as
we
as
graph
QL
is
expanding
covered
at
the
graph
QL
coverage,
we
are
also
making
sure
that
we're,
including
that
in
Peregrine's
and
in
the
PWS
to
do
so
that
effort
will
continue
all
going
all
the
way
through
the
end
of
the
year,
where
I
think
they're.
Their
roadmap
for
coverage
is
slated
to
kind
of
a
complete
towards
the
end
of
the
year.
A
What
else
is
worth
talking
about
on
here?
I?
Think,
that's!
Oh
and
of
course,
page
builder,
we've
already
begun
discovery
around
page
builder
and
PWA,
so
that'll
be
an
ongoing
effort
and
that's
something
that
we're
looking
to
really
make
some
big
strides
on
and
deliver
on
towards
the
end
of
the
year
going
into
the
next
year.
So
I'd
say
stay
tuned
for
that.
We've
got
some
great
some
great
early
progress
and
we'll
make
sure
that
we
continue
to
communicate
out
on
successes
there.
That's
about
it
for
a
kind
of
high-level
overview.
A
So
again,
we'll
look
to
make
sure
we
get
all
of
our
all
of
our
resources
that
are
out
there
on
the
wiki,
updated
to
be
accurate
with
our
roadmap
I
think
it's
a
we're
looking
at
how
we
can
make
sure
we're
communicating
the
changes
to
the
roadmap
and
then,
of
course,
if
there
are
any
questions,
feel
free.
Anybody
to
black
us
email
us
ask
questions
on
where
we're
going
in
for
delivering
any
questions.