►
From YouTube: Node.js Tooling Group Meeting
Description
A
Alright,
it
looks
like
we
are
probably
live,
so
hi
welcome
to
this
user
group
meeting
for
the
two,
the
node
tooling
working
group
meeting.
A
A
A
B
Yeah
yeah
I
did
add
the
new
Shu
tail
module
and
then
I
just
to
start
I,
just
directly
ported
rim
ref
into
there
all
of
the
globbing
functionality
and
then
so
I
that
was
working
and
then
I've
started
working
on
just
cleaning
that
code
up
to
make
it
more
in
line
with
the
existing
node
libraries,
so
I've
removed
I
used
a
cert,
for
example,
to
check
that
prep
that
input
parameters
were
valid,
so
removed.
All
that,
and
now
it
throws
like
the
proper
like
invalid
argument,
type
exceptions
and
things
like
that.
B
B
Probably
it
probably
needs
like
additional
testing
I'll
look
at
the
the
existing
tests
in
rim
RAF
as
well,
and
see,
if
there's
any,
that
we
can
sort
of
move
over
to
make
sure
we're
covering
as
much
as
possible.
So
yeah
I
think
that's
that's
kind
of
where
that's
at.
If
anyone
has
I
just
created
a
PR
on
my
fork,
because
I
wasn't
ready
to
submit
it
to
like
node
proper,
yet
I
posted
a
link
to
the
PR
in
the
tooling
channel
and
slack
so
yeah.
B
A
A
B
Yeah
I
mean
I
would
definitely
welcome
some
help.
I'm
I'm
I
don't
have
a
ton
of
experience
working
directly
in
node,
so,
like
I
said
just
even
the
the
style
of
like
how
the
internal
libraries
are
written.
This
is
something
I
could
use
sort
of
some
help
with
yeah.
If
anyone
wants
to
to
work
on
it
with
me,
that
would
be
great.
Otherwise,
even
just
yes,
I'm,
like
some
feedback
would
be
helpful
and
I
can
I
can
just
work
through
myself.
It's
kind
of
yeah
up
to
you
guys
so.
C
C
There
might
be
issues
with
early
versus
late
initialization
of
stuff
if,
if
there
is
any,
but
we
have
tests
that
cover
essential
bits.
Okay,
so
I
think
that
most
like,
like
the
idea
of
the
core,
is
to
put
in
some
tools
in
place.
If
you
can
pass
the
lender
and
the
test
week,
you're
95
percent
there,
okay.
B
C
B
C
B
A
Right
yeah,
so
I'll
I
can
just
take
a
look
at
the
I
mean.
So
you
said
you.
Basically
you
took
rim
ref
and
essentially
what
copy
paste
and
then
and
then
rip
some
stuff
out
with
the
globs
more
or
less
yeah.
You
know:
okay,
I
I'm
wondering
if
there
needs
to
be
some
sort
of
copyright
notice
in
here
right.
B
Yeah,
it
depends
like
I
mean
at
one
point:
I
was
thinking,
I
would
just
like
rewrite
it
all,
but
there
is
definitely
some
stuff
in
there.
That
I
think
will
want
to
keep
there's
there's
some
specific
stuff
related
to
handling
permissions
in
Windows
and
also
handling
something
to
do
with
like
file
handles
not
being
closed
in
a
timely
manner
on
Windows,
so
I
think,
like
I,
mean
I
can't
even
really
test
that
stuff
locally,
so
I
think
like
those
sort
of
workarounds
that
we
should
probably
leave
in
there,
as
is.
A
Yeah,
it's
something
about
I'm
sure
somebody
knows
more
about
than
I
do
but
yeah
it's
like
something
is
not
not
a
synchronous
operation.
It's
like
when
you
remove
a
directory
or
something
like
that.
It's
it
happens
and
it
have
the
rim.
Ref
has
to
like
ping
to
make
sure
it's
actually
gone
or
something
no
I.
Remember
this.
D
A
B
A
Is
the
life
is
suffering
comment
yours,
or
is
that
that's
that's
directly.
E
C
E
C
C
B
C
C
D
C
A
All
right,
so
the
the
only
other
thing
was
the
the
art
parsing
stuff,
and
nobody
has
gotten
to
that.
As
of
yet
as
we're
all
busy
with
other
things,
I
was
I
was
really
thinking
hard
about
sitting
down
and
and
banging
something
out,
but
I
didn't
do
it,
but
I
thought
about
doing
it.
I
I
didn't
do
it,
though,
so
we
haven't
gotten
anywhere
on
that.
A
If
you
do
not
have
access
to
the
repo
and
want
to
contribute
just
let
me
know,
but
yeah
I
made
like
a
repository
that
we
can
use
and
discuss
this
stuff
right
now.
It's
private,
maybe
I,
should
just
make
it
public.
I,
don't
know
I,
don't
think
anybody's
gonna
pay
attention
to
it
anyway,
so
it
might
as
well
be
public
but
yeah.
So
I
had
just
come
like
opened
an
issue
and
described
this
as
kind
of
what
we
need
to
do
and
we're
just
kind
of
waiting
until
somebody
does
something
and
that's
how
things
go.
A
A
E
C
I
have
like
a
in
my
in
the
back
of
my
mind:
I
have
our
long
term
roadmap
and
I
want
to
make
it
polyglot
in
some
way.
I
might
find
a
way
to
compile
it
to
wasn't
or
something
I
want
to
make
interrupts
between
JavaScript
I
wanna
make
you
know,
chip
three
polygons
and
then
be
able
to
interact
with
JavaScript,
Python
and
other
stuff,
and
then
it's
a
it's
a
it's
a
disgusting,
a
veto,
there's
a
ton,
our
parsing
and
graphing
and
everything.
C
C
I
wanted
to
say,
happy,
I,
know
12
to
everybody.
We
got
on
the
tools
front.
If
anybody's
watching
we
managed
to
implement
a
ton
of
bootstrapping
optimizations
node
12
should
put
strapped
50
to
60%
faster
than
node
11.
So
you
know,
quick
tools
will
benefit
from
that
immensely
and
tools
that
for
car
will
benefit
from
that.
A
huge
I
think
it's
more
like
75%
on
Windows
it
up.
Trapping
and
soon-to-come
are
snapshots
and.
C
Initially,
we
kind
of
snapshot.
What
strapped
note
state,
but
days
on
you
know,
on
the
under
non-existing
road
network,
no
to
be
able
to
ship
snapshots
with
the
binary.
So
essentially,
what
we'll
be
able
to
do
is
compile
tools
into
snapshot,
form
and
ship
that
and
get
even
faster
spinning
up
and-
and
you
know,
all
the
benefits
of
packaging
and
compilation.
C
C
C
First
line
of
tools
is
executed
will
benefit
from
having
that,
as
in
a
way
of
compilation,
you,
you
put
your
tool
once
you
take
a
snapshot
of
its
state,
you
can
ship
that
snapshot
as
a
resource
separate
file
or
bundle
it,
and
from
now
on,
you
have
a
new
recruit
binary
that
just
starts
at
that
stage.
It
can
run
from
that
and
it
doesn't
need
to
pack
to
ship
to
parse
compile,
run
all
the
steps
just
perform.
C
That
the
important
bits,
so
that's
that
snapshot
that
said
using
it
as
a
it's
a
metaphor,
that
report
from
p8
gate
works
that
way
on
your
browser
and-
and
you
note
a
gate
starts
with
you
know
all
of
the
primordial
all
the
intrinsic
functions,
everything
of
the
constants,
alright
everything's
already
in
memory.
It
just
starts
at
that
point
and
I
know.
Binary
will
start
one
step
further
and
after
that
the
plan
is
to
enable
core
level
platform
level
tooling.
C
A
C
C
C
A
A
All
right
super,
so
yeah
we'll
take
a
look
at,
or
at
least
I.
Well,
I,
don't
know
you!
Nobody
else
has
to
if
you
don't
want
to,
but
I'm
gonna
take
a
look
at
what
Williams
done
and
then,
hopefully,
hopefully
later
this
week
or
maybe
next
week,
I
can
I
can
look
further
into
argument.
Parsing,
an
implementation
if
I
have
a
chance
but
yeah,
so
alright,
so
I
think
I'm
gonna
call
it.