►
From YouTube: Node.js Tooling Group Meeting
Description
C
D
C
All
right
so
cool,
so
we
got
the
the
agenda
here.
So
this,
if
you're
not
aware
so
the
way
the
agenda
works
is
essentially
it's
automatically
generated
from
github
issues
and
get
of
issues.
If
they
have
tooling
agenda
label,
they
will
get
added
to
the
agenda
and
Michael
Dawson
has
a
script,
looks
at
the
calendar
and
auto
generates
these
meetings
and
these
Google
Docs
for
us
and
blah
blah
blah,
and
so
that's
where
our
agenda
comes
from.
C
So
the
first
thing
on
the
agenda
would
be
tracking
hot
module
reloading
for
ESM
in
core
and
so
after
Montreal.
We,
let's
see
in
that
Montreal
meeting.
We
talked
about
it
with
this
guy
and
and
some
others,
and
it
seems
like
a
thing
that
really
should
happen,
but
there
needs
to
be
a
proposal.
Somebody
needs
to
do
the
work.
I
don't
know
if
we
can
rely
on
anybody
other
than
us
to
do
the
work
at
this
point.
So.
C
Yes,
in
fact,
it's
it's,
it's
not
in
aspect
you're
not
supposed
to
be
able
to,
but
that's
unfortunate,
because
it's
it
just
essentially
disables
a
lot
of
tooling,
including
things
like
reloading
files
and
like
a
watch
mode,
maybe
or
mocking,
especially
like
module
level.
My
essentially
kills
that
and
so
tools
need
this.
It's
just
a
matter
of
who's.
Gonna
who's
gonna
have
the
time
to
do
it.
I
don't
know
if
anybody
else
here
is,
is
particularly
interested
in
working
on
this
one.
Anyone.
Anyone.
A
Might
be
easiest
as
if
someone
has
like
a
pressing
work
need
for
this,
and
we
could
enable
them
right,
like
I'd,
be
curious
to
see
if
anyone,
if
this
is
kind
of
causing
day-to-day
problems
with
anyone,
not
their
job
and
looking,
maybe
carve
out
some
time
even
out
of
their
work.
Do
it
I
mean
this
is
important
enough
that
it
feels
like
it
should
be
affecting
some
companies
yeah.
C
B
C
E
F
C
A
C
B
As
far
as
tooling
goes
I'm
not
sure
if,
if
this
is
something
that
could
be
kind
of
pushed
in
the
webdriver
direction,
because
I
could
see
this
sort
of
functionality
actually
being
useful
in
the
browser
and
that
specific
way
you
know-
because
basically
webdriver
is
not
something
that
is
on
the
open
web.
So
there
are
cases
where
they
might
also
need
to
escape
the
normal
restrictions.
C
Yeah
I
mean
it
would
seem
like
if
you're
trying
to
do.
How
would
that
work?
How
would
you
like
hot
reload,
a
module
in
the
browser
I
mean
you'd,
have
to
have
some
hack
around
it
with,
like
you
need
like
a
unique
query
string
every
time
and
always
like
cash
busting
stuff
anyway,
and
and
certainly
that
is
a
like
workaround
I
think
maybe
maybe
not
I
haven't
I
haven't
thought
about
it
too
hard.
It
just
seemed
gross.
C
So
what
I
was
thinking
of
is,
if,
like
whatever
tool,
is
trying
to
do
this
actually
loads
these
modules
and
because
it's
like
a
URL
right,
then
you
give
it
like
a
query:
string,
unique
query,
string
at
the
end
and
change
that,
every
time
the
file
changes
or
something,
then
you
can
pull
it
off,
except
that's
a
memory
leak,
so
you
have
to
be
able
to
delete.
I
mean
it's
just
it's
kind
of
a,
not
I.
Guess
it's
really
not
negotiable.
So
anyhow,
I.
A
C
Maybe
you
know,
but
I
guess
you
know,
I
think
it's
I
think
there's
agreement
that
it's
something
that's
needed,
so
I'm
not
too
worried
about
it.
As
far
as
you
know,
we
have.
We
need
to
do
something.
I
think
the
whatever
the
implementation
looks
like
may
be
contentious,
but
it's
it's
definitely
a
thing
that
needs
to
happen
and
I
think
we
can
get
you
know.
So
you
know
support
from
us
of
course,
and
then
and
then
others
you
know
in
the
project.
C
Other
collaborators
other
TSC,
you
know
maybe
a
TC,
a
member
to
that
that
says
it's
important
I
mean
I.
Think
we
lack
here
right
now.
It's
just
like
a
fire
under
our
butts
to
get
going
on
it,
but
it
is
what
it
is
anyway.
So
meeting
at
the
open,
JSF
summit
is
on
Julia
agenda.
I,
don't
think
that's
correct!
I
think
that
was
unless
this
is
like
a
recap.
Should
I
recap
for
people
who
weren't
there.
Do
you
guys
want
that
I.
B
C
C
C
C
Is
it
the
20%
or
I
would
say
much
less
than
20%
who
our
library
authors
and
we
want
to
give
them
something
cool
to
build
on,
or
do
we
cater
to
the
to
the
masses
who
are
like
the
the
people,
learning
node
the
people
just
using
stuff
and
want
to
bang
something
out
and
I?
Think
the
I
don't
know
if
I
could
call
it
consensus,
but
I
think
there
was
kind
of
of
a
general
feeling
that
we
wanted
to
optimize.
C
C
He
says
you
know,
there's
many
things
that
don't
have
this
nice
argument
and
they're
fine.
You
know
the
fine
without
it
so
I
mean.
Okay,
but
it's
it
sounds
like
generally,
we
wanna
you
want
to
focus
on.
What's
something
we
can
build
for
people
to
actually
use
and
and
and
kind
of
go
down
that
road.
How
do
we
feel
about
that.
A
I,
have
this
on
my
mind
even
this
week,
because
I
have
up
here
who's,
you
know
making
the
switch
to
JavaScript
recently
and
they're,
just
updating
all
of
our
samples,
which
comes
up
a
lot
in
my
because
whitey
manages
like
80
libraries
and
like
hundreds
and
hundreds
of
samples,
and
most
of
them
are
command
line,
applications
and
I.
Don't
it
was
pretty
confusing
that
the
art
v
slice
I
mean
yeah,
that's
what
a
lot
of
languages
have
is
API,
but
it's
confusing,
especially
the
folks
who
are
new
to
programming
in
general,
so
I
don't
know.
A
B
B
C
A
Sorry
not
cry
sorry:
Chris
I
was
personally
I,
don't
think
we
should
implement
types,
I
think
that
would
probably
be
the
layer
above
where
like.
If
the
goal
is
that
this
could
be
something
that
minima
story
yards
or
Commander
or
now
use
instead
of
processed
Arg
V
like
I,
think
maybe
the
typing
would
be
added
a
layer
above
that
would
be
my
gut
just
because
there's
a
lot
of
contention
around
typing
like
when
does
it
become
an
array?
When
does
it
become
a
you
know?
A
My
number
and
we've
actually
fixed
a
surprising
number
of
bugs
and
yards
related
to
imply
guessing
typing,
because
people
will
put
a
UID
in
that's
above
JavaScript's
maximum
number
size
and
it
gets
truncated
because
it
tries
to
think
it
thinks
it's
a
number
and
then
turns
it
into
a
number.
That's
been
truncated.
So,
like
you
know
the
Devils
in
the
details,
you
probably
don't
want
to
be
doing
that
to
people.
It
should
be
a
big
int
at
that
point,
that's
being
pretty,
but
that's
being
pretty
starting
a
complicated
yeah.
C
C
Okay,
yeah
I,
like
this
I,
like
you
know,
I
mean
it
is
gonna.
Take
somebody
just
coming
up
with
a
basic
specification
for
for
this
again
right
now,
I'm
trying
like
at
work
and
basically
trying
to
decide
what
I'm
gonna
do
with
myself
for
the
rest
of
the
year,
and
you
know
it
may
be
something
like
this.
It
may
not
be,
and
so
I
don't
know
if
I
have
time
to
do
it.
I
will
know
more
in
a
couple
weeks,
but
you
know
so
I
feel.
E
Maybe
yes,
a
refresher
I
see
there's
matin
and
Bryan
that
were
not
here,
but
I
did
like
to
take
said
it.
One
is
the
most
simplistic
thing
we
could
possibly
do,
which
is
just
get
rid
of
those
likes
to
who
argues
like
schools.
You
know
just
having
a
proper
name
for
that
and
the
second
one
that
one
I
did
before.
That
was
more
sort
of
a
heightened,
inspired
API
to
just
do
the
very
basic
like
believing
the
parametres
that
yeah.
Maybe
let
me
paste
them
to
the
chats
on
that
particular.
C
E
I
sent
it
by
mistake,
but
my
idea
was
to
open
the
PR
I
guess
my
own
fork,
so
that
people
can
comment
on
it
like
prior
to
a
an
actual,
no
no
requests.
So
yeah
there's
actually
comments
from
Isaac
from
Corey
yeah
Corey
actually
wanted
to
expand
a
little
bit.
Give
it
a
little
bit
of
room
for
expanding
it
later,
which
I
think
is
a
good
idea.
So
yeah
like
maybe
continue
the
conversation
in
that
or
request
or
just.
B
A
Yeah
I,
don't
know
I
kind
of
my
opinion
on
that.
Pr
was
seemed
like
a
good
idea
in
conversation,
but
I
would
kind
of
want
the
slightly
more
complete
API
we've
been
talking
about.
I
think
it
would
add,
more
value.
I
was
kind
of
worried
and
I
think
we
could
get
like
from
the
feedback
we
were
getting
in.
Our
meetings
that
note
interactive,
I,
don't
I
think
we
could
actually
make
some
progress
on
an
actual
API,
so
that
was.
C
My
gut
yeah
me
personally,
I
would
I
guess
I'd
rather
go
with
a
more
full-featured
thing,
and
because
this
to
me
it
felt
like
it's
kind
of
a
stopgap
and
it's
just
something
that
might
be
a
lot
easier
to
get
in
and
get
merged.
But
if
we
can
go
in
and
provide
a
more
complete,
API
I
think
that's
probably
I
would
be
fine
doing
that
instead
of
this,
not
not
I,
don't
think
it
needs
to
be
in
addition
to
this,
and
what
do
you
think
right.
E
I
also
send
a
comment
with
the
the
other
pull
request,
the
one
that
just
outlines
the
dock
for
fight
on
his
part
kind
of
module,
but
yeah
this
yeah
yeah
I,
think
we
need
more
more
discussions.
I,
don't
know
yeah
if
people
can
just
like
discussing
more
in
the
PRS,
but
also
define
of
the
reaction.
Yeah.
C
So,
let's
see,
oh
I
was
going
over
the
stuff.
Okay,
the
next
thing
we
discussed
there
at
Montreux
self-contained
binaries.
So
the
summary
is
there
should
be
there
be
a
blessed
way
to
install
it
run
a
CLI
to
written
a
note
without
needing
to
install
node
separately.
The
base
guy
had
been
said,
basic
idea
for
command-line
tools.
It's
nice
to
be
able,
distribute
an
executive,
all
tool
that
a
consumer
doesn't
need
to
know
about.
Nodejs
doesn't
need
install
node,
yes,
and
on
I
mentioned
that
you
could
write.
C
C
C
F
Yeah
one
of
the
one
of
the
former
main
taters
of
create
react.
App
works
its
next
chest.
No
I
did
actually
I
asked
him
like
a
month
ago.
If
he
wanted
to.
He
was
interested
in
joining
these
meetings
and
he
did
express
some
interest,
but
I
guess
I
should
send
them
the
actual
invite
for
next
time.
So
I'll
try
and
get
him
here
next
time.
C
B
C
A
My
point
of
view
at
Google,
like
you,
know,
Jess's
at
one
of
our
official
languages,
so
it
would
make
it
easier
for
me
to
distribute
tooling
to
teams
if
they
didn't
even
have
to
think
about.
Node.Js
like
this
is
just
a
magic
thing.
You
type
you
don't
have
to
worry
about,
have
to
worry
about.
What's
happening.
E
C
F
A
Okay,
I
think
I
would
make
it
easier
for
certain
Linux
distributions
to
or
they
D
where
they
need
to.
You
know
they
know
they're.
You
know
to
ship
that
you
get
the
whole
thing.
You
don't
have
to
pull
in
seventy
different
packages
to
ship
the
distribution
which
I
think
it's
how
it
maybe
Debian
a
ship
snowed
package.
I.
Think
when
it's
one
of
the
Linux
distros
like
pulls
in
literally
every
dependency
whenever
they
ship
a
node
module.
It's
kind
of
interesting
but.
C
B
A
C
F
C
F
C
F
C
F
B
So
one
question
I
have
for
this:
how
would
how
would
this
deal
with
situations
where,
let's
say
a
module
loads,
something
that's
not
JavaScript
like,
for
example,
NYC
the
HTML
report?
When
you
run
the
report,
it
copies,
there's
some
asset
files
that
get
copied
into
the
destination.
C
A
Think
we'd
have
to
have
I
mean
this
would
be
something
we'd
have
to
put
in
a
design,
but
I
would
guess
that
it
would
resolve
to
a
node
modules.
Folder
that
was
actually
built
into
the
binary,
potentially,
maybe
would
be
like.
Maybe
it
takes
it
I
don't
know.
Yeah
you'd
also
need
like
filesystem
shimming
right,
like
you'd,
have
to
shim
the
FS
module.
C
C
C
B
B
F
C
A
B
C
A
A
C
C
A
Basically,
there's
just
no
public
interface
for
the
source,
apps
that
we,
so
we
have
source
maps
for
two
node
GS
right
now.
You
run
it
with
a
flag,
and
that
means
that
if
you
have
source
maps
embedded
in
the
code,
that's
loaded
by
the
module
loader
will
cache
them
and
then,
if
a
stack
trace
occurs,
it
will
try
to
give
you
the
original
source
location,
as
well
as
the
trans
filed
source
location.
A
But
this
broke
some
community
tooling,
because
we're
overriding
prepare
stack
trace
which
is
used
by
some
parts
of
Express
and
it's
used
by
some
other
things
like
source
map
support,
which
is
the
historic
way
people
have
done
stuff
like
pretty
stack
traces.
So
I
am
proposing
a
I'm
working
on
a
public
API
for
source
maps.
I
actually
have
a
PR,
that's
approved
and
I
just
need
to
rebase,
but
it
basically
just
puts
prepare
stack
trace
back
to
working
the
way
it
works
for
folks
who
overrode
prepare
stack
trace,
so
Express
will
continue
working
source
map.
A
Support
will
continue
working
without
losing
support,
but
there
is
now
a
public
API
so
that
someone
upstream
like
source
map,
support
or
or
the
one
that
broke
Express
could
just
start
looking
at
our
own
cache
of
source
maps
and
actually
interact
with
them
their
selves.
So
they
can
see
if
we
have
this
source
map
module
available.
If
we
do
have
it
available,
they
can
actually
pull
in
our
own
source
map
information
and
start
to
use
it.
So.
A
F
A
Well,
we
we
basically
changed
the
guarantee
of
the
preparer
stacktrace
method
and
upon
further
investigation,
v8
documents.
That
is,
if
it's
a
very
public
API,
so
I
think
we've
just
made
a
bad
decision
than
that
implementation.
So
we're
putting
it
back
the
way
it
was
v8
documents
at
the
way.
It's
it's
you
it's
working
so
should
that
will
fix
Express
and
then
the
next
step
is
I
really
would
love
Express
to
use
the
source
map
support?
We
have
other
really
cool
use
case.
A
I
was
thinking
of
was
puppeteer
which
lets
you
run
code
in
the
browser,
but
it
uses
node
for
instrumentation
right.
It
uses
node
to
kind
of
orchestrate
a
conversation
with
the
browser.
You
could
totally
take
source
maps
that
are
popping
up
in
that
browser
session
and
load
them
into
nodes.
Own
source
map
handling
I
was
thinking
yeah.
Another
really
neat
use
case,
so
I
think
it's
cool
I'm
excited
to
see
how
people
use
it
so.
A
In
the
puppeteer
cases,
I'm
hoping
to
expose
the
source
map
class
so
that
it's
someone
even
like
the
puppeteer
use
case,
could
take
those
source
maps
and
in
node.js
itself,
load
them
into
a
class
that
they
can
then
interact
with
them
and
consume
them
in
the
exact
same
way
that
they're,
interacting
and
consuming
source
maps
that
have
been
found
in
the
module
loader.
So
it
kind
of
just
makes
it
a
consistent
API
surface.
A
A
B
A
F
A
B
Ben,
did
you
see
the
comment
that
I
I'm
not
sure
if
I
commented
on
the
PR
but
as
far
as
Istanbul
goes
I
think
for
it
to
be
able
to
use
that,
then
we
would
need
a
way
to
essentially
perform
an
index
of
on
the
mappings.
So
in
other
words,
instead
of
saying
give
me
the
location
of
you
know
say
we
have,
you
know
generated
line
one
column
1000
tell
me
what
the
original
source
location
was.
B
A
How
do
you
feel
that
that
being
in
a
follow-up,
PR
and
I
I
said
because
the
I
noticed
that
so
we're
using
v8
source
map
implementation?
Ijoy
pointed
out
to
me
that
that's
actually
kind
of
out
of
date
and
chromium's
implementation,
which
v8
got
theirs
from
it's
a
little
newer,
has
a
few
more
features
and
bug
fixes,
but,
most
importantly,
it
actually
sorts
the
source
Maps
post-talk,
which
I
think
is
specifically
for
your
use
case
that
there's
no
guarantee
of
sorting
order,
but
people
in
the
community
started
assuming
a
sorting
order.
A
So
now
it's
built
into
the
tooling.
So
if
we
were
going
to
do
that
approach
where
the
index
would
actually
work,
I
think
we
need
to
pull
in
the
chromium
source
map
class
first
same
API
surface,
just
with
a
few
bug
fixes
basically,
and
then
we
could.
You
could
probably
safely
do
that
index
based
approach
because
we
actually
are
sorting
everything
so
I
think
it's
kind
of
a
blessed
use
case
at
that
point.
I.
B
Definitely
agree
with
what
you
just
suggested,
not
just
for
the
bug
fix,
but
also
because
your
PR
has
already
approved
and
adding
to
the
API
surface
will
basically
create
more
questions
and
potentially
slow
down.
Your
initial
I
want
what
you
have
to
get
put
in
now,
and
then
we
can
iterate
I
think
that's
the
better
way
to
go.
Yeah.
A
I
could
imagine
us
like
quickly
doing
it
in
to
follow-on
PR
as
one
we
pull
in
the
newer
version
of
the
class
too.
We
add
the
way
to
get
an
index
out
for
Istanbul,
so
I
think
we
could
get
that
done
in
a
couple
weeks.
Hopefully
I'm
excited,
you
know,
61%
of
people
use
typescript
now
so
I'm
like
this
is
I
think
this
is
the
way.
No,
it's
gonna
stay
relevant.
My
head
to
a
certain
degree,
yeah.
C
B
B
A
B
A
B
A
B
A
So
I
don't
know
that
much
about
this
part
of
the
system
either
and
I
think
the
subject
matter.
Expert
who's
helped
make
sure
that
stuff
works
properly
is
Joey,
so
one
other
way
to
move
start
moving
things
for
it
might
be
just
ask
Joey
for
advice
as
well
as
make
maybe
Sam
I,
think
I
think
Joey
knows
best
where
to
where
we
might
be
able
to
implement
this
behavior
Joey
or
Adil
acts.
I,
don't
know,
I
think
like
even
like
a
PR
that
doesn't
work
perfectly.
A
B
C
A
C
C
A
C
B
A
B
A
That
make
sense
I've
to
actually
run.
Maybe
do
you
know
what
might
be
worth
doing
is
having
like
an
issue
that
summarizes
how
all
these
features
relate
to
each
other,
because
a
bunch
of
them,
a
bunch
of
them
have
to
do,
is
like
exit
time
and
how
stuff
has
passed
either.
Bring
up
or
tear
down
related
to
NYC
might
be
neat
for
someone
to
see
the
whole
picture,
and
then
we
can
talk
about
that
in
the
next
meeting.
Potentially
how
a
summer
is
it
I'm
probably
get
yelled
at
for
being
in
the
circle.