►
From YouTube: Magento PWA Community Meeting August, 9th 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
B
A
And
we
have
a
fairly
short
update
because
Andrew
Wilcox's
outs,
Eric
away,
is
in
Chile,
although
he's
going
to
be
attending
he's
a
little
bit
late
on.
This
call,
because
he's
got
that
another
update
to
do,
and
so
I
am
answer.
So
oddly
described
it,
your
guest
host
I,
don't
know
I
feel
like
I
feel,
like
I'm,
a
part
of
the
picture
and,
in
general
an
usual
basis
right,
I,
think
so,
but
we
for
my
purposes
anyway.
I
think
we
have
three
things
to
discuss.
A
One
of
them
is
the
the
main
one
of
them
is
our
intention
ultimately
to
do
a
major
release
rather
than
a
minor
or
patch
release.
Given
the
the
substance
of
the
changes
to
the
core
repository
and
another
one
is
just
in
general,
aligning
on
priorities
for
q3
and
q4
and
putting
together
just
a
sort
of
top
priority
list
and
making
sure
that
the
folks
here
who
commit
so
much
time
and
energy
to
our
project
feel
pretty
much
in
agreement
on
it.
So
I'm
leaving
all
those
is
there
just
off
of
the
cuff
any
additional
stuff.
A
A
Okay,
can
you
see
that
now
yeah,
okay?
Well,
everybody
recently
closed
tickets
include
some
fairly
large
ones,
including
this
don't
merge.
I
hope
we
didn't
merge
this
and
though
my
name
is
on
a
couple,
these
two
obviously
and
there's
some
details.
Let's
not
start
with
mine,
let's
start
with
sort
of
a
follow-up
to
the
merge
of
the
repository
that
we
carried
off
so
successfully
last
week,
probably
mostly
because
I
wasn't
super
involved.
I
have
an
D
Terranova
and
the
rest
of
the
team
to
thank
for
that.
A
But
I
wanted
to
call
out
any
specifically
because
he
did
so
much
organizational
work
and
stepped
up
to
do
it,
but
we
have
had
a
fairly
smooth
transition,
but
nevertheless
there
will
still
be
some
trailing
issues
to
update
and
there
were
last
week,
including
just
changing
Magento
research
to
Magento
and
a
bunch
of
text
files
and
markdown
files.
So,
though,
we
have
a
trailing
issue
that
we
closed
to
make
sure
that
the
move
to
the
Magento
organization
is
done
and
that
any
integrations
that
did
not
survive
the
transfer
are
at
least
being
worked
on.
A
The
CSE
PR
update
I'm
going
to
leave
to
dev
because
that's
also
really
important
for
community,
but
this
is
a
fairly
major
merge
and
I
demonstrated
a
little
bit
of
last
week.
So
I
won't
go
into
a
lot
of
detail,
but
the
important
thing
is
that
there
is
now
a
new
configuration
API
for
build
pack
to
create
a
web
pack
config.
A
A
That
shrunk
down
this
is
because
a
lot
of
what
you
used
to
see
in
this
large,
complex
web
Peck
and
fig
has
been
abstracted
into
a
configure
web
pack
function.
This
is
documented,
currently
part
of
the
merge
into
master,
was
approved
by
Docs
and
includes
a
draft
document
describing
the
configure
web
pack
function.
It's
not
yet
merged
in
and
fully
edited,
but
it
is
present
here
in
drafts
configure
web
pack
with
a
full
description
declaration
of
API
and
and
its
purpose.
A
Upcoming,
pull
requests
are
going
to
take
advantage
of
this
functionality
and
the
the
merging
of
up
word
files
that
it
enables
and
the
collection
and
inclusion
into
the
build
of
graph,
QL
queries
and
other
static
assets.
I
think
you're
gonna
like
it,
but
this
constitutes
a
major
change
and
hilariously.
A
All
of
my
PRS
were
called
v4
PRS,
because
I
forgot
that
we
were
already
on
four
but
you're
not
going
to
see
this
stuff
get
released
onto
NPM
and
into
the
major
package
intoo,
without
going
to
a
full
major
or
at
least
5.0
point,
and
that
means
so
migration
burden.
But
it's
a
lot
better
than
the
alternative,
which
is
breaking
you
with
a
patch
or
a
minor
update,
so
we're
gonna
try
to
be
very
hands-on
and
very
presence
in
the
community,
chats,
etc
to
help
you
guys
with
this
transition.
A
But
it's
going
to
lead
the
way
to
extensibility
and
we're
super
excited
about.
So
that's
the
reason
for
a
5.0
release.
I
think
you
can
see
that
our
release,
cadence
is
still
fairly
nimble,
released
3.0
came
out
most
recently
and
then
before
then
was
released.
Two
one
and
two:
oh,
we
don't
have
a
very
conservative
approach,
doing
major
releases
and,
as
hopefully
most
of
us
know
and
remember,
these
releases
are
not
specifically
connected
to
releases
of
the
Magento
product.
A
We
do
guarantee
compatibility
with
current
releases
of
the
Magento
open
source
product
in
the
enterprise
product,
but
Ino
us
to
do
is
a
separate
piece
of
software
and
our
major
version
scheme
is
just
for
that.
It's
not
supposed
to
coincide
with
regular
Magento,
so
those
are
the
first
two
agenda
items
and
the
third
one
is
something
I
don't
have
collateral
built
for,
but
we
have
a
general
issue
where
we
want
to
make
sure
that
the
folks
who
are
adopting
PWA
studio
get
their
questions
and
their
concerns
into.
A
We
have
had
a
lot
of
questions
about
localization
and
internationalization.
We've
had
a
lot
of
questions
about
proper
deployment
characteristics
and
having
better
documentation
for
that
deployment
and
find
in
the
epic
or
maybe
that's
over
here,
I
knew
we
called
it
another
coherent,
but
maybe,
most
importantly,.
A
A
Hurt
from
a
couple
of
pieces
of
feedback
that
our
SSR
story
is
not
sophisticated
enough,
it
certainly
has
some
layers
of
complexity
and
we're
going
to
pair
those
down
for
rendering
to
the
major
clients.
But
the
current
static
render
philosophy
is
to
render
the
page,
via
upward,
via
mustache
template
resolution,
to
all
browsers
and
for
many
years.
B
A
It's
a
desktop
computer.
Maybe
it's
a
phone
we'd
like
to
research,
switching
from
partial
SSR
to
zero
SSR,
the
SEO
concerns,
as
we've
said
they
they
aren't
a
big
deal,
because
this
is
an
endorsed
approach
from
the
major
consumer
of
search
engine,
optimization
Google
themselves,
and
the
speed
concern
I
think
is
something
we
have
to
see
from
our
research
spike.
That
turns
out
to
not
be
faster,
we'll
figure
out
why?
But
the
whole
point
of
it
is
to
render
faster.
A
So
we
want
to
at
least
test
switching
from
rendering
HTML
that's
an
application
shell
out
of
upward
itself
and
into
pre
compiling
the
HTML
shell
and
then
delivering
that
statically
to
get
to
the
first
render
down
much
faster.
We
haven't
yet
that
prioritized
and
assign
this
task.
It's
still
kind
of
ready
for
grooming,
but
this
is
something
that's
on
our
radar
as
the
next
kind
of
major
technical
change
to
the
way
that
we
winter
and
it
is
directly
in
service
of
Shaving
seconds
off
of
the
first
render.
A
So
we
think
people
will
be
fairly
pleased
with
it.
But
the
floor
is
open
for
folks
to
take
on
some
of
the
recommendations
in
this
story
and
with
them
and
use
the
HTML
web
pack
plug-in
kind
of
you
name
it.
There
are
a
couple
of
other
initiatives.
I
have
talked
enough
and
I
promised
it
was
going
to
be
a
light
day.
So
Debra
you
ready
to
talk
about
CI,
CD,
stuff,
yep,.
B
A
B
Okay,
so
coming
to
see
a
CD
of
this
link,
we
have
three
updates.
First,
one
is
about
deployment,
so
previously
we
had
like
bills
and
liquid
dead
and
we
never
had
deploy
build
on
AWS.
So
now
we
have
set
it
up
and
you
can't
access
to
a
front
audio
W
systems.
Now
with
you
would
be
like
this
is
a
static
part
of
it
and
you,
the
changing
part,
will
be
the
PR
number.
A
B
Yeah
and
second
of
details
about
the
danger
beyond
template
terror,
so
so
like
via
tablet,
if
you
have
any
description
or
a
range
of
steps
missing,
so
currently
danger
through
this
the
other
side.
Even
if
you
update
it,
this
don't
go
away
until
the
next
push,
but
now
we
have
sort
of
a
nightly
build
which
runs
like
around
8
p.m.
B
C
C
My
screen,
yes,
sir
yep,
so
this
is
a
draft
I
have
it's
still
I'm,
still
working
on
it,
but
I'd
love
to
get
some
feedback
on.
You
know
the
content
that
I've
pushed
up
already
James
I
know
you
probably
have
some
things
you
want
to
add
to
some
of
these
topics.
You
know
headless
architecture
and
Magento's
micro
services.
Things
like
that.
So
yeah
just
comment
on
this
draft
PR
and
I'll
keep
while
working
on
it.
A
So
you've
gone
and
thank
you
so
much
and
you've
gone
as
well.
I
I
got
kicked
out
of
the
room.
I
was
in,
but
I
wanted
to
say
real
fast
that
if
you
don't
want
to
wait
for
the
nightly
build
great
as
it
is
to
have
you
know
a
lot
of
you
didn't
know
what
was
going
on.
So
thank
you
for
that.
If
you
don't
wanna
wait
for
the
nightly
build,
you
can
create
an
empty
commit
with
a
flag
on
that
get
man
line,
and
you
can
push
that
empty.
B
B
A
A
Yeah
and
David:
that's
something
we
talked
about
offline
because
you've
brought
some.
You
brought
a
perspective
to
light
on
that.
That
I
think
is
important
to
address,
but
you
and
I
should
talk
about
that
in
more
detail.
Does
anyone
on
the
call
have
questions
or
wants
to
volunteer
their
own
update
or
or
just
have
general
comments
to
make.