►
From YouTube: Magento PWA Demo, 3 December 2018 (Sprint 30)
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
Great,
so
welcome
everybody.
So
today
marks
our
sprint
30
demo.
We've
got
lots
of
lots
of
things
to
cover
as
usual.
Specifically
we're
gonna
kick
things
off
with
with
with
some
post
2.3
work
from
Adrian.
So
he's
been
doing
some
some
nice
work
on
the
autocomplete
for
search.
This
is
gonna
share
with
us.
That'll
come
in
over
time,
but
then
switching
gears
over
to
some
development
documentation
updates
from
for
mr.
Kalka
Ben.
A
So
lots
of
lots
of
good
progress
as
we
headed
into
the
2.3
release
last
week
and
as
we
continue
to
make
make
make
progress,
especially
around
setup
configuration
and
really
building
your
first
PWA
for
that
one.
So
we'll
we'll
cover
him
second
and
then,
and
then
the
really
the
the
bulk
of
the
the
demo
today
is
going
to
be
about
the
essentially
the
venue
storefront,
and
so
what
I'd
like
to
do
as
a
as
a
non
engineer,
kind
of
walk
through
the
clone
to
preview
process.
A
So
so
that
you
really
get
a
chance
to
see
what
that
might
look
like
for
someone
who
doesn't
work
in
this
everyday
and
so
so
kind
of
walk
through
that.
And
then
and
then
you
know,
with
color
commentary,
of
course,
from
James,
Jimmy
and
Andy
on
that
one
and
then
afterwards,
kind
of
the
behind
the
scenes.
Tour
and
really
kind
of
a
walk
through
the
dev
tools.
For
this
and
so
I
know
a
lot
of
this
we've
covered
in
bits
and
pieces.
A
But
we
thought
it'd
be
a
really
good
idea
as
a
team
to
cover
this
in
a
in
kind
of
our
kind
of
our
milestone
demo
for
42.3
kind
of
seeing
it
all
together
a
lot
of
the
great
work,
even
though
it
wasn't
a
traditional
demo
vibe.
By
most
most
definitions,
it's
really
a
culmination
of
all
the
great
community
work.
That's
been
done
today,
whether
it
be
bar
green,
whether
it
be
calm,
wrap,
certainly
into
and
others,
and
so
we're
super
appreciative
of
that.
And
so
we
thought
we'd
take
the
time
to
do
that.
A
B
Thank
you,
I
will
share
my
screen,
so
you
can
see.
Okay,
let
me
know
if
you're
seeing
my
screen
looks
good
okay.
So
for
those
who
do
not
know,
my
name
is
Adrian
betsa
I'm,
a
front-end
developer
here
at
team,
true
and
I've
been
playing
around
with
PW
a
studio.
For
about
three
months
now
we
internally
we've
been
developing
custom
into
PW,
a
studio
team
for
learning
purposes.
You
may
have
seen
that
in
the
video,
but
two
weeks
ago,
I
have
started
contributing
to
PW
a
studio
branch.
B
B
B
So
this
search
bar
has
been
developed
by
the
community
member
and
I
have
built
the
suggestion
box
when
user
starts
typing.
So
if
we
start
typing
dress,
you
can
see
the
little
box
show
up
and
it
shows
the
category
suggestions
and
few
product
suggestions.
This
was
really
easy
to
build,
build
since
graph
QL
returns,
also
category
a
category
data
for
each
product
and
also
each
search.
B
Each
keystroke
has
been
D
bounced,
so
query
doesn't
fire
off
on
each
keystroke,
so
after
200
milliseconds
on
or
when
the
user
stops
typing.
That
is
when
we
fire
off
the
search.
Query.
Also
I
have
made
the
improvement
to
use
same
search,
query
for
the
search
results
page
and
for
autocomplete,
so
if
user
decides
to
hit
enter,
he
would
be
redirected
to
the
search
results,
page
email
immediately
and
it
would
be
displayed
right
away
since
the
results
have
been
cached
or
user
can
filter
by
category.
B
B
Alternatively,
users
can
click
on
the
progress,
suggested
products
right
away
and
they
will
be
redirected
to
the
product
page.
So
that
is
all
for
the
feature.
I
would
also
like
to
mention
that
we're
discussing
some
minor
lacs
improvements
and
and
user
interaction
with
this
component
and
I'm
currently
awaiting
feedback
from
the
team
on
this
feature,
and
if
you
have
any
questions
or
suggestions
like
you
know,.
C
D
Hey:
hey
sorry,
guys
who
wanted
to
ask
a
couple
questions
and
that's:
okay,
Adrian!
This
is
Misha
great
great
work
on
the
demo.
It
looks.
It
looks
great
just
a
couple
questions
once
you
just
confirm,
since
you
guys
are
using
the
graph
qo
ap
is
for
to
power
the
double
drop-down
suggestion
drop-down.
That
means
that
you
guys
are
gnostic
what
the
search
engine
is
configured
underneath
right,
whether
it's
my
sequel
or
elastic,
currently.
B
It's
currently
my
sequel,
if
I'm
correct
its
default,
Magento
I'm
not
really
sure
if
it's
going
to
be
really
100%
agnostic,
but
I
can
look
into
making
making
some
adjustments
to
it.
Since
we
have
these
micro
improvements,
where
we
display
category
name
once
we
filter
out
the
search
results
that
depends
on
the
API
I,
see
I,
see.
D
Yeah
that
makes
sense,
Thanks
I
would
yeah
definitely
at
least
test
to
see
how
the
heaves
with
elastic,
because
that
going
forward
you
know
it'll,
be
a
preferred
search
engine
of
choice
and
Magento,
and
my
sequel,
with
my
sequel,
being
deprecated,
so
I
think
that
the
generic
API
is
that
the
graphical
works
on
top
of
should
be
agnostic
to
the
engine.
But
if
you
guys
are
using
like
engine
specific
things
to
do
certain
custom
logic,
then
we
definitely
want
to
at
least
test
out
how
that
works.
Oh
thank.
B
You
also,
as
I've
said
before,
this
is
built
on
top
of
already
existing
search
search
functionality
that
has
been
in
developed
by
another
community
member.
So
we
also
need
to
pass
these
suggestions
to
that
member
also,
so
he
can
make
the
adjustments
on
his
branch
and
I
can
make
adjustments
on
mine,
yeah
I'm,
actually.
D
B
So
when
you're
typing,
when
you
finish
typing
it's
then
when
you
file
the
query
is
being
fired
off
and
you
get
the
results.
So
I
haven't
had
the
time
to
test
the
latency
and
all
that
it
was
a
simple
implementation
for
now
just
to
see
if
proof
of
concept,
basically
until
I
get
my
first
feedback
from
the
team.
Sure.
D
No,
that
sounds
great
thanks,
yeah
we
we.
We
appreciate
that
and
then
and
then
the
last
question,
sorry
to
to
bombard
you.
But
can
you
can
you
summarize
again
how
what
kind
of
the
logic
looks
like
on
the
high
level
for
finding
these
categories?
You
said
the
graphical
graphical
supports
showing
a
category
for
the
products
that
get
returned.
So
do
you
guys
just
look
at
those
and
aggregate
the
most
popular
ones
within
the
search
results,
or
how
does
how
do
you
guys
compiling
a
list
of
categories
yeah.
B
I
actually
wanted
to
explain
that,
but
I
think
to
have
skipped
over,
but
thank
you
for
reminding
me
of
course,
once
the
query
is
fired
off
with
products.
We
also
return
the
categories
one
product
can
be
in
multiple
categories,
so
you
can
get
an
array
of
categories
so
first
we
need
to
join
those
arrays
and
flatten
them
and
going
by
the
most.
B
We
didn't
adjust
these
to
reflect
the
most
popular
category,
but
we
only
extracted
the
unique
category
so
and
we
returned
four
categories
in
this
case,
as
you
can
see,
so
there
is
no
ending
complicated
logic
for
counting
how
many
returns,
how
many
results
for
each
category
we
get
since
the
API
only
returns.
The
first
page
of
results
I
see.
D
D
B
A
E
B
F
B
A
G
Thanks
so
this
print
was
pretty
light
because
two
days,
but
most
improvements
were
basically
to
fixing
broken
links
and
updating
references.
The
only
major
improvement
I
wanted
to
highlight
was
venya
project
structure
topic
just
now
reflects
what's
in
our
code
code
base,
so
that
is
you
want
to
get
up
on
that.
It's
for
the
venue
store
front
section,
project
structure.
G
A
A
This
might
be
a
helpful
way
to
kind
of
show
how
you
can
get
up
and
running,
because
we
we
tend
to
and
even
since
last
week
tend
to
get
a
lot
of
questions
on
how
to
get
started
for
this
one,
so
I'm
gonna.
What
I'm
gonna
do
is
kind
of
walk
through
this
at
a
very
business
level.
This
is
all
gonna,
be
a
culmination
of
all
the
great
work
from
you
know,
both
the
team
here,
but
also
the
team.
A
You
know
the
teams
all
over
the
world
for
that
one,
so
I'm
open
to
feedback
and
kind
of
we
can
use
it
some
time
to
kinda
go
back
and
forth,
but
you
know
I
kind
of
talk
about
how
things
work,
but
then
what
I
want
to
do
is
turn
it
over
to
it's
a
James
Jimmy
Andy
and
the
team.
You
know
if
there
are
any
any
kind
of
help
and
tools
are
kind
of
behind
the
scenes.
A
Walkthroughs
that
we've
been
talking
about
internally.
They
kind
of
support
that
case
as
well.
So
when
I
can
separate
those
two
and
then,
of
course,
we'll
have
have
some
time
for
questions
so
ELISA.
Let's
take
a
look
at
what
what
we've
got
here.
I'm
gonna
share
my
whole
screen.
Can
everybody
see
my
screen?
A
Alright,
alright,
so
again
for
those
who
those
aren't
familiar,
this
is
the
essentially
the
beginnings
of
fee
to
be
a
studio.
You
can
access
this
from
P
to
be
a
studio
IO.
So
if
you've
never
done
this
before,
one
of
the
great
things
you
can
use,
if
you're,
not
using
github
desktop
or
command
line,
is
to
download
the
whole
package
again
for
those
who
do
this
all
the
time.
This
is
pretty
rudimentary.
A
Well,
if
we
take
a
look
at
this
unzip
it
and
in
my
case
again
for
the
purposes
of
doing
a
lot
of
these
demos,
I
just
bring
it
over
to
my
desktop
for
the
purposes
of
typing,
because
they
do
this
line
a
lot
in
command
line.
I
just
shorten
that
up.
So
that's
not!
You
can
call
this
whatever
you'd
like
and
then
from
there.
You
can
go
into
the
desktop
from
the
term
terminal
itself.
A
So
what
we're
doing
is
sending
up
essentially
a
headless
instance
of
venya
right
there's,
definitely
a
more
technical
discussion
and
kind
of
walk
through
this,
a
lot
of
documentation
we
have,
but
really
the
ideas
were
for
creating
something
that
will
point
to
an
existing
Magento
2.3
instance.
In
this
sense,
in
this
case,
we're
actually
pointing
to
an
instance
that
James
himself
has
created
off-site
and
you'll
see
it
regularly
with
any
PR
that
gets
us
submitted.
A
We
use
this
as
a
way
to
kind
of
test
and
see
what
things
look
like,
especially
with
a
lot
of
the
venue
work,
but
if
you
want
to
look
at
a
fresh
instance,
this
is
this
is
one
way
to
do.
It
it'll
give
NPM
a
few
minutes
to
finish
up
here
again.
This
is
a
clean,
install
that
I
just
happen
to
be
running
on
my
desktop
to.
F
Clarify
that,
bearing
in
mind
that
this
toolkit
is
meant
for
external
use
and
that
this
demo
is
about
core
engineering
on
this
toolkit
installing
the
entire
mono
repo
takes
a
while,
because
that
is
the
use
case
where
you're
working
on
venía
or
on
build
pack
you're
working
on
the
core.
But
if
you
are
importing
these
packages
into
another
library,
you're
building
your
own
PWA,
you
can
expect
that
that's
install
and
build
process
is
much
much
shorter.
This
effectively
has
to
install
twice
in
order
to
share
dependencies.
A
That's
a
good
point,
James
and
so
yeah
and
I
think
the
case
that
we
really
liked
about
this.
A
lot
was
back
in
the
days,
especially
the
early
contribution,
where
you
know
you
have
add
a
new
contributors
who
want
to
get
up
and
run
started,
and
they
you
know
prior
to
to
having
a
reliable
docker
instance
or
something
into
that
manner.
This
is
really
really
valuable,
especially
for
those
who
are
less
familiar
with
Magento.
So
even
in
the
cases
where
we're
having
to
kind
of
do
this
twice,
you
know
behind
the
scenes
here.
A
So
anything,
it's
really
hats
off
to
James
in
the
work
behind
the
scenes
here,
but
yeah
with
like
like
like
a
lot
of
things,
there's
there's
more
work
to
be
done,
so
let's
take
a
look
at
the
build
in
the
run
piece
of
this
again.
The
these
commands
happen
to
be
copied
from
from
my
previous
history,
but
these
are
available
in
dev
box.
We
have
to
do.
Is
kick
this
off?
A
E
A
That's
that
so
this
will
be
the
first
time.
I
run
this
with
this
particular
instance,
so
you'll
see
a
little
bit
of
latent
latency
that
you
typically
wouldn't
see
and
something
that's
hosted
for
that.
So
please
note
that
and
because
this
is
local
I
don't
have
this
set
up
similar
to
the
publicly
available
version
which
is
running
on
the
server,
and
you
start
to
see
things
like
the
serviceworker
and
other
pieces
of
that.
That's
all
built
with
that
in
mind,
but
setup
locally.
A
A
Pick
any
item
here
just
pick
the
earrings
again
from
here,
since
this
is
non
configurable.
We
can
add
this
to
cart,
easy
enough.
We'll
have
two
items
and
carts
and
then
firmly,
let's
say
we
have
a
little
bit
of
you
know
a
little
bit
of
remorse.
Maybe
we
don't
want
to
add
to
buy
that
sundress
after
all,
pulling
in
some
against
with
a
great
work
from
bar,
green
and
team.
We
remove
that
and
then
oh
wait
a
minute.
Let's
see
if
the
internet
connection
goes
down,
turn
off
the
Wi-Fi.
A
F
Eric
I,
actually
I
actually
have
some
input
here.
It
is
real,
easy
to
simulate
offline
mode
in
Chrome,
and
this
is
a
great
demo
for
some
others,
because
from
Chrome
constantly
changes
their
dev
tools
and
I'm
sure
that
if
you
have
any
questions
about
how
that
impacts
process,
you
can
feel
free
to
give
them
to
Rowan
near
would
use
on
this
call.
If
that
is,
let
me
give
you
the
email
address.
It
is
non
kidding,
but
the
the
chrome
dev
tools
right
now
don't
make
it
super
easy
to
disable,
JavaScript,
etc.
F
A
A
All
right,
cool,
so
I
think
with
this
one
again:
we've
we've
actually
gone
offline
and
online.
We've
proven
that
with
blue
jeans
from
here,
we
want
to
do
a
quick
and
check
outs.
We've
got
some
basic
shipping
address
information
here,
which
I'll
pre
populates
with
Veronica
our
friend
saving
that
keep
in
mind.
We
do
have
payment
methods
and
shipping
methods
actually
coming
in
any
day
now.
So
so,
look
for
that
and
then
from
there
we
place
an
order.
Give
that
a
second.
This
is
actually
again
pinging
that
2.3
instance
that
James
is
set
up.
A
This
happens
to
be
order,
number
46
and
we're
complete.
So
so
that's
that-
and
so
there's
a
couple
things
that
are
happening
also
behind
the
scenes
we
demonstrated
for
those
who
could
catch
it
quickly.
What
offline
looks
like,
but
there's
also
some
awesome
key
considerations
once
this
is
set
up
in
a
hosted
environment
with
regard
to
a
traditional
PWA,
and
so
with
this
one
we
do
have
the
ability
to
open
this
up
in
venya.
A
The
purposes
of
kind
of
a
business
demo,
you
can
definitely
play
around
with
this
yourself.
You've
got
some
really
interesting
cases
on
authentication.
You
can
actually
log
in
as
Veronica
and
see
what
that
looks
like
we've
got
some
some
work
coming
relative
to
to
the
account
section
fairly
soon
from
our
from
our
friends
at
ePub.
We've
got
some
additional
work,
that's
coming
obviously
we're
on
search
and
then
we've
got
to
you
know,
get
some
content
cleanup.
A
So
what
you
see
here
may
look
a
bit
basic,
but
we've
actually
got
a
couple
couple
things
coming
in
that
that
were
just
after
the
list
relative
to
search
and
some
of
the
check
out
pieces
that
are
gonna
be
coming
in
very
very
soon,
but
again
for
the
purposes
of
especially
for
those
who
haven't
seen
it
or
playing
around
with
this.
Yet
you
know
how
quick
and
how?
How
long
would
it
take
to
set
this
up
and
get
this
play
around
with
this
yourself?
A
It
really
doesn't
take
a
lot
of
time
if
you,
if
you
make
that
one
change
and
copy
the
env
file,
and
then
you
you
fill
this
up
yourself,
you
get
the
ability
to
do
that.
You
can
actually
make
some
changes
and
and
get
used
to
this
again
for
those
who
are
here
and
contributing
this
as
old
news.
But
for
those
who
are
wondering
how
does
this
work,
because
we
continue
to
get
questions
on?
How
do
you
configure
this
as
a
theme
and
em2,
and
you
don't
from
that
one?
A
So
anyways
I
appreciate
everybody
bearing
with
me,
especially
when
we
have
went
offline
for
that
one,
but
it
looks
like
we
were
able
to
recover
nicely
in
that
one
and
yeah.
So
any
any
questions
we're
like
relative
to
the
function
allottee
here
before
I
switch
gears
to
mr.
Zeppelin
and
team
here
on
on
some
of
the
behind
the
scenes.
Work.
B
G
F
F
F
All
right,
you'll
notice
that
it
assumes
that
the
node
end
this
production
and
that
there's
no
specific
port
that's
been
set,
and
this
is
a
mode
that
is
ideal
for
binding
internally
to
a
cloud
deployment
container
like
our
now
SH
containers.
But
if
you
are
testing
for
local
developments,
a
cool
thing
that
you
can
do
is
set
the
node
and
manually
on
the
command
line
in
Windows.
This
works
a
little
differently,
and
so
we
can
have
a
Dappy
an
NPM
script
if
you
like,
but
right
now,
it's
very
simple
I
mean
you
set
that
up.
F
F
Your
dev
server
always
runs
in
a
very
similar
URL.
As
a
matter
of
fact,
it's
almost
exactly
the
same,
except
that
your
port
number
will
begin
with
an
8
instead
of
a
9.
That
is
a
quick
and
dirty
way
to
identify
whether
you
are
running
the
development
environment
which
hot
reloads
but
uses
much
larger
assets,
because
it's
not
fully
compressed
or
you
are
running
the
staging
environment
which
is
compressed,
but
it's
not
suitable
for
development.
F
So
just
a
neat
little
trick
to
identify
where
you're
at
and
now
again
I'm
going
to
run
the
stage
server
and
check
it
out.
So
the
first
thing
is
that
Eric
was
demonstrating
a
offline
mode.
The
great
thing
about
offline
mode
is
that
you
can
simulate
it,
especially
when
you're
in
the
mobile
node
now
I
opened
up
my
chrome
dev
tools,
but
they
immediately
simulated
a
mobile
device
because
I
have
the
dev
tool
set
automatically
to
be
mobile
device.
F
If
you
look
here,
I,
don't
know
if
that's
very
visible
to
you
guys,
but
there
is
an
icon
for
toggling
device,
toolbars
an
odd
way
of
putting
it,
but
it
does
in
fact
simulate
a
mobile
device
and
the
feature
detection
will
work
a
bit
differently,
though
you
can
actually
have
get
a
great
deal
of
control
over
that
by
setting
your
sensors
so
that
you
can
simulate
various
situations
in
your
simulated
phone.
Pretty
nice,
but
maybe
the
most
relevant
simulation
is
two
things
that
have
recently
been
added
to
venía.
F
That
I
wanted
to
get
a
quick
chance
to
demonstrate.
So
how
did
I
summon
this
very
useful?
Looking
panel?
It's
a
lot
like
on
an
editor
in
in
the
vein
of
phpstorm
or
vs
code.
There
is
a
hotkey
that
you
can
press
when
the
dev
tools
are
focused.
So
when
you've
clicked
inside
your
developer
tools
in
chrome,
you
can
press
command
shift,
P
or
ctrl
shift
P,
and
then
you
can
type
in
one
of
the
many
useful
and
immediate
commands.
A
lot
of
stuff
is
duplicated
from
the
UI.
F
I
can
go
immediately
to,
for
instance,
the
elements
panel,
but
what
I'm
most
interested
in
is
going
back
to
the
store
is
panel
or
actually
going
back
to
the
network
panel,
showing
the
console
and
then
disabling
JavaScript,
and
now
that
javascript
is
disabled.
You'll
see
that
indicated
with
a
little
exclamation
point
in
the
sources
panel,
and
then,
when
I
refresh
the
page,
you
might
observe
that
one
of
our
wonderful
community
members
has
contributed
a
javascript
is
disabled
view.
This
is
a
really
really
simple.
F
Html
page,
it's
enclosed
inside
a
no
script
tag
and
like
many
things
of
its
nature,
it
directs
you
to
a
helpful
site
called
enable
JavaScript
dot-com,
which
teaches
you
how
to
enable
JavaScript
in
your
browser
in
well
I'll,
just
say
several
languages.
If
your
language
is
missing,
I'm,
sorry
take
it
up
with
them.
It's
a
terrible
oversight
on
their
part,
but
yeah.
That
is
how
to
disable
JavaScript
and
try
to
interact
with
it.
Obviously,
there's
no
interaction
as
possible,
because
this
is
a
JavaScript
powered
application.
It's
worth
observing
what
that
actually
is
implemented.
F
F
We
have
a
simple
container
and
some
simple
style
which
is
written
in
a
very
terse
manner
in
order
to
enable
the
venía
appearance
without
having
to
import
any
style
sheets,
the
way
that
the
JavaScript
does
through
web
pack,
so
it's
pretty
straightforward,
it
doesn't
have
presently
localization
or
otherwise,
but
it
is
a
real,
simple
implementation.
That's
easy
to
look
at
in
the
future.
F
We
may
end
up
wanting
to
build
a
version
of
this:
that's
reuses
style
from
our
core
style
sheets
or
reuses,
the
rendering
of
a
particular
react
component
in
order
to
produce
this
HTML
that's
for
the
future,
and
that
would
be
a
fun
optimization
that
we
would
welcome
in
a
pull
request
as
it
stands.
This
adds
a
very
small
amount
of
pelo
of
less
than
one
kilobyte
to
every
page,
but
it
is
completely
disabled
when
javascript
is
enabled
which
I'm
going
to
do
now.
F
Whoops
here
that
and
there
we
are
we're
back
and
if
you
observe
there
is
no
server-side
detection,
it
is
still
rendering
this
content,
but
because
it
inside
it's
inside
a
no
script
tag,
it
doesn't
appear.
You
can
still
see
it
because
it
is
still
present
in
the
Dom
or
is
it
maybe
you
remove
the
no
script
eyes?
Oh
yeah
there.
It
is
there's
the
no
script
tag
and
as
browsers
must
do
by
definition,
no
script
tag
is
not
rendering
when
javascript
is
enabled.
So
that's
a
fun
thing.
That's
a
new
feature.
That's
been
added!
F
F
That's
what
it
is.
Do
you
take
offline
and
then
Chrome
stimulates
that
you're
offline
some
features
may
be
unavailable.
It
says
a
great
example
of
an
unavailable
feature
is
when
you
haven't
loaded
yet
because
I
just
tried
to
visit
a
category
page
that
my
fresh
new
copy
of
beignet
with
my
fresh
new
it
session
has
never
loaded
before,
but
press
the
back
button.
You'll
notice
that,
unlike
other
offline
applications,
which
say
now
every
page
is
inaccessible,
this
goes
back
to
the
original
view.
Now,
let's
go
online,
guys
stop
doing
that.
I
want
to
go
online.
F
You
notice
that
there
is
an
excellent
little
notifier.
That
says
you
are
online
that
subscribes
to
a
device
based
API
which
receives
Network
Status
change
events.
Now
I'm
gonna
go
to
accessories.
It's
no
longer
offline,
these
image,
optimizations.
These
images
will
be
much
faster
when
they're
optimized,
which
is
a
cool
upcoming
thing,
will
show
you
in
a
new
demo.
That's
got
these
gold
circular
rings.
Why
not
hey?
F
F
F
This
is
data
fetcher
on
that
one.
So
we
may,
we
may
actually
have
some
problems
with
the
product
page,
but
that's
something
that
we
rating
on
the
category
pages,
however,
remain
available.
So
those
things
have
been
logged
in
the
service
worker
and
the
service
worker
serves
them
back,
which
you
can
actually
see
here
in
the
the
Service
Worker
fetched
items,
which
is
something
you
can
identify
with
a
little
icon
of
a
gear
next
to
them.
F
Is
it
because
the
manifest
is
not
well
okay?
Well,
we'll
just
that
later,
I
may
end
up
having
to
kill
the
application
restarted,
because
it's
likely
is
not.
That
I
was
messing,
something
clearing
the
site,
data,
I'm,
registering
all
the
service
workers
and
we
go
to
service
workers
and
say
I'm
gonna
stir
get
rid
of
it,
and
then
we
close
reopen
a
new
session
then,
because,
if
any
in
that
session,.
F
And
there
was
a
manifest.json
now
the
manifest.json
is
what
enables
this
to
be
added
to
the
home
screen.
Thank
you
very
much
to
Paul
and
the
others
that
bargain
Ellison,
who
gave
us
this
fantastic
feature.
The
manifest.json
will,
let
us
add
it
to
the
home
screen
and
I
could
drag
it
to
the
dock
and
this
snack,
but
I
had
some
trouble
with
that
earlier
and
I
blame
Mojave
so
we'll
skip
that
demonstration.
F
But
we
will
show
that
there
is
such
a
thing
as
a
serviceworker
that
is
running
and
it
has
had
a
couple
of
errors
which
are
actually
due
to
the
dev
tools
and
are
a
known
issue
with
the
work
box
and
the
chrome
run
times.
But
we
can
probably
adjust
our
serviceworker
implementation
to
change
so
again
because
of
the
presence
of
that
serviceworker
as
I
navigate,
the
serviceworker
pulls
up
images
from
its
own
cache
they've
routes
to
do
that
cache
and
then,
when
I
go
offline
or
even
when
I
stay
online,
you
might
see.
F
F
Sensors
to
simulate
different
user
agents,
we
can
use
this
menu
to
simulate
different
form
factors,
but
we
don't
actually
know
about
the
browser
rendering
engine
now
in
OS
10,
you
can
summon
with
Xcode
a
thing
called
simulator,
and
this
is
actually
gonna
run
a
virtual
machine
that
has
an
iPhone
in
it,
because
it's
a
virtual
machine
with
an
iPhone
in
it.
It's
going
to
have
to
boot
like
an
iPhone
does,
which
is
to
say
mysteriously
and
at
different
lengths
and
at
different
times
you
guys
can
see
it
right.
F
F
There's
no
obvious
way
in
the
simulator
to
open
developer
tools,
or
if
there
is
then
it's
relatively
new.
Let
me
show
you
how
that
how
that
will
be
done,
because
the
iPhone
is
running
Safari.
You
would
want
to
launch
your
Safari
browser
because
the
Safari
browser
and
it's
develop
menu
which
you
may
have
to
turn
on.
You
have
to
Google
how
to
turn
this
on.
F
It's
looks
around
your
system
for
other
instances
of
the
Safari
web
browser
to
which
it
can
connect
notice
that
it
has
a
simulator
there
and
we
can
actually
visit
and
open
an
inspector
for
that
simulator
instance.
So
we
just
clear
this
log
here
and
you
navigate
back
to
our
simulator,
we'll
find
that
as
we
go
back,
we
are
loading
we
are
executing
and
the
graph
QL
has
come
down
so
now
in
this
environment
we
are
definitely
running
iOS,
Safari
and
iOS.
Safari
has
its
own
particular
abilities.
F
Like
Add
to
Home
screen
and
right
now,
the
venía
icons
are
downloading.
It
should
be
replaced
ultimately
with
the
venía
icon.
I
think
there
might
be
a
mistake
with
the
manifest
in
this
case,
I
think
Magento.
Now
that
Sh
might
not
be
exposed,
but
we
can
go
ahead
and
observe
that
there
is
no
longer
any
browser.
Chrome
here.
F
Then
he
app
to
be
able
to
very
quickly
get
to
the
Julian
side.
Now,
that's
how
actually
happens
not
to
be
working?
No,
it
is.
It
just
had
to
load
from
the
serviceworker
because
it
wasn't
in
the
run
time
notice
how
fast
that
happens.
That's
because
the
app
itself
and
the
website
are
sharing
a
cache
good
stuff.
Now
the
way
to
simulate
in
android
is
perhaps
a
little
bit
harder,
but
not
too
hard.
F
F
F
That
is
a
Chromebook,
and
you
might
observe
that
on
this
Chromebook
itself
an
instance
of
venía
is
running,
and
is
this
the
Magento
dadada
SH
version
of
enniaa
I
know
it
is
not
we're
using
the
new
crostini
linux
subsystem
inside
Chrome
OS
to
do
development
on
a
Chromebook,
a
very
small
and
beautiful
Chromebook.
I
might
add.
You
can
do
development
on
PWA
studio
in
Chrome
OS
in
Linux
and
it'll
work
just
great.
F
H
F
H
F
Didn't
hear
me
yeah
yeah.
Well,
the
the
pixel
book
is
the
most
powerful
Chromebook
I
think
that
the
the
main
obstacle
that
you
might
find
as
a
project
grows
is
RAM
and
potentially
also
the
filesystem
limitations
of
Chrome
OS
when
you're
doing
development,
you,
typically
in
the
PWA
studio
and
in
general,
WebP
active
development
flow.
You
end
up
having
to
have
a
lot
of
open
file
handlers
and
that
takes
up
some
ram.
Cpu
itself
is
usually
not
a
huge
concern.
F
The
the
actual
calculations
that
webpack
needs
to
run
in
order
to
continue
doing
build
building
are
not
super
CPU
intensive
in
dev
mode
in
build
mode.
They
are
because
they
all
have
to
happen
at
once,
but
a
Chromebook
doing
a
full
production
build
is
not
something
that
necessarily
needs
to
be
part
of
your
regular
workflow.
So
it's
totally
doable
I
found
it
to
be
nice
and
usable
and
and
cool
right
now.
The
the
thing
we're
still
working
on
with
the
Chromebook
is
doing
customized
domains,
but
you
don't
need
customized
domains.
F
A
Yeah
James,
this
is
Eric,
I,
think
we're
good
in
terms
of
the
agenda
items,
and
so
you
know
turning
this
really,
the
you
know
the
whole
team.
If
there
any
specific
questions
between
this,
some
of
the
vending
work
or
even
kind
of
going
back
to
some
of
the
search
and
Docs
work
that
was
shared
as
well,
any
any
questions
or
comments.
F
There's,
there's
mostly
a
concern
right
now
about
trying
to
integrate
our
specific
PWA
supports
mechanisms
that
we
have
in
our
developer
tools
like
creating
a
new
domain
so
that
your
service
workers
are
boxed
in
the
the
Google
work
box
tool
is
also
innovating
rapidly
to
help
us
out.
One
thing
that
you
might
find
is
that
you,
you
can't
test
out
your
serviceworker
in
developer
mode
unless
two
things
are
true
and
I'll
share
my
screen
and
show
you.
F
First
of
all,
you
need
to
make
sure
that
you
are
successfully
running
on
a
secure
domain,
now
I'm
doing
that,
because
when
I
originally
built
this
this
application,
it
asked
me,
as
you
might
find
that
it
asks
you
to
add.
Your
administer,
provide
your
administrator
password
so
that
it
can
do
that.
But
let's
say
because
I
happen
to
know
that
that
provisioning
of
a
domain
name
is
based
on
the
path
of
the
repository
I'm,
going
to
do
a
little
trick.
F
It's
gonna
bother
this
because
it
notices
that
there
is
no
longer
a
customized
domain
and
because
it's
not
secure
you'll
find
that
the
Service
Worker
does
not
work.
It's
not
installed.
They
do
to
make
sure
to
have
a
secure
domain.
The
way
to
do
that
is,
first
of
all,
you
have
to
kind
of
start
from
scratch
and
we're
still
working
on
a
way
to
kind
of
reprovision
this,
but
especially
on
a
Mac
in
your
teaching
you'll
find
that
there
is
a
dev
cert,
which
is
a
central
certification
Authority
that
you
can
feel
free
to
delete.
F
Then,
once
that's
done
and
keychain
access
will
ask
you
for
your
password
zillion
times.
It'll.
Ask
you
twice
for
each
thing:
you
try
to
delete
multiple
things
so
watch
out
for
that.
There's
also
another
quick
command
to
run,
which
again
we're
working
on
automating
this
process.
But
you
don't
have
to
remember
it
for
now,
which
is
that
dead,
cert
stores,
its
certificates
in
a
dead
cert
folder.
F
F
Hopefully,
my
password
did
not
get
visible
in
blue
jeans
in
some
way
and
once
I've
entered
my
password.
What
its
gonna
do
is
edit
the
Etsy
host
file
and
it's
going
to
provision
a
new
SSL
certificate.
It's
taken
a
little
while,
but
it
does
happen.
That's
because
open
SSL
has
to
do
some
serious
work
and
notice
that
the
URL
has
changed,
because
it's
a
hash
of
the
path
in
my
path:
change
in
PWA,
studio
to
the
PWA
studio
demo.
F
So
I
know
that
we've
sort
of
gone
over
some
of
those
things
before,
but
now
that
service
workers
are
in
the
mix.
I
think
it's
really
important
to
note
that
it's
that
it's
necessary
to
do
that
in
order
to
get
to
Service
Worker
editing,
however,
observe
that
the
Service
Worker
is
still
not
there.
So,
what's
missing,
you've
probably
seen
that
omitting,
those
Service
Worker
in
development
mode
notice
and
that's
because
in
development
mode
you
often
want
your
your
resources
to
reload.
F
A
lot
of
projects,
including
create
react,
react
at
the
news
service
workers
have
struggled
with
this,
so
our
default
behavior
is
to
turn
off
service
workers
in
our
service
worker
plug-in
when
you're
in
development
now.
But
you
can
change
this
either
by
adding
an
environment
variable
at
runtime
or
by
editing
your
env
file,
which
is
the
way
I'm
going
to
do
it.
F
In
packages
venía
concept
env,
there
is
a
little
bit
of
documentation
here
that
says
set
this
to
true
to
force
service
workers
in
development.
Well,
that's
what
I
want
to
do,
though
I've
uncommented,
the
line
and
it's
set
to
1,
which
equates
to
true
in
the
world
of
environment
variables
and
snow
thanks,
I!
Don't
care
about
that
then!
F
You'll
notice
that
that
note
that
notice
about
disabled
service
workers
does
not
appear
and
when
I
refresh
service
workers
installed,
so
we
still
had
some
work
to
do.
Debug
the
service
worker
since
service
workers
since
work
box
looks
at
the
local
URL
to
determine
whether
it's
local,
it's
not
giving
us
the
dev
versions
of
the
service
worker,
giving
us
production
versions
we're
working
on
fixing
that.
F
F
F
By
doing
enable
Service,
Worker
debugging
equals
1
and
then
npm
run
welcome
on
stage
but
watch
Benia
and
sorry
about
them.
Yelling
at
me,
because
my
file
is
imperfect,
so
again
observed
that,
even
though
the
env
file
still
doesn't
have
the
environment
variable,
you
can
add
it
for
the
duration
of
one
session
also
works
I'll,
beat
with
different
syntax
in
Windows
and
and
everything
else.
F
H
F
A
Cool
all
right,
well,
good!
Well,
thank
you!
So
much
everybody
a
couple
housekeeping
items
as
we
as
we
start
to
get
more
into
social
in
the
next
phase
beyond
2.3.
So
a
lot
of
work
ahead,
you
know
James
in
team
and
working
really
heavily
on
the
cloud
enablement
piece,
but
for
those
who
are
following
along
in
Zen
hub
there's
a
lot
of
great
work,
that's
that's
being
developed
and
merged,
and
so
look
for
look
for
progress
on
the
the
ship
and
payment
methods
and
for
work
on
search.
A
Look
for
something
working
on
payments
itself,
so
we're
doing
some
some
early
work
on
that
and
then
just
you
know
again.
Thank
you
to
everybody.
I
know:
we've
been
a
little
bit
prolific
online
recently,
but
I
want
to
make
sure
that
you
know
this.
This
really
has
been
the
result
of
everybody,
both
internally
and
externally
on
here.
A
So
I
really
think
everybody
here
in
the
room,
but
then
also
you
know,
as
you
saw
you
know,
the
work
that
you
saw
here,
especially
in
the
venya
piece,
was
it
was
a
big
part
of
you
know
the
efforts
from
from
artem,
obviously
Adrian.
Looking
forward
and
then
Paul
me,
the
VAR,
Green
Team
beyond
that
and
of
course,
consultation
from
here
in
Rouen
all
these
folks
on
the
call
gear.
So
you
know
don't
don't
you
know,
as
you
see
this,
you
have
questions
and
you
like
what
you
see.
Don't
just
don't
just
thank
guys.
A
Thank
thank
everybody
here
for
that,
and
so
it's
been
a
it's
been
a
huge
team
effort
and
looking
forward
to
the
next
turn
as
we
look
to
a
build
out
optimize
and
find
find
ways
to
to
put
this
up
and
cloud
in
a
way
that
that
everyone's
gonna
be
able
to
really
really
take
advantage
of.
So
thank
you
again
and
then
and
then
in
terms
of
next
next
step.
A
So
we've
got
our
our
next
grooming
on
Friday
and
then
look
for
us
to
mix
it
up,
but
I
think
I've
talked
to
you
guys
that
individually,
but
I
want
to
move
away
from
the
Sprint's
and
really
look
at
a
more
proper
Kanban
model
for
the
team.
These
these,
these
iterations
work
really
well,
at
least
in
terms
of
time
boxing
things
but
I
think
as
a
team.
A
We
can
get
a
do
a
better
job
at
grooming
and
looking
at
ways
for
us
to
be
more
independent
relative
to
to
the
work
that
be
picked
up
and
that
and
the
work
that
they
can
be
produced
and
really
consumed
by
the
team,
and
so
look
for
some
updates
on
that.
We'll
talk
about
that
on
Friday,
but
would
obviously
be
any
questions
about
that.
Let
us
know,
but
it
still
means
regular
meetings.
A
The
demos
will
include
both
in
progress
and
finished
work,
but
then
the
grooming
will
really
help
us
pare
down
the
work
that
needs
to
be
done
again
as
we
as
we
pick
up
the
velocity
after
2.3.
So
thank
you
again
to
everybody,
as
always,
and
for
the
folks
who
presented
today
have
a
have
a
great
rest
of
your
day
and
have
a
great
rest.
Every
week.
Okay,.