►
From YouTube: PWA Community Meeting, February 22, 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
great
so
it
looks
like
we
have
good
participation
here
all
right,
so
some
big
news
to
cover
today
we'll
turn
it
over
to
James.
We,
we
obviously
had
a
big
release
yesterday,
so
we
want
to
talk
kind
of
high-level
or
as
detailed
as
we
want
to
go
on
what
was
in
that
release.
Why
it's
important
after
that?
You
know,
I,
don't
know
that
we'll
have
much
in
terms
of
demo,
I
think
barbering,
I
think
I
talked
about
last
week's
I,
don't
from
you
guys!
I
think
you
guys
aren't
ready.
A
Maybe
this
week,
maybe
we're
looking
at
defer
that
maybe
to
the
next
week.
So
that's
fine
as
well.
So
what
kind
of
just
do
open
floor
for
any
questions,
demos,
topics
of
discussion
and
then
high-level
all
how
quickly
about
what's
the
output
of
sort
of
working
sessions
you've
had
this
week
didn't
really
drive
the
priority
for
upcoming
development
on
the
on
the
project
and
we'll
kind
of
cover
that
really
high-level
views,
the
team
hasn't
had
time
to
really
break
down
that
there's
high-level
at
big
kind
of
initiative,
level,
concepts
or
buckets
of
work.
C
Need
a
guess
from
somebody:
can
you
can
you
see
my
screen?
Okay,
fantastic
yeah,
I,
don't
know,
I
thought
I
thought
it
was
like.
Can
you
see
this
release?
Well,
since
you
didn't
do
very
much
announcing,
except
for
like
four
cryptic
posts
on
on
Twitter,
you
know,
then,
maybe
you
were
just
looking
right
at
get.
We
have
released
PW
a
studio
version,
2.0
point,
though
this
is
a
long
time
coming
in
the
interest
of
transparency.
C
I
should
say
that
we
intended
to
do
this
release
months
ago,
partly
because
we
didn't
want
this
release
to
be
a
gigantic
fanfare.
We
simply
wanted
to
issue
a
version
of
pwace
to
do
that
was
major
release
that
you
could
set
your
NPM
dependencies
and
new
projects
on,
and
that
was
fully
compatible
with
the
release.
Magento
2.34.
No,
that
came
out
at
the
same
time
again
in
the
interest
of
transparency.
What
held
us
up
was.
C
In
fact,
we
are
about
to
redirect
our
demo
URL
to
use
that
professional
cloud
instance.
So
you
can
see
how
the
PWA
venya
can
perform
identically
on
a
totally
different
server
architecture.
It's
a
great
demonstration
of
the
portability
of
our
PWA
architecture.
So
that's
done
and
with
the
final
support
from
that,
we
have
what
we
consider
to
be
release
that
is
ready
to
start
semantically,
versioning
and
supporting
in
its
first
iteration
and
we're
extremely
happy
about
that.
C
As
I
mentioned
on
Twitter,
if
you're
already
using
PW
a
studio
and
you've
been
keeping
track
of
it,
as
is
true
for
most
people
on
this
call,
then
most
of
these
features
and
new
editions
are
not
a
surprise
to
you.
They've
been
merged
in
they've,
been
heavily
regressed
and
tested,
and
the
release
points
was
chosen
after
we
took
some
time
off
for
merging
in
new
features.
C
But
what
is
significant
to
you
is
that
with
semantic
versioning,
we
are
now
obeying
the
semantic
version
constraints,
and
that
means
that
if
we
issue
any
change
to
the
public,
API
is
to
use
in
PW
a
studio.
The
methods
in
the
build
pack
plugins
the
methods
and
the
Peregrine's
components
and
the
behaviors
of
such
or
any
of
the
publicly
exposed
methods
of
any
ax
components.
Then
that
means
that
we
issue
a
full
major
release.
C
So
PW
a
Studio
3.0
point
now
and
it
may
come
out
quickly
and
if
you
were
accustomed
to
the
versioning
patterns
of
Magento
itself,
that
may
seem
a
little
disorienting
because
of
the
major
release
seeming
to
imply
that
you
can
have
to
a
major
change
and
that's
not
really
the
case.
We're
going
to
do
a
major
release
for
any
breaking
change.
So
it's
basically
just
an
indication
that
there
will
be
some
code
intervention
necessary
to
keep
your
code
working.
C
So
a
major
release
is
simply
a
signal
of
that
and
because
we're
using
proper
dependency
management,
not
just
in
composer
now,
but
also
in
NPM.
You
can
easily
choose
simply
not
to
let
that
flow
in
by
using
just
the
defaults.
Npm
some
cember
specifier,
the
caret
range
carrots
to
point
0.0,
which
guarantees
that
you
can
accept
all
minor
and
patch
releases
automatically
from
2.0,
and
you
can
upgrade
to
3.0
if
it
comes
out
when
it
comes
out
at
4.0
and
1718
point.
C
Oh,
when
you're
good
and
ready
and
that's
the
major
release
behavior
for
anything
that
is
additive
to
existing
api's
but
does
not
modify
any
existing
methods
which
would
be
able
to
flow
into
your
app.
Even
if
you
don't
take
advantage
immediately
of
the
new
functionality,
it
would
flow
in
without
breakage.
That
would
be
a
minor
release.
So
we
would
release
PWA
studio,
2.1
point,
oh
two
point
2.0
and
lastly,
or
patches
or
hot
fixes,
which
don't
add
public
api
but
may
correct
an
unexpected
behavior
or
add
a
performance,
improvement
or
fix
crash.
C
Those
would
be
patch
releases,
which
is
the
last
decimal
point
to
point.
0.1
2.0
point
2
to
point.
0.38
cetera-
and
you
may
see
this
occurring
as
fast
follows,
because
there
is
additional
functionality
that
we've
been
waiting
waiting
excitedly
to
start
to
integrate.
But
we
wanted
to
have
this
2.0
point.
I'll
release
be
stable,
so
that's
the
major
change
that
you'll
experience
if
you're
somebody
on
this
call
who's
been
using
this
code
and
working
on
it,
but
just
as
a
broader
kind
of
announcement.
C
Apart
from
just
me
talking
about
it
right
now
and
I
hope,
everyone's
taking
copious
notes
is
to
go
to
the
places
where
you
would
normally
find
the
release
of
a
software
library,
which
in
many
ways
is
what
PWA
studios
packages
are
as
libraries.
So
in
github,
the
Lisa's
section
is
going
to
show
you
the
release
object,
which
contains
the
changelog
associated
with
the
git
tag
that
we
pushed
and
there's
a
great
deal
of
good
information
in
here
links
to
issues
that
still
exist,
links
to
pull
requests
that
we
merged
and
summaries
of
the
documentation
updates.
C
This
document
is
designed
not
just
for
developers
to
consume
some
of
the
more
detailed
stuff,
but
also
for
business
users
and
high-level
project
managers,
etc.
To
be
able
to
just
read
some
bullet
points
about
the
important
things
we
did,
that
impact
your
timeline,
your
business
and
the
features
of
the
PWA.
So
this
is
one
place
to
see
everything,
but
you
might
notice
that
the
contents
of
this
release
object
are
identical
to
the
contents
of
the
new
change
log,
which
we
keep
up
to
date
and
change.
C
Log
is
a
conventional
document
that
you're
all
familiar
with
that
we're
going
to
keep
up
to
date
with
hot
fixes
and
patches,
and
this
list
will
kind
of
continue
and
the
release
object
will
be
populated
with
the
contents
of
the
most
recent
change
log.
Another
place
to
see.
All
of
this
great
information
is
on
PW,
a
studio
IO
which
links
to
the
current
documentation
and
will
have
up-to-date
and
now
stable
and
semantically
versioned
descriptions
of
a
standard
setup
for
core
contribution
of
any
a
sample
data
installation
process.
C
Some
of
the
brand-new
amazing
features
like
Braintree
direct
check
out
integration.
Thank
you
to
Andy
Terranova,
who
single-handedly
added
that
to
us
and
some
of
the
more
detailed
component
specifications
which
which
have
some
sort
of
UX
description
to
them,
which
have
some
description
of
their
behaviors
and
internally
have
exposed
public
API
s,
which
your
any
of
your
code,
editors,
if
they
have
support
for
detection
of
type
script
or
JavaScript
definitions,
should
be
Auto.
Completing
for
you
and
helping
you
to
get
things
going.
Another
place
that
you
can
see.
C
The
results
of
our
work
is
in
the
NPM
package
manager.
Now,
if
you
go
to,
for
instance,
NPM
J's
compact
and
then
use
the
at
Magento
namespace,
where
we're
putting
all
of
our
stuff
and
you
go
to
city
I,
don't
know
PWA
buildpack,
which
would
be
Devdutt
Endon,
see
that
you'd
import
in
any
independent
project.
Then
you
can
see
that
we
have
released
two
point
0.0
online.
Now
we
try
to
centralize
the
documentation
so
where
you
might
expect
a
full
readme
like
in
github.
C
We
have
you
redirected
to
the
documentation
site
and
it
is
just
to
keep
things
very
consistent
across
the
board,
but
the
not
only
the
package
PWA
build
packed,
but
also
the
package
Peregrine,
which
we
should
specify
it's
not
yet
full
and
functionality,
but
we're
iterating
on
it
very
fast
and
the
package
venía,
which
you
may
end
up
using
because
it's
modular
capabilities.
Allow
you
to
import
individual
venía
components
into
your
product,
as
I
demonstrated
on
an
earlier
call,
and
all
of
these
are
live
as
well
as.
C
All
of
these
are
available
now
and
are
now
present
in
the
I
know
what
the
thing
that's
so
long,
oh
yay,
we
might
be
getting
a
little
bit
of
a.
We
might
be
getting
hug
to
death
here
in
a
couple
of
places,
we'll
let
you
know,
but
all
of
these
are
now
available
to
install
via
the
classic
NPM
install
or
a
yarn
ad
package
manager,
client
functionality,
and
once
those
are
installed
those
package
managers
will
they
start
to
behave
a
little
differently
because
of
the
the
semantic
versioning
now
being
majorly
released.
C
You
will
you'll
see
those
package
managers
bringing
in
patches
and
even
minor
releases
automatically,
and
you
have
really
pinpoint
control
over
that
through
the
use
of
the
semantic
versioning
string
so
again
for
developer,
facing
the
semantic.
Versioning
is
kind
of
the
major
change
and
improvement
that
you're
going
to
see,
and
we
also
just
for
the
purposes
of
everyone
who
wants
to
get
some
great
sort
of
rolling
updates
of
what
we're
doing
and
how
it's
coming
out.
C
We
have
the
release,
object
and
that's
for
the
consumption
not
only
of
you
guys,
but
for
your
managers
and
for
the
project
managers
of
the
product.
People
who
want
to
use
PWA
studio,
we're
very
excited
about
it
again.
We're
probably
gonna
follow
up
with
follow-on
releases
but
they're
going
to
be
semantically
versioned
and
any
questions
about
its
any
reports
of
issues
with
it.
Please
let
us
know
both
here
and
in
the
community
slack
or
just
you
know,
slide
in
to
mine
she's
on
Twitter.
If
you
want
to
do
that
all
right.
Thank
you
very
much.
A
E
B
B
B
B
B
B
A
All
right
so
then
quickly
I
guess
to
wrap
up.
Here's
relatively
short
update
the
team
went
through
this
week
and
really
we
sat
down
and
tried
to
map
out
all
of
the
work
that
we
need
to
do
the
next
36
days
and
also
some
longer-term
work.
So
we
could
really
fleshed
out
our
roadmap
for
this
year,
I'd
say
at
a
high
level
coming
up
for
the
team.
Our
focus
is
mostly
around
things
that
LM
kind
of
already
indicated
and
Jimmy's
talking
about
with,
with
building
out
Peregrine
as
a
concept
in
the
fully
fledged
component
library.
A
Our
focus
also
will
be
on
venya
and
continuing
our
effort
on
venya
and
what
that
means
for
many
of
being
a
storefront
versus
a
theme
which
is
also
a
new
topic
that
we've
put
into
our
Docs,
that
change
soccer
games,
launch
to
the
docs.
So
more
effort
around
that,
and
then
the
third
I
think
highest
priority.
For
us
right
now
is
the
concept
of
extensibility
and
what
that
means
and
enabling
expensive
extensions
for
pwace
to
do
so.
A
As
we
continue
to
answer
some
of
the
questions
we
have
around
those
topics,
you'll
see
in
our
repository
on
our
board,
will
create
epics
and
stories
that
relate
to
these
topics
and
relate
to
those
buckets
of
work.
So,
if
you're
interested
in
kind
of
the
direction
we're
headed
in
justjust
stay
tuned
in
to
our
board,
of
course,
we'll
keep
everyone
up
to
date
during
this
meeting
on
how
things
are
progressing
against
those
topics,
but
I'd
say
at
a
high
level.
Those
are
those
are
our
priorities
for
for
immediate.
E
Upcoming
work
right,
I
know
that
a
lot
of
you
guys
have
been
have
been
asking
for
a
long
time
when
we
were
finally
going
to
get
to
fleshing
out
this
Peregrine
concept.
You
know
of
actually
being
a
library
of
components
that
are
worth
using
and
what
that's
going
to
look
like,
because
we've
been
pretty
much
focused
exclusively
on
venía
this
whole
time.
E
You
know
all
the
works
but
going
into
venía
as
for
the
concept
here,
so
we're
we're
basically,
finally
ready
to
to
really
start
translating
stuff
from
venía
into
Peregrine's
and
and
we're
gonna
have
some
some
vision,
documentation
on
what
exactly
that
process
looks
like
what
the
what
the
differences
are
between
of
any
component
and
a
programming
component.
So
there's
going
to
be
a
lot
of
opportunity
to
infer
for
people
to
get
involved
at
the
component
level.
E
You
know
and
not
just
it's
not
just
working
on
specific
features
right,
but
like
really
getting
involved
with
the
American
for
the
first
time
and
then
also
you
know,
the
other
part
of
that
right
is
we're.
Gonna
start
looking
at
what
it
takes
to
make
a
more
luma
like
experience,
or
you
know,
for
a
storefront
right
and
so
whether
that's,
whether
that's
turning
Benia
into
something
that's
more
easily
configurable
or
whether
that's
something
entirely
separate.
E
D
A
C
C
That's
that's
gonna
enable
a
lot
of
great
stuff
and
I'm
proud
of
us
for
waiting.
You
know
we
could
have
created
a
great
deal
of
Peregrine's
API,
which
we
would
have
then
had
to
make
a
big
changes
and
I've
been
commenting
that
as
the
folks
who
build
an
ecosystem,
we
have
to
be
a
little
bit
more
careful
about
introducing
lots
of
innovations,
because
there
is
this
pressure
for
all
of
you
guys
to
begin
building
projects
on
what
we've
made
and
we
don't
want
to
shift
the
platform
around
you.