►
From YouTube: Node.js Tooling Group Meeting
Description
A
A
See
I
did
sorry.
I
I
tend
to
like
cram
everything
in
right
before
the
meeting.
So
I
took
a
look
at
a
closer
look
at
Ian's,
pull
request
and
I
didn't
have
too
much
to
say
about
I
mean
look
good
to
me,
Isaac
just
popped
in
and
says
we
should
not
create
a
new
module
cut.
It
called
Shu
till
we
should
put
all
this
stuff
in
FS
I
see
seed
Raphael
there
too,
because
I
feel
like
that
was
probably
your
idea
so
to
to
kind
of
explain
the
reasoning
behind
it
it.
B
B
Like
unless
you're
pretty
deeply
embedded
in
a
Python
community,
that's
kind
of
a
terrible
name,
but
it
doesn't
tell
me
a
thing
about
like
I:
don't
it
doesn't
make
me
think
file
system
functions,
so
it's
like
I
feel,
like
my
vote,
would
be
put
in
another
module,
but
maybe
not
Shu
till
this,
because
it's
feels
like
we're
taking
a
name.
That's
not
that
great
from
another
community
that
you
have
to
be
part
of
to
know.
That's
my
two
cents,
I'm
gonna
block
on
that
either.
D
So
I
would
say:
yeah
I'm,
not
super
married
to
the
actual
name.
I
just
I
always
prefer
a
prior
art.
If
anybody
has
I
think
for
Windows,
there
is
for
like
there's
the
windows
grating
host
there.
It's
called
shell,
those
kinds
of
utilities,
so
maybe
she'll
utilities
instead
of
SH
appear
like
being
over
both
but
I,
think
calling
it
shell
utilities,
as
is
pretty
close
to
what
our
intentions
are
and
and
I'll,
go
into
detail,
and
you
don't
good
I,
just.
B
Wonder
I
feel:
does
it
does
it
kind
of
pigeonhole
us
a
bit
that
that
like
are?
They
is
an
extension
to
available
shell
commands
or
is
it
you
know,
extension
to
the
file
system
API
like
I,
just
wonder,
is
it
a
shell
or
is
that
a
file
system
API,
like
you
know,
she'll
just
feels
like
a
weirdly
overloaded
word
to
me.
D
D
D
B
A
So
yeah
I
mean
the
way
I
understand
it
anyway,
is,
if
you
didn't
know
how
these
things
work
like
a
recursive,
make
der
you'd
say:
oh
well,
that's
a
filesystem
thing,
but
it's
not
really
it's
it's!
It's
a
loop
over
a
filesystem
thing.
It's
as
like
one
higher
level
up
of
that
abstraction,
but
I
mean
I
can
see
how
people
would
say.
Well,
oh
that
should
be
in
FS,
because
it's
it's
working
with
the
file
system
right
so
I
mean
I,
get
that
but
I
like
I
like
the
calling
it.
A
This
is
what
you
need
when
you,
when
you're
writing
a
shell
script
and
node.
So
what
what
then?
What's?
What's
a
good
way
to
say
you
know,
I
mean
is,
is
is
do
we
not
want
to
put
this,
considering
that
people
makes
may
expect
it
to
be
in
FS,
which
is
not
I,
don't
think,
that's
unreasonable!
What's
the
what's
the
rationale
for
not
putting
it
there
just
to
that,
it's
crowded
or.
C
I
mean
I,
think
I,
think
sort
of
to
your
point
like
it's
not
necessarily
a
FS
utility.
It's
something
kind
of
on
top
of
FS
I
think
that's
probably
the
best
argument
that
I
can
think
of
for
not
putting
it
in
there.
I
think
one
thing,
that's
gonna
be
a
little
confusing
like
like
we
just
talked
about
a
whole
bunch
of
other
things
that
are
shell
related
that
could
be
in
that
module.
C
But
the
fact
that
were
this
is
going
to
be
submitted
like
on
its
own
as
the
only
function
in
that
module,
so
there
that
we
don't
there
that
context,
isn't
really
there.
So
I
don't
know
if
maybe
that
just
needs
to
be
kind
of
explained
a
little
bit
in
the
PR.
What's
sort
of
like
the
future
intentions
are
here.
B
Yeah
I
guess
it
may
be
one
way
to
look
at.
It
is
well
I
like
the
way
of
looking
at
it,
like
the
the
other
confusion
we're
gonna
have
is,
if
we
start
to
lay
in
some
of
our
improvements
to
child
process
management,
so
that
it's
less
coupled
to
you
know
so,
there's
a
cleaner
abstraction
like
people
are
gonna,
be
like.
Why
isn't
that
in
compiled
process?
So
it'll
be
like
you
know
why,
arts?
Why
isn't
rim
ref
in
FS?
B
B
D
B
B
B
A
B
An
alias
help
them
future,
detect
it
as
well.
If
you
remember
the
argument
way
back
in
the
day,
so,
like
maybe
that's
the
perfect,
maybe
then
we
can
move
two
things
into
Shu
till
right.
The
way
we
have
a
McGirt
which
lets
people
feature
detect
McGirt,
which
is
just
an
alias
to
victor
recursive,
and
then
we
have
the
work
being
done
on
Rimrock
right,
because
then
there's
two
things
and
not
just
one
which
is
great
and.
D
I
think
that
any
you
know
in
my
point
of
view
in
it
anyway.
These
two
should
be
like
two
cars
and
what
we
have
our
and
like
for
reference
for
context.
We
have
our
conversations
and
the
meeting
notes
and
we
would
just
need
to
like
defragment
the
knowledge
back
into
the
into
the
pr
threat
and
and
comment
back
and
say
we
gave
this
some
thought
this.
What
this
was
our
reasoning.
D
If
you
strongly
disagree,
then
you
know:
let's,
let's
escalate
it
up
to
a
vote.
I
like
I,
like
you
know
when,
when
when
things
get
into
this
like
kind
of
white
Chevy
with
the
personal
preference
area,
bring
it
up
to
a
vote,
see
what
the?
If
you
can't
get
consensus,
see
what
the
majority
and
then
just.
C
Yeah,
we're
probably
not
going
to
get
it
right,
initially,
I
think
as
long
as
we're
sort
of
an
agreement
that
it
should
be
in
a
new
module.
I
think
you
know
we
can
call
that
whatever
Shu
tail
or
she'll
and
submit
the
PR
with
that,
and
then
people
will
have
opinions
about
what
the
actual
name
should
be.
Yeah.
B
A
C
Yeah
I
have
I,
have
not
had
a
chance
to
do
any
work
on
it
since
the
last
meeting,
but
I
am
really
hoping
that
I'll
have
some
time
either
this
week
or
weekend
to
get
it
submitted.
I
think
I
just
need
to
make
sure
the
linter
is
passing
and
then
I
also
wanted
to
there's
a
number
of
like
existing
tests
in
the
rim
raft
package.
I
wanted
to
try
to
like
port
over
as
many
of
those
as
possible
to
cover
you
know
all
of
those
cases.
That's
really
the
only
like
outstanding
work.
C
A
C
B
C
C
A
It's
kind
of
like
a
meta
question
about
this,
so
is
there
a
precedent
for
for
pulling
nearly
verbatim
a
user
land
module
into
node
core
yeah
yeah?
We
had
with
node
expect
or.
D
D
B
D
B
Was
gonna
say
my
only
concern
it's
not
like
Isaac
said
he's
totally
cool,
so
we'd
have
to
worry
about
offending
the
maintainer,
but
just
from
a
legal
Providence
point
of
view,
I
might
ask
a
lawyer
friend
about
do.
We
have
to
slap
a
license
on
everything
we
probably
do
so,
even
if
Isaac
is
saying
that
we
don't,
he
doesn't
care
like
from
a
legal
standpoint.
You
actually
would
need
all
the
contributors
ever
to
agree
to
a
license.
Change,
yeah.
C
I
think
that
I
think
the
license
will
need
to
be
included
where
or
what
that
process
is
I
just
at
the
top
of
each
file,
but
I'll
confirm
I'm,
not
a
lawyer,
so
I
don't
say
the
problem
is
that
file
is
going
to
contain
a
bunch
of
other
stuff
as
well,
but
yeah
I,
don't
know.
If
there's
like
a
list
of
these
licenses
somewhere.
My.
C
D
D
A
Think
is
just
this
like
crazy
maze
of
of
weird,
you
know,
one-off
edge
cases
and
bugs
that
are
that
have
to
do
particular
systems
in
anybody
stepping
into
this
code,
which
would
now
be
a
note
or
it's
gonna,
look
at
it
and
be
like
well.
Why
the
hell
is
that
there
and
nobody's
gonna
be
able
to
tell
them
anything.
D
D
D
A
You
know.
Certainly
we
can
ask
questions
of
him,
but
it's
going
to
be
kind
of
more
work
to
track
down
why
this
works
in
this
way.
You
know
why
that
one
comment
says
life
is
pain
or
whatever
like
what?
What
what
is
unique
to
the
history
here,
where,
where
did
that
come
from?
And
why
and
who
reported
it
context?
Is
it
still
valid
so
I
would
just
I
would
just
say
that
no
there's
automation.
D
B
Don't
yeah
I
was
gonna
echo.
What
Rafael
is
saying
and
just
say
like:
let's
make
sure
that
we
have
links
in
the
what
is
the
ported
code,
so
folks
can
go
back
and
look
at
the
rim,
ref
history,
but
I
think
it
would
create
a
lot
of
work
to
try
to
bring
in
the
whole
history
partially.
Just
because
it's
gonna
be
squashed
once
the
merge
has
landed
anyways,
just
by
virtue
of
how
commits
land
on
node.
E
The
solution
in
other
languages
has
been
dual
life
modules
where
they
exist
both
on
the
in
the
registry
and
in
core
and
core
updates.
It's
essentially
the
way
NPM
is
distributed
within
with
node
I,
although
I
think
the
module
resolution
algorithm
makes
it
impossible
for
us
to
do
this
in
node,
unfortunately,
because
it
will
load
the
internal
version
in
preference
over
the
file
system
version.
E
You
can
NPM
yeah
it's
the
way
than
the
majority
of
Perl
core
is
brought
in
as
well
in
in
Perl.
That's
most
of
their
modules
are
actually
live
on
the
sea
pan
and
you
can
install
them
separately
and
get
updates
sooner
than
core
would
update.
But
if
you
don't
you
by
default,
get
the
one
that
comes
with
core
the.
C
It
says,
like
this
code
was
ported
from
rim
ref
and
here's
a
link
to
like
the
github
page,
and
you
can
view
the
history
there
I
think
that's
I
mean
definitely
something
we
should
do
yeah
in
terms
of
like
the
modules
sort
of
like
coexisting
like
I'm,
not
sure
I
think,
like
rim
ref
will
have
to
continue
to
exist,
and
this
we
were
not
backporting
this
and,
like
maybe
eventually
room
ref
just
becomes
like
it
just
checks
for
the
presence
of
this
function
and
uses
it.
If
it's
there
otherwise
uses
its
own
implementation.
C
D
B
B
A
A
A
Club
I
I,
don't
know
if
I
want
to
make
it
like
I,
don't
I
mean
I,
don't
know
if
I
want
to
make
it
like
an
official
thing,
because
it
might
be
difficult
to
set
up
the
video
conferencing
or
just
like
a
pain
in
the
butt.
So
maybe
just
it
should
be
more
of
an
informal.
Let's
not
really
decide
too
hard
on
anything,
but
it
just
kinda
depends.
So
if
you
know
I
don't
know,
I
haven't
looked
to
see
if
the
the
actual
schedule
has
been
released.
D
So
just
two
comments:
for
the
sake
of
inclusivity
exclusivity:
some
people
are
not
able
to
attend
various
reasons.
Soap,
like
the
mandate.
Let's
say
the
collaborator
summit
is
to
discuss
our
fast-track
things
and
then
you
know,
look
them
back
into
the
official
canonic
channels
which
are
get
up
and
and
these
meetings,
so
if
anything
interesting
happens,
try
to
document
it.
So
you
can
know,
put
it
in
writing,
so
everybody
could
read
and
and
follow
up
and
the
second
thing.
C
That's
something
I'd
like
if
I
know
more
about
that,
maybe
not
for
the
collaborate
or
something
because
it's
pretty
coming
up
there.
Pretty
quick,
but
we're
talking
about
a
note
interactive,
for
example,
because
I'm
kind
of
like
independent,
like
my
company,
doesn't
sponsor
me
to
do
these
things.
So
how
can.
D
A
Alrighty
and
so
argument
parsing
was
on
the
agenda.
Nothing's
really
happened
there
on
that
front.
I
guess
we're
still
just
waiting
for
whoever
that's
going
to
be
to
send
some
sort
of
proof
of
concept
through
and
yeah
I
totally
understand.
If
nobody
has
time
to
do
that,
because
I
don't
have
time
to
do
that
and
but
when
and
if
anybody
does,
that
would
be
cool.
A
There
is
a
little
bit
of
discussion
going
on
in
there
if
you,
if
you
want
to
participate
in
in
that,
let
me
know
if
you're
not
already,
but
it's
just
like
you
know
right
now.
It's
just
in
a
private
repo
under
my
name,
I
guess
I
could
make
it
public
I
can't
remember
why
we
made
it
private
or
maybe
I,
did
that
unilaterally.
I,
don't
remember,
but
there's
like
a
little
repo
and
in
that
repo
is
absolutely
nothing
except
an
issue
that
says
hey.
A
A
B
B
B
The
whole
process
around
getting
v8
merged
back
into
node
is
just
like
it
takes
like
12
weeks
and,
and
what
will
happen
is
like
some
really
great
new
feature.
Well,
land
in
you
know
v8
and
they're.
Just
the
process
is
pretty
janky
for
actually
getting
it
through,
so
I,
probably
outside
of
that
tooling
group.
But
you
know
for
if
we're
continuing
to
work
upstream
on
things
like
v8
and
like
live
UV
and
whatnot
I
could
kind
of
cool
if
we
automated
automated
that
flow
a
little
bit
better,
but
probably
beyond
our
scope.
D
D
The
plus
and
minuses
of
C++
is
that
usually,
if
it
compiles
then
you're
like
ninety
percent
into
correctness,
but
but
I'll
give
it
a
really
quick
overview
of
how
we
create
current,
as
it
has
managers
at
any
sir.
Any
point
in
time:
three
branches,
there's
the
official
GA
general
availability
version,
that's
current
and
day
and
date,
and
this
goes
for
for
chromium
as
well
and
every
12
weeks
they
cut
the
new
branch
and
move
everything
downstream.
D
All
these
versions
are
considered
major
node
tries
to
have
at
least
so.
We
have
general
availability
web
beta
and
we
have
devs
and
there's
also
the
like
tinnitus,
that
the
tip
of
the
of
the
git
repo
no
tries
to
be
up-to-date
with
with
the
general
availability
of
a
v8
and
chromium,
but
that
is
via
like
that
latest
gate
goes
into
nodes
master.
D
D
B
Well,
I
guess
you
know,
that's
the
only
thing
I've
been
working
on
I
was
just
gonna
make
move
you
could
maybe
we
could
take
it
offline,
but
getting
some
help
that
figure
out
how
to
cherry-pick
that
stuff
would
be
nice
for
six
months.
But
the
frustrating
thing
with
test
coverage
has
been:
it's
super
cool
and
it's
nice
that
were
able
to
use
v8
like
we
are
able
to
use,
be
inspector
protocol,
but
the
six-month
leg
can
be
kind
of
painful
when
you
have
these
kind
of
deep-seated
issues
right.
D
D
D
D
D
D
B
It's
interesting,
so
we
manage
the
back
port
coverage.
The
v10
I
think
no
to
be
totally
back
yeah.
We
back
ported
the
bunch
of
patches
to
be
ten,
but
it
was
like
a
15
patch
merge
hell
basically,
and
it
feels
like
some
of
the
new
fixes
for
coverage.
You're
gonna
be
the
same
thing,
so
it's
just
a
hassle,
but
it
is
doable
like
you
can
get
it
in
within
a
couple
months.
You
can
get
it
in
within
a
few
weeks,
if
you're
going
to
do
the
footwork.
B
Starts
to
look
like
a
Frankenstein's
monster
like
yours,
but
the
v8
in
node,
like
months
into
being
like
when
you
say
you're
five
months
in
and
a
ton
of
patches
have
been
floated
with
some
manual
changes
to
land
them.
You
start
getting
this
thing
that
doesn't
might
look
that
much
like
any
real
release.
Ova
I
can
I've
definitely
seen
bugs
that
crop
up
in
nodes,
v8
that
don't
crop
up
in
the
mainline
v8
like
with
specifically
around
coverage,
because
you
know
I've
had
to
make
some
manual
changes
to
the
code
even
make
them
landable.
D
D
The
essentially,
the
and
I
think
that
that
happened
almost
with
all
Apaches
to
d8.
We
had
them
spent
some
time
in
the
v8
repo
getting
actual
v8
reviews
before
being
back
ported
I,
don't
remember
maybe
it
happened,
but
at
Donna
number,
like
a
case
of
something
that
was
patched
only
note
and
didn't
get
any
like
create
review
at
least
an
attempt
to
up
to
like
upstream
it
has
been
done
to
get
that
feedback.
So
that's
like
so
the
issue
here
is
this
developer
focused.
D
B
C
B
B
A
Ready
does
anybody
have
anything
they
want
to
bring
up,
got
any
ideas
you
want
to
kick
around
and
he
like
cool
stuff
that
you've
seen
on
the
CLI.
That
makes
you
excited
and
know
anything
like
that
anything
you
want
to
chat
about.
So
the
world's
an
issue
I
touched
on.
We.
D
Somebody
brought
up
an
issue
issue
and
in
the
no-drip
home,
asking
the
court
to
publish
a
corn
if
economy
is
and-
and
some
people
have
been
pushing
back
on
that
and
saying
like
there's
no
standard,
ASP
or
IR
for
JavaScript.
So
we
don't
want
to
make
a
corn
like
the
de
facto
standard
and
and
this
difference
between
the
VI
parsing,
which
will
consider
like
the
truth
and
a
conf
are
saying
this.
The
gap
between
those
two
will
be
surprising
to
developers,
etc.
B
D
D
D
The
JavaScript
engine,
the
crown's
node,
so
if
you're
a
node
I'd
like
to
see
the
the
same
parses,
that's
actually
gonna
invite
my
code
parts
my
code
and
if
the
VM
is
replaced
with
chakra,
jarred
script
or
SpiderMonkey,
then
then
have
that
do
the
same.
Like
the
same
VM,
that's
gonna
run
my
code,
I'd
like
it
to
parse
my
code,
but
anyway,
I
think,
as
we've
seen
many
times
with
with
p39
as
standard
come
to
come
to
be
based
on
push
from
the
ecosystem.
D
D
D
D
D
D
A
A
Yeah
well
almost
had
time
any
any
last-minute
stuff
anybody's
got
no
all
right.
Well,
thanks
for
hanging
out,
and
we
will
talk
again
in
three
weeks,
I
believe
that
is
after
the
collab
summit,
and
so,
if
anything
comes
out
of
the
club
summit
worth
mentioning
I'll
be
sure
to
report
it
back
somehow.
So
anyone
thank
you.