►
From YouTube: Magento PWA Community Update 30 August, 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
here
we
go
welcome
everybody
to
another
Friday
community
demo,
sync
I
think
we
are.
We
have
a
couple
really
good
demos
from
revolt
here
today.
I
think
Jimmy.
If
he
ends
up
joining
us
this
morning,
is
going
to
have
a
couple
of
things
to
cover
James
I'm
sure
you'll
have
something
to
talk
about
me
baby.
No,
no,
this
time,
I
think.
A
C
C
So
the
first
one
was
a
word:
writing
a
web
plug-in
using
actually
the
web
pack
instrument
plugin
on
starting
couple
other
plugins
around
it
to
get
SSI
Kovarian.
So
the
problem
we
had
was
it's
not
a
problem
statement.
Whatever
we
had
in
the
past
was
compiling
at
run
time.
They
call
the
HTML
files
and
everything
combined
using
upward
at
runtime,
so
it
was
little
sluggy
at
times
it
was
take.
C
B
C
C
Yes,
this
particular
one.
If
you
look
at
the
performance
wise,
the
left
is
actually
with
the
changes
and
the
right
is
actually
with
without
the
changes.
This
is
developed
branch.
So
this
is
a
huge
performance
boost
from
six
to
six
to
ninety
five.
But
then
you
could
see
the
best
practices
in
the
Casio
as
kind
of
a
HUD
at
this
point,
but
then
we'll
get
it
back
zlingly.
If
you
want
to
add
something
wrong.
B
Meta
tags
and
stuff,
though
I,
can
mention
the
SSR
approach
here
of
doing
a
static.
Html
page
for
all
pages
is
currently
the
best
practice
used
by
many
PWA
implementations
that
are
very
high
performance
and
recommended
by
PW
a
thought
leaders
what
else
to
say
that
developer
relations
advocates
at
Google
certainly-
and
there
are
cases
where
we
do
want
to
do
some
data
or
content
in
the
server-side
render
or
BOTS
and
machines
that
aren't
going
to
render
the
full
app,
but
most
search
engines
do
render
the
full
app.
So
this
covers
the
most
use
cases.
B
The
previous
approach
did
render
full
content
for
most
pages
using
a
lot
of
upward
logic,
but
it
was
pretty
slow
because
of
a
number
of
sequential
calls
that
have
had
to
make
to
get
all
of
that
data.
The
graph
QL
API
is
going
to
speed
up,
so
that
would
be
helped
certainly,
but
in
general
we
found
that
the
performance
benefits
of
switching
to
full
client-side
rendering
outweigh
the
costs
of
waiting
for
the
data
on
the
client
side,
but
we
have
removed
some
functionality
with
this.
It
no
longer
does
the
full
content
server-side
render.
B
Since
we
know
that
things
like
the
Facebook,
it's
likely
Cod
are
going
to
leave
that
server-side,
rendering
we're
going
to
bring
it
back,
we're
going
to
bring
it
back
differently,
using
extension
functionality
with
new
extension
API,
and
that
SSR
will
only
kick
in
when
they
detect
that
the
request
is
not
coming
from
neither
problem
with
it's
coming
from.
You
know
a
bot
that's
coming
later.
For
now
we
needed
to
simplify,
so
people
will
have
questions
about.
D
C
C
E
B
B
That's
kind
of
what
upward
is
for
is
to
say
this
is
how
the
server
has
to
respond
and
doesn't
matter
whether
that
happens,
runtime,
which
it
currently
does
using
the
servers
or
whether
it
happens
at
the
point
I'm,
where
you
read
that
file
and
configure
the
static
stuff
to
be
deployed
on
again
and
the
proxies
to
be
handled
via
the
reverse,
proxy
or
varnish
so
yeah,
it
can
be
deployed
to
a
community.
We
simple
static
to.
B
To
improve
and
yeah
caching
will
help,
but
right
now
it's
not
there
and
we
do
know
that
even
for
the
projects
that
have
fast
backends
and
do
aggressive
caching,
many
of
them
you
choose
not
to
do
any
server-side
rendering
anyway,
just
to
simplify
things.
The
point
to
the
PWA
is
to
get
to
a
quick
first
paint
yeah
and
usually,
if
you
do
it
right,
the
client-side
only
approach
and
can
get
you.
C
B
B
C
You
could
use
that
so
what
happens
with
that
is
you
can
make
your
own
Nora's,
liver,
Lourdes,
quad,
I,
guess
the
ones
you
said
HP
it
yeah.
So
for
those
there
are
loaders
already,
even
maybe
I
guess
if
I
can
find
something
for
mustache.
Maybe
we
can
use
the
assessment,
but
for
now
we
are
actually
done
with
and
his
team
will
find
which
will
be
served.
Even
if
you.
C
Products
page,
if
it's
pretty
similar,
except
for
these
set
of
lines,
we
are
taking
the
plugins
that
we
already
had
in
the
past
that
the
configure
that
function
is
kind
of
done,
and
then
we
are
adding
on
top
of
it.
The
first
one
we
are
adding,
as
distorting
which
you
can
use
any
variable,
because
it's
going
to
be
while
the
compile
is
being
done.
If
you
look
at
store
name
being
used
inside
inside
HTML,
and
you
can.
C
C
C
B
Would
want
to
put
into
the
template
yeah,
and
we
ultimately
want
to
put
this
into
bill
tack
as
part
of
the
configure,
but
we
had
Assad
saying
it's
so
common
that
people
are
going
to
want
to
query
the
schema
and
get
your
config
is
a
great
example.
We
should
just
be
able
to
hard-code
store
name
into
the
final,
build
just
for
simplicity,
sake,
yeah.
So
this
is
actually
the.
C
C
If
you
look
at
the
async
plugin,
all
it
does
is
takes
the
callback
and
construct
a
time,
and
then
it
just
puts
that
into
a
try-catch
because
it
doesn't,
he
doesn't
want
to
cancel
out
the
folder
pack
process
just
because
this
particular
callback
is
Nepali
and
all
it
does
is
called
constant
callback
function.
That's
like
a
asynchronous.
C
C
B
B
B
We
did
upward
because
of
specific
needs
that
happen
in
our
ecosystem,
where
there's
different
deployment
targets
and
just
push
the
fireplace
it's,
it's
got
a
run
with
Magento,
but
we
found
a
way
to
make
it
closer
to
the
way
everything
we
have.
That
runs
and
still
work
for
Magento,
and
that
is
a
great
win.
Well,
thank
you
very
much.
B
C
E
C
Yeah,
so
if
you
look
at
the
previous
develop
implementation,
we
had
given
like
300
and
370
fires,
the
width
and
height
for
that
image.
This
is
that
in
your
court,
this
is
combined
into
the
port.
But
now,
if
we
look
at
the
example
of
what
what
what
we
have
here,
look
at
the
responsive
images,
I'm
going
for
a
pixel
density
of
1,
and
if
you
look
at
this
image,
it
is
rendered
at
489
pixels,
like
it's
actually
eating
of
a
space
of
489.
C
But
it
is
downloading
it's
downloading
the
image
of
320
pixels.
That's
because
that's
actually
the
closest
a
breathable
one
inside
the
source,
and
this
is
the
phone
source
and
that
we
are
given
the
also
said
attribute
and
if
we
start
compressing
this
image
and
then
probably
change
the
device.
Pixel
ratio
to
something
something
like
a
pixel
to
pixel
3
has
a
device,
pixel
ratio
to
you.
Look
at
this
image,
even
though
it
was
only
rendering
at
199
with
200.
It
was
still
downloading
640
pixels
worth
of
an
image.
C
That's
because
200
pixels
into
2,
that's
400
and
the
closest
one
is
around
400
big
cells.
It
has
data
it
is
needed
to
render
this
particular
image.
The
closest
one
available
at
that
point
of
time
is
actually
640
pixels
and
that's
the
reason
why
it
has
downward
at
pick
image,
but
now
the
benefit
that
the
person
or
that
is
using
the
user,
is
having
us
he's
going
to
have
a
very
high
quality
image,
even
though
his
is
formal
is
actually
smaller
in
size.
This
one
factor
is
small
in
size
device.
D
B
Yeah,
so
the
store
doesn't
have
torches.
There
is
a
good
API
and
the
general
direction
of
Magento
architecture
is
to
move
away
from
having
the
Magento
platform.
Do
things
like
EU
management
does
do
it
right
now
and
it's
a
nice
system.
You
know
you
can
create
sizes
of
an
image
and
assign
roles
to
them
like
thumbnail
in
future
again,
because
those
aren't
present
in
the
API
yet
and
because
we
are
live
or
things
that
are
commerce.
We
are
going
another
direction
so,
instead
of
using
those
cached
images,
we
are
generating
them
on.
B
Why
we're
having
discussions
with
architecture
about
having
integrated
etiquette
alive,
but
there's
two
ways:
it's
done
right
now.
The
best
one
is,
if
you
have
from
a
gentle
cloud,
if
you
have
enterprise
class
Pro
to
your
cloud
and
you
have
the
fastly
IO
feature
on
it,
but
fastly
IO
is
grabbing
all
of
your
image
requests
through
the
fastly
CBN,
and
so
you
can
use
your
L
parameters
to
do
fast.
The
image
optimizations,
which
is
public
API.
You
can
do
before
that's
what
we're
doing
here,
because
the
attached
instance
I
believe
that's
my
problem.
B
It
does
use
fast.
The
IO
so
fast
we,
those
ok,
so
fastly,
is
generating
based
on
Europe,
renders
and
runs
here.
Toad
will
actually
auto
generate
those
your
elbows
for
your
sides
and
then
they
get
cached
so
they're,
not
always
all
right
yeah.
When
you
don't
have
past
the
audio,
the
PL
you
a
studio
server
that
runs
up
where
Jas
has
its
own
built-in
onboard
image,
made
aware
that
stimulates
the
exact
same
in
the
yeah.
C
Right
now,
and
so
we
always
sort
the
bits,
because
the
height
ratio
is
always
fortified.
This
is
specific
to
Vania
and
all
we
do
is
generates
or
set
using
this
particular
image
bits
and
also
generate
URL
for
each
of
these
myths.
What
it
does
is
make
a
map
of
it
and
just
joining
them
with
a
comma
and
that's
what
that's
okay,
so
this.
B
It
it
it's
going
to
be
a
little
bit
heavier
to
the
payload,
because
you
look
at
the
current
state.
There
are
some
places
where
some
of
this
is
my
fault,
where
the
images
are
not
properly
sized.
According
to
the
media
queries,
sometimes
you
get
really
low
resolution
images
of
sizes,
so
our
story
is
full
of.
F
B
C
If
you
look
at
the
current
implementation,
I'm
going
with
the
device,
pixel
ratio
of
two
and
still
if
you
look
at
the
image-
is
actually
picks
that
it
is
not
clear
if
you
look
at
the
newly
implemented
on
the
fuses
and
like
super
sharp
and
that's
what
you
want
your
users
to
have
a
better
experience
with
the
products.
So
it
depends
completely,
but
we
don't
want
to
maintain
all
these
virtual
services
we
only
have
so
set
is
utilize
again.
C
So
they
might
be
a
small
bundle.
Size
increase,
that's
because
now
it
has
more
options
to
use
it's
going
to
download
a
higher
resolution.
Even
this
mama
dog
come
back
to
the
previous
one,
irrespective
of
anything
is
coming
down
with
exact
solution.
That's
why
the
bundle
seismic
will
take,
but
then
the
experience
is
kung-fu
teacher
yeah.
C
C
B
C
So
that's
that's
this.
There
was
one
thing
actually
I
want
to
talk
about
it.
It's
a
community
thing
yeah.
So
if
we
have
seen
a
multiple
websites
out
there,
they
have
a
she
would
let
this
show
like
if
the
yeah
the
flow
kind
of
nightly
yeah
it's
coming.
Some
page
gets:
oh,
it's,
okay,
absolutely
yeah,
so
we
could
have
it
as
a
placeholder
whenever
the
image
is
actually
being
dominated,
because
sometimes
it
might
happen
that
you
want
to
download
a
bigger
image.
F
A
E
Cool,
so
so
Stephen
and
I
are
are
hard
at
work
on
Paragon
we're
trying
to
make
Paragon
actually
complete
here
in
the
next
next
few
months.
So
one
of
the
things
we
did,
one
of
the
things
we
showed
off
a
couple
weeks
ago,
was
some
work
on
the
Left
row,
where
we
have
made
application
state
like
user
and
the
drawer
and
catalog
available
via
context.
E
E
E
Can
simply
use
context
with
these
context
objects
to
get
the
read
up
state
without
having
to
connect
through
a
container
component
and
do
a
map
state
to
prop
your
map
dispatch
to
promise.
So
at
any
level
of
the
component
you
can
at
any
level
of
the
tree.
You
can
use
context
to
get
the
redux
state
you
need,
and
this
doesn't
come
with
a
performance
cost
like
Kinect
does
because
of
the
subscriptions.
E
So
you
can
just
you
can
do
this
as
many
times
as
you
need
to
and
totally
change
up
your
component
architecture,
rather
than
this
should
help
avoid
passing
a
lot
of
props
from
high
up
connected
components
down
to
lower
ones.
You
can
just
skip
straight
to
what
you
need,
so
we're
gonna
see
that
pretty
soon
and
the
other
thing
we're
talking
about
is,
we
did
get
some
new
graph
QL
coverage
that
we
notice
right
before
we
merge
to
the
left
artwork.
So
as
a
result,
when
you're
navigating
through
the
menu.
E
E
You
can
distinguish
between
branches
and
leaves,
however,
you
want
with
styling,
because
they're
different
components,
but
basically,
at
this
point,
we've
fully
exposed
everything
all
the
categories
in
the
tree
and
and
made
the
navigation
a
lot
snappier
as
a
result,
and
the
navigation
is
using
these
new.
These
new
slices
of
context
that
are
available.