►
From YouTube: PWA Studio Community Meeting Nov. 15th, 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
That's
cool,
they
came
out
really
well
so
the
first
thing
I'm
going
to
demo
is
some
breadcrumbs
Scott
for
this
really
there's
two
bread
crumbs
that
that
we
are
displaying
now
there's
a
category
page,
bread,
crumbs
and
product
page
bread,
crumbs,
and
they
were
done
separately.
Both
of
these,
both
of
these
features
have
been
merged
into
develops.
So
if
you're
working
out
the
develop
branch,
you'll
see
them,
I'll
just
show
you.
They
look.
Ignore
the
air
I,
don't
actually.
C
B
We
have
a
home
link
and
the
current
page
non
clickable.
You
can
go
to
an
intermediate
category
and
it
will
show
the
links
between
so
you
have
shop
in
the
home.
One
thing
I
wanted
to
call
out
was
that
there
is
currently
a
gap
in
the
gradual
coverage
for
the
breadcrumb
information.
So
while
we
can
tell
we
can
make
a
request
to
to
I'm
going
to
show
you
the
code,
real,
quick
inside
pressure,
pros
breadcrumbs
query.
You
basically
say
basically
say
give
for
a
category.
B
Give
me
the
breadcrumb
information
for
that
for
this
category,
so
normally
that
data
would
come
back
with
a
path
and
then
we
could
use
that
to
link
in
that
in
right
here.
This
would
just
be
a
link,
but
that
functionality
hasn't
been
released.
It
will
be
released
in
two
three
four
I
believe,
and
so
when
that
happens,
we'll
come
back
in
and
we
can
uncomment
this
or
if
you
update
here,
you're
back
at
your
Magento
is
just
two
three
four
you
can.
B
So
if
you've
ever
been
working
on
a
page
that
honestly
I
don't
know
if
this
is
a
route
components
create
account,
isn't
a
route
component,
it's
kind
of
like
a
root
component,
it's
a
route,
so
this
is
the
one
way
that
I
was
able
to.
We
produce
this
bug
that
Brennan
falkowski
was
having,
and
probably
several
other
people
were
getting
I
was
able
to
reap
Roman
the
create
account
page.
So
to
do
that,
you
would
just
be
on
that
page
and
let's
say
you
made
a
change
like
you
wanted
to
add
a
button.
B
Hope
this
works
so
though,
I'm
about
to
add
a
button
to
do
that,
create
account
page
and
you
can
see
it's
rebuilding
and
then
there's
two
things
that
actually
happen.
First,
the
hot
module
replacement
plug-in
tells
us
that
it
got
in
there
and
it
said
it
can't.
It
can't
accept
the
change,
and
so
it
just
does
a
full.
C
B
So
it
actually
does
that
full
reload
of
the
page
and
that's
what
we're
getting
here
and
then
there's
no
other
errors,
but
obviously
the
page
is
broken.
This
is
a
link
and
it's
like
for
some
reason.
It
doesn't
show
anything
else.
It's
just
the
shell
of
the
button.
Oh,
it
was
really
weird.
It
didn't
even
show
the
child
that
clicked
me
text
and
it
didn't
show
anything
after
it.
I'm
not
even
sure.
There's
another
container
I
think
is
on
there,
so
that
fix.
B
Just
check
out
this
all
is
live
the
two
things
that
I
fixed
I'm
gonna,
restart
my
watch
right
now.
Okay,
I
check
out
my
fix
to
restart
the
watcher.
Real,
quick
and
the
things
I
wanted
to
call
out
were
that
that
error
that
we
saw
with
the
Hmong's
replacement
will
not
force
a
hot
reload.
It'll.
Just
are
sorry
a
full
reload.
It
will
do
hot
reload,
so
just
the
chunk
that
was
replaced
will
get
changed
and-
and
it
shouldn't
look
like
this.
Obviously,
we
refresh
and
I'll
clear
my
storage.
B
Okay,
so
now
I'm
gonna
add
this
button
back
come
back
over
here.
Do
the
button
appears,
click
me
and
you
can
see
the
hot
line
replacement,
it
says
updated
modules
and
it
went
through
and
it
was
able
to
update
the
a
create
account
page
without
actually
doing
a
full
reload,
and
you
can
see
that
also
in
if
I
want
to
use
it
here.
B
Actually,
I'm
not
going
to
do
it
right
now,
but
there's
other
ways
that
you
can.
You
can
demo
it
by
like
telling
it
I
can't
remember
exactly
I
should
practice
them,
but
you
can
tell
it
to
toggle
stuff.
You
can
do
changes
in
hooks
and
it
will.
It
will
swap
out
those
cleanly
without
doing
flow
refreshes.
B
So
it's
a
much
better
experience
if
here
in
the
middle
of
working
on
like
the
checkout
form,
you
know-
and
this
is
something
that
we
worked
on
recently,
but
if
you're,
if
you're,
deep
in
the
checkout
form
and
you're
making
some
changes
to
something
every
time
you
made
a
change,
it
would
do
full
refresh
of
the
page.
This
would
get
closed.
You'd
have
to
open
the
form
back
up,
go
through
all
the
steps
just
to
get
back
to
where
you
were
in
development.
Just
like
get
to
the
step
that
you
were
on
now.
B
Yes,
so
I
can
show
you
what
I
did
so,
there's
two
things
so
this
line
here
we
had
a
react:
hot
loader
battle,
plugin
that
fixes
the
issue
that
was
forcing
us
to
restart
the
watcher.
So
that's
where
the
page
looked
broken
and
you
actually
had
to
just
restart
the
watcher
for
to
it
or
to
render
properly
that's
what
the
hot
loader
does.
The
next
thing
was:
adding
this
three
lines
of
code
to
actually
accept
changes
to
that
dependency
tree
or
anything
within
the
source
index
file.
B
So
if
anything
changes
this
now
allows
it
to
do
that
hot
reload
reven,
rather
than
that
error
that
shows
up
and
says
please
reload,
oh
actually
really
small
change,
said
only
30
lines,
three
additions,
but
I
think
it
makes
the
developer
experience
a
lot
better.
Hopefully,
if
anybody's
been
running
into
this
father
in
development,
it's
it
no
longer
happens.
B
D
Can
you
guys
see
my
screen?
Yes,
all
right
cool,
so
I'll
just
walk
you
through
the
PR.
There's
I
took
screenshots
of
all
the
interactive
pieces,
so
we
don't
have
to
do
a
live
demo,
but
basically,
as
part
of
our
performance,
optimization
milestone
that
we
started
on
a
couple
months
ago.
This
was
one
of
the
we're,
mostly
through
that
milestone
by
the
way,
and
so
this
is
one
of
the
last
remaining
issues,
and
so
this
is
just
the
loading
of
the
category
page.
D
When
you
first
come
into
the
page,
you
have
to
click
that
filters
button
to
see
it
so
I'm,
basically
just
reading
this
PR
to
you,
but
instead
of
so
basically
we're
just
lazy
loading
that
in
now
so
using
react,
lazy
and
suspense.
The
new
flame
chart
looks
like
this.
So
the
time
to
interactive
on
the
category
page
itself
is
much
quicker
and
then,
after
the
fact,
we
load
in
the
filter
stuff-
and
this
is
based
on
the
assumption-
I-
guess
that
the
filters
would
not
be
shown
right
away.
D
So
we
have
that
extra,
you
know
second
or
whatever.
In
reality,
it
takes
much
less
than
that,
but
that
extra
second
to
load
in
the
filters,
because
users
are
not
going
to
interact
with
them
right
away.
Anyway,
we
originally
had
logic
in
vania:
hey,
don't
even
load
the
filters
until
the
user
hovers
over
this
button
or
clicks
the
button
or
focuses
the
button
for
accessibility.
We
still
support
that
use
case
and
that
functionality
is
still
there,
but
the
default
in
venya
is
just
to
load
it
right
away.
D
So
if
you
want
to
defer
the
loading
in
your
project,
it
is
a
really
simple,
one-line
change
and
there's
a
comment
in
the
code
that
tells
you
how
to
do
it.
I,
don't
know
if
that's
the
best
place
by
the
way,
if
Kalka
bins
on
the
line,
maybe
we
can
write
a
docx
or
something
like
that,
but
yeah
feel
free
to
comment
on
this
PR
I,
don't
know
the
most
common
use
cases,
so
that
would
be
good
to
know
from
the
community.
But
this
is
the
default
and
venya.
D
B
And
just
to
just
add
on
Andi,
we
talked
about
this
in
the
PR
a
little
bit,
but
the
reason
why
we
ended
up
changing
it
so
that
it
so
that
it
autumn
in
the
chunk
but
on
the
first
load,
is
because
we
found
that
kind
of
a
weird
experience
on
slow
devices
or
slow
network
connections
that
if
we
waited
till
you
clicked
or
hovered,
then
you
end
up
in
this
weird
intermediate
state.
Where,
like
you,
get
an
overlay
of
the
things
still
fetching
and
then
after
it
fetches
it
like
pulls
in
the
drawer.
E
G
To
add
on
to
what
Raylan
said,
since
this
is
a
dynamic,
important,
that's
governed
by
a
web
PACs
detection
of
dynamic
imports,
it
would
be
something
that
potentially
could
be
changed
at
Build
time
by
adjusting
the
optimization
parameters
in
the
web
pack
build.
So
if
we
want
to
provide
people
the
opportunity
to
do
this
or
a
choice
to
do
it
based
on
their
UX
needs
versus
their
bandwidth
needs,
then
potentially
it
will
be
something
that
we
could
spike
later
to
be
just
adjusted
at
Build
time.
G
So
you
could
say,
reuse
existing
chunks
if
they
match
this
and
this,
and
that
you
could
make
a
nice
API
on
top
of
it,
so
that
it
requires
less
intimate,
webpack
knowledge,
but
because
of
that
availability.
If
build
phase
to
do
this,
I
think
it
will
be
reasonable
for
us
to
write
the
code
that
allows
it
to
be
split
dynamically,
since
it's
a
lot
easier
to
make
that
fast,
with
reusing
a
chunk
so
that
it's
preloaded
than
it
is
to
to
make
a
static
import,
suddenly
load
dynamically.
So
I
I
approve
of
this
basic.
D
G
Well,
I
guess
maybe
I
should
summarize
what
I
said
by
saying.
Thank
you.
This
is
great.
Thank
you.
So
much.
A
What
about
my
account?
What
about
full
checkout
and
the
cart
experience
and
this
piece
of
the
cart
experience
right
so
we've
had
those
in
our
backlog
and
now,
when
they're
starting
to
come
up
in
priority
and
return
to
work
on
those.
So
if
you
have
particular
interest
in
what
we're
doing
there
stay
tuned
on
these
upcoming
demos,
we'll
have
you
X
coming
in
talking
about
the
designs.
A
You'll
start
to
see
more
PRS
that
are
focused
on
menu
feature
work
and,
if
you're
interested
in
contributing
there
or
helping
out
or
what
we're
doing,
please
feel
free
to
reach
out
and
let
us
know,
comment
on
the
PRS
we're
back
home
right.
But
obviously
that
said,
that's
kind
of
a
shift.
That's
not
happy!
Now
we're
kind
of
wrapped
up
with
our
green
and
wrapping
up
some.
A
C
Awesome,
so
that's
nothing
to
do
with
the
actual
code
base,
but
I
thought
it
would
be.
It
would
be
great
to
have
like
a
list
of
actual
production
life
pwh
to
do
web
shops
and
as
far
as
I
know,
these
are
the
only
three
that
are
live
right
now
and
it's
basically
just
an
collection
of
metrics
and
who
made
them
and
a
link
to
the
webshop
and
I
think
this
can
be
beneficial
for
both
developers
and
merchants.
C
The
reason
it
it's
good
I'm,
not
sure
about
developers,
but
for
for
a
merchant
it
can
be
like.
Oh
wait.
All
these
metrics
improved,
so
I
was
still
doubting
if
I
would
go
for
petabytes
to
do,
and
this
could
be
like
this
final
push
and
maybe
for
developers
as
well,
actually
because
a
developer
can
reach
out
to,
for
example,
gh
or
experience
and
ask
okay.
How
did
you
fix
the
filters
and
we
can
help
each
other
grow
and
so
yeah?
That's
basically
why
I
made
this
list.
A
Think
there's
definitely
value
I,
think
and
just
I
think
the
question
we
get
consistently
most
people
know
where
Peter
very
studio
is
where
to
find
it
by
now.
But
the
question
we
get
consistently
is
hey:
what
production
storefronts
are
there
that
have
been
launched,
and
so
I
think
this
really
helps
to
answer
that
question
and-
and
we
can
discuss
it,
you
know
what
Jordan
but
I
think
it's
a
great
resource
for
just
answering
that
question
right.