►
From YouTube: 2020-09-16 JavaScript SIG
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
B
B
B
B
B
B
Should
we
wait
more
because
still
many
people
join
it,
I'm
not
sure
if
there'll
be.
C
B
Okay,
so
today
I'll
run
it
because
daniel
is
on
vacation,
we
don't
have
many
things
in
agenda
basically,
and
the
number
of
prs
is
grown,
so
please
review
them
with
regards
to
to
ga,
and
there
is
just
one
pr
that
you
know
I
think
you
might
open
here.
So
it's
ready
for
reviews.
B
It's
been
just
converted,
so
please,
radio
and
then
the
next
one
from
the
previous
meeting
has
already
been
reviewed
like
three
times
so
I
think
it
would
be
measured
so
other
than
that
we
still
have
few
things
left
in
ga,
which
hasn't
started
yet
just
wondering,
but
I
think
no
one
is
here
today
which
which
the
things
were
assigned
to
them
left.
A
Yeah,
I'm
salzman
yeah,
it's
my
first
meeting,
so
I
can
so
can
I
can
just
put
my
name
there
right.
A
A
Yeah
true
yeah
yeah,
so
we
we're
looking
to
see
where,
where
is
the
best
place,
we
can
add
value
to
the
community.
So
we
just
figure
out:
okay,
let's
just
at
least
start
with
like
participate
in
these
meetings.
So.
B
B
So,
basically,
if
you
want
to
participate,
you
are
more
than
welcome.
If
you
just
open
the
open,
telemetry
gs
on
the
github,
you
can
see
the
issue.
Some
of
them
has
attack
like
up
for
grabs
and
good
first
issue.
So
this
is
something
you
can
definitely
focus
on,
because
this
is
like
a
good
start.
B
B
D
B
Not
really
because
quite
often
many
things
are
like
either,
for
they
are
not
only
for
node,
but
they
both
for
not
and
for
web
sure.
So
the
only
difference
is
that
we
create
a
platform
folder
and
then
we
can
differentiate
between
if
there
is
any
difference
between
weapons
and
not
that
that's
the
place
where
what
you
should
differentiate,
but
other
than
that
most
of
the
stuff
is
meant
to
work
in
the
web
and
not
with
just
few
exceptions
but
other
than
that.
Most
of
the
stuff,
especially
api
and
sdk,
works
fine
in
buff.
B
C
There
is
an
entirely
second
repo
for
contrib,
which
is
all
the
instrumentation
yeah.
So
I
think
that's
good
to
have
in
mind
that
stuff
really
doesn't
end
up
like
on
this
required
for
ga
list.
It's
really
kind
of
like
focused
on
sdk
and
api
functionality,
but
you
know
users
always
care
about
about
instrumentation
and
kind
of
coverage
there.
So
I
think
yeah
yeah,
I
mean
that's.
C
I
don't
know
what
the
state
of
the
issues
are
there
and
if
they
always
reflect
what
people
really
want.
I
think
yeah.
D
D
B
B
But
if
you
are
interested
like,
for
example,
there's
a
plug-in
for
the
react,
but
it
only
supports
the
the
standard
components,
so
it
doesn't
work
with
react
hooks.
So
this
is
also
something
like
you
know
that
can
be
open
for
contributions.
B
Okay,
yeah
and
I
guess
the
community
would
be
also
interested
in
this
one
like
having
the
automation
in
a
when
using
react
to
so.
Okay.
D
I
also
have
a
random
question
I
was
looking
at.
I
was
so
I've
been
playing
around
with
the
web
components
with
the
web
plugins
and
it
seems
like
it
it.
The
build
like
the
distribution
package
is
pretty
big
like
it
compiles
like
into
like
a
one
mag
of
javascript.
D
Is
that
a
concern
at
this
point?
Like
do
you
from
like?
I
know
that
from
our
cust,
a
lot
of
our
customers
are
very
like
cognizant
about
the
size
of
their
javascript.
B
We
are
not
doing
this
so
so
yeah
for
for
those
reasons,
because
then
it
means
we
would
have
to
prepare
many
different
versions.
Sure
and
it
would
never
satisfies
everybody.
So
so
this
is
just
a
you
know:
typescript
without
any
obfuscation,
minimification
and
so
on.
So
I
would
say:
use
a
webpack
as
the
most
popular
one
and
then
minify
this
as
much
as
possible.
So
I
guess
then
it
should
be
much
smaller.
D
Yeah,
I
mean
that's
what
I
did.
I
did
use
webpack
with
minification
and
it
did
end
up
just
very
basic
like
one
script
and
it
was
like
one
mic,
but
I'll
double
check
why
it
was
so
big.
Oh
yeah
I'll,
try
to
see
why
it
was.
B
B
We
do
sorry,
I
think
it
would
be
interested
if
you
have
something
that
you
did
maybe
just
post
an
issue,
so
it
will
be
easier
to
to
see
what
you
did.
What
your
webpack
looks
like
and
I
can
give
it
a
try
and
see.
Okay,
there
is
anything
for
improvement
or
not.
Okay,.
C
Yeah,
I
was
going
to
kind
of
say
the
same
thing,
that
this
is
something
that
that
people
ask
from
time
to
time
so
like
having
having
some
documentation
on
it,
or
at
least
like
documenting
your
experience
on
it,
so
that
we
kind
of
have
have
an
idea
where
things
stand
and
maybe
where's
where
we
can
make
improvements
or
what
the
best
practices
around
here
would
would
be.
Super
helpful,
okay,.