►
From YouTube: Node.js Tooling Group Meeting
Description
A
A
All
right
so
hi,
so
we
met
and
there
were
actually
quite
a
few
people
who
attended
the
session
at
Jay
s
confi
you
or
no,
not
Jay
Scott
for
you,
but
the
collab
summit,
but
in
Berlin
anyway.
So
yeah
there
were
some
I
kind
of
started
with
first
off.
Okay,
so
I
put
some
meeting
or
minutes
in
the
repo
from
that
meeting.
But
you
know
I
started
off
kind
of
explaining.
Okay,
this
is
the
tooling
group,
and
this
is
stuff
we've
done.
A
This
is
some
stuff
we'd
like
to
be
working
on
and
there
were
some
discussions
about
various
things,
but
we
didn't
have
a
whole
lot
of
time
to
get
into
a
lot
of
detail.
Among
the
topics
that
were
covered
include
things
like
rim,
dur
things
like
argument,
parsing
things
like
accessing
v8
flags,
node,
essentially
node,
exposing
those
another
thing
that
was
brought
up
by
Ahmad
Nasri
was
packaging
or
distributing
CLI
apps.
A
A
If
he
has
a
chance
to
talk
about
his
use
case-
and
you
know
I
feel
like
that
might
be
a
good
you
know
good
initiative
or
for
this
group,
but
yeah,
so
that
that's
kind
of
kind
of
basically
what
what
went
on
there.
There
was
also,
of
course,
the
typical
chatter
about
small
core
bla
bla
bla,
bla,
bla,
bla
bla,
so
not
not
super
interesting
or
or
new,
but
yeah
we
had
like
I,
don't
know,
maybe
15
20
people
in
there,
so
it
was.
It
was
a
good
group
anyhow.
A
That
is
that's
kind
of
that.
The
the
first
thing
on
the
agenda
was.
This
is
the
meeting
that
we
had
and
that's
kind
of
what
happened.
Of
course,
we
didn't
like
make
any
decisions.
It
was
mostly
just
kind
of
I
hesitate
to
call
it
brainstorming,
but
it
was
a
discussion.
So
then
you
were
there
anything
to
add
no
I.
B
Mean
we
definitely
had
a
pretty
long
conversation
about
whether
the
riff
raff
was
against
the
philosophy
of
small
core
that
was
solid.
20
minutes
I
have
some
thoughts
from
tc39
that
was
attended
immediately
afterwards,
which
was
the
idea
that
you
know
maybe
some
things
like
rim
Roth
could
be
in
kind
of
a
standard
module
like
as
nodes
scope,
or
maybe
that
would
help
diffuse
some
of
the
fear,
uncertainty
and
doubt
around
having
some
of
these
features
in
core.
A
B
It's
works
differently
that,
with
our
file
system
operations
right
then,
after
the
conference
I
proceeded
to
go
to
tc39,
where
I've
been
advocating
UUID
and
what
would
eventually
be
a
built-in
module
with
potentially
the
JavaScript
specification,
there's
actually
and
that
actually
wasn't
too
controversial.
I
think
a
lot
of
folks
I'm
sure
will
be
controversal
wants
to
get
further
along,
but
a
lot
of
the
initial
people
I
talked
to
we're
actually
really
excited
about
this
as
a
path
forward
for
some
of
these
little
utility
modules.
B
So
I'm
kind
of
wondering,
like
maybe
that's,
a
path
forward
for
some
of
these
more
complex
libraries
we'd
like
to
happen,
node
core,
maybe
they're,
actually
in
a
standard,
say
no
js'
namespace
or
something
infinitely
in
the
you
know,
first
as
being
say,
built
into
the
FS
module.
We
already
were
kind
of
talking
about
this
by
putting
it
into
the
into
a
different
space
than
FS
already.
C
B
Came
in
super-high
came
in
pretty
passionately
to
that
thread
when
I
was
working
at
NPM
and
it
was
like
no,
we
should
use
the
same
syntax
as
NPM
and
we
should
not
use
the
like
use
the
@
symbol
and
uses
forward,
slash,
I'm,
Way,
less
I
care
way.
Less
now,
I
think
it's
about
the
value
of
having
a
core.
We
did
some
built-in
modules
I,
don't
really
care
about
semantics
of
it
yeah.
A
B
That's
a
fair
point:
I
quote
this
is
not
solidified
I'm.
Just
wondering
like
is
this.
Maybe
we
don't
want
to
tie
yourself
to
this?
That's
fair!
That's
a
fine
point,
but
I
would
say,
like
maybe
there'd
be
less
if
we're
in
a
world
where
we
are
extending
the
core
JavaScript
and
the
core
node
api's,
and
we're
doing
so
through
these
built-in
modules,
it
might
be
less
friction
than
introducing
a
new.
B
C
B
No,
it's
totally
a
chicken
or
egg
problem,
yeah
I,
just
wonder
if
it
comes
down
too
late.
Listen,
we
understand,
you
know
a
chunk
of
the
new
ecosystem.
You
still
really
wants
to
adhere
to
this
small
core
philosophy.
We
get
this
core
stays
small,
but
here's
a
set
of
West
modules
that
that
are
extensions
to
core
that
live
in
those
namespace,
maybe
starts
to
be
an
easier
philosophical
discussion.
A
B
B
One
could
imagine
a
world
where
you
know
node,
13
or
whatever,
ships
with
the
rim
RAF,
and
then
we
back
port
import
Maps
to
note
all
the
way
back
to
say
no
to
11
or
something,
and
then
someone
can
ship.
The
shim
of
rim,
wrath
with
node
11
have
run
an
identification,
I
note
11,
but
when
you
get
node
13,
you
know
you're
going
to
get
this
set
of
modules
that
have
gone
into
who'd
gone
into
that
extended.
Okay,.
B
Of
discussions
around
modules,
but
no
real
paths
forward
yet,
but
lots
of
folks
who
are
excited
about
UID,
which
I
think
is
super
exciting
and
kind
of
dovetails-
are
some
of
the
work
we
want
of
you
in
the
tooling
group,
which
is
like.
Wouldn't
that
be
cool
if
node
just
got
you
ID,
because
it
was
part
of
the
JavaScript
language
now
and.
B
Not
necessarily
it's
it's
more
about
you
would
go,
it
would
potentially
go
into
the
specification
for
JavaScript,
which
would
say
to
be
a
JavaScript
complexity.
To
be
like.
I
can
fly
an
engine.
You
you
have
this
module
in
this
one
module
in
this
module
like
Yui
ID,
then
maybe
no,
it
has
its
own
implementation
or
maybe
it
comes
down
through
v8,
but
but
it's
just
more
of
us,
like
this,
we've
agreed
that
this
is
something
that
the
engine
should
have.
C
Yeah
I
did
some
work
on
the
weekend.
I
had
some
time
to
kill
him
Airport,
so
I
did
some
work
on
trying
to
get
the
linter
passing
I,
mostly
done
with
that.
Although
I
do
have
a
couple
strange
ones
that
I'm
still
working
out,
so
it's
kind
of
where
I'm
at
with
that
I
was
hoping
to
try
and
resolve
those
today
and
then
yeah
I
was
getting
ready
to
put
up
a
PR.
Although
there's
now
another
PR
as
of
this
morning,
so
yeah.
C
A
look
at
it
and
yeah
I
mean
I
think
there
are
some
issues
with
the
particular
implementation.
It
looks
like
kind
of
a
partial
rewrite
of
rim,
wrath
like
it's
definitely
based
on
the
original
rim,
ref
code
and
excludes
the
globbing,
but
it
also
excludes
a
lot
of
the
like
edge
case,
handling
for
Windows
file,
permissions
and
Solaris
and
whatever
other
crazy
stuff
is
in
rim.
C
And
then
yeah
the
other
I
guess
the
other
issue.
Is
he
implemented
in
a
way
similar
to
make
derp,
where
it's
a
it's
a
flag
to
rim
dur,
which
we've
kind
of
talked
about
like
that
makes
feature,
detection,
difficult
and
people
kind
of
wish
that
make
derp
had
been
implemented
differently.
So
it's
another
potential
issue.
A
A
Right,
well,
so
do
you
need
any
anything
with
the
Shu
tell
stuff
I
mean
you're
still
gonna
send
the
PR
right
yeah.
C
I
mean
I
think
so,
like
I
guess
what
what
is
sort
of
the
immediate
path
forward
here,
I
yeah,
it
was
planet
I'm
almost
finished
with
the
linter
fixes,
so
as
I
was
planning
to
submit
the
PR
unless
anything's,
unless
we
feel
anything's
changed
whether
that's
because
of
this
other
PR.
Because
of
discussions,
you
guys
had
at
the
collaborator
summit,
I.
B
D
B
B
B
C
Kind
of
why
I
was
thinking
like
there
is
more
work
that
I
want
to
do,
for
example,
writing
like
additional
tests,
and
things
like
that
and
writing
Docs.
But
I
was
kind
of
thinking.
Maybe
just
put
it
up
before
that's
ready
because
there
probably
is
gonna,
be
sort
of
an
ongoing
conversation
for
a
while
yeah.
B
I
think
that's
worthwhile
and
just
keep
it
will
keep
it
civil
whole
and
just
like
some
people,
I'm
sure,
come
in
on
one
side
of
the
conversations
people
come
down
the
other
side
of
the
conversation
and
as
long
as
we
don't
go
in
hoping
it
lands
in
two
weeks,
I
think
we
can
stop
it
from
big,
too
frustrating
right.
Okay,.
B
All
right,
it's
probably
the
coordinating
sorry
to
interrupt
I
was
gonna
say
it's
try
just
worth
for
anything
with
that
other
issue
too
and
say:
like
listen,
here's
kind
of
what
we're
thinking
for
the
tooling
group,
yeah
I
do
we
can
combine
out
for
it
just
so.
The
other
person
doesn't
feel
like
we
swooped
in
just
to
just
to
squash
their
PR.
A
So
like
it
can
get
pretty
frustrating
like
the
longer
it
sits.
The
more
people
comment
on
it
and
the
more
people
comment
on
it:
the
more
changes,
people
on,
etc,
etc,
etc.
So,
like,
if
you
are
feeling
frustrated,
you
know,
I'm
certainly
willing
to
go
in
and
just
like
hack
on
some
of
those
changes
that
people
want
just
to
like
just
make
it
less
like
frustrating
for
you,
because
I've
been
there
so.
B
Guess
yeah
another
interesting
thing
maybe
send
us
a
gist
over
before
you
open
the
PR.
Oh
that's
just
like
the
PRU
clan,
an
opening
in
terms
of
your
wording,
just
because
we
can
oh.
A
You
know
what,
though,
like
I
think
what
would
be
really
helpful
is
if,
and
maybe
like
really
impactful
is,
if
you
know,
whoever
in
this
group
is
interested
in
commenting
or
reviewing
that
code
like
if
we
can
come
together
like
like
as
a
common
front
of
like
this,
is
these
are
the
reasons
why
we
want
this
in
here
these.
Essentially,
these
are
our
talking
points,
and
this
is
our
platform,
and
you
know
I
think
if
we,
if
we,
if
we
are
careful
not
to
like
start
disagreeing
amongst
ourselves,
you
know
things.
B
Least,
this
was
kind
of
why
I
was
this
is
kind
of
why
I
was
thinking
a
little
bit
about
the
nodejs.
Namespace
was
because
one
of
the
topics
of
conversation
that
came
up
was
that
there
would
be
namespaces
for
some
platforms
where,
like
so,
it
doesn't
make
sense
for
a
FS
functionality
to
be
in
in
JavaScript
as
a
whole,
because
you
know
the
web
browser
doesn't
give
you
a
test
access.
No,
it
gives
us
access,
so
it
was
a
conversation
that
there
might
be
some
node,
specific
libraries
that
you
know.
B
B
Javascript
Commons
ends
up
being
called
so
like
Rim
ralphus
fits
this
bag
so
well,
it
goes
like
you
would
never
in
a
million
years
that
RIM
ref
in
the
browser,
but
it
makes
a
lot
of
sense
in
oh
I.
Don't
know,
I'd
also
want
to
derail
the
conversation
and
suddenly
have
it
be
at
six
months.
The
land
of
this
thing's
balance.
D
E
B
A
A
I
guess
I
tried
to
explain
that
you
know
if
we're
doing
this,
and
you
know
we
want
to
use
essentially
what
the
community
has
decided
on
like
how
they
use.
Api
should
look
and
what's
important
and
and
pick
the
pick
ax
men,
the
minimum
set
of
things,
but
again
P
is
somebody
that,
of
course,
that's
not
going
to
be
good
enough
for
everybody
because
they
want
like
total
control
over
buh-buh-buh-buh-byeeeee
yeah,
and
if
you
want
total
control
you
can
use.
What's
there
already,
but
essentially
yeah
I
mean.
A
B
B
About
that
afterwards-
and
he
was
saying
that
like
it
would
be
a
one-liner
to
turn
that
iterator
into
an
object,
so
I
think
maybe
we
could
figure
out
I,
don't
know
I'm
curious
to
hear
Cure's
point
of
view
just
because
he'd
be
an
advocate
of
it.
I,
don't
know
I'd
say
like.
If
you
look
at
you
did
a
good
literature
review.
I
mean
most
most,
the
community
seems
to
have
most
of
the
JavaScript
folks.
Gonna
use
something
that's
similar
to
the
minimis
approach
of
just
arguments
onto
an
object.
B
A
A
So
sorry,
I,
don't
know
how
to
pronounce
your
first
name
was
a
really
yeah
right.
It's
good
good
enough!
Okay,
you
sent
you
didn't,
send
the
PR,
but
you
like
sent
a
PR
against
your
own
fork
or
something,
but
you
had
implemented
something
I
didn't
get
a
chance
to
look
at
what
exactly
you
implemented,
but
I
I
only
added
you
to
that
that
other
the
repository,
where
the
did
you
get
it.
You
probably
didn't
get
a
chance
to
look
at
that.
Yet
I
just.
A
D
A
G
G
A
G
A
A
A
Diagnostic
reports,
and
so
diagnostic
reports
is
an
experimental
API.
It's
like
process
report
dot
report
and
it
basically
is.
It
creates
a
JSON
dump
of
a
bunch
of
info,
including
like
what's
on
the
heap
and
your
memory
usage
and
CPU
usage
and
a
whole
bunch,
there's
stuff
like
that,
and
so
I'm
making
a
tool
to
essentially
take
that
information
and
do
something
useful
with
it,
because
it
can
be
a
lot
of
information
and
it's
not
always
obvious,
and
so
there
are
little
bits
of
functionality.
A
But
one
of
the
things
is
it's
kind
of
like
it's
kind
of
like
a
linter
where
you
in
goes
the
report
and
out
comes
potential
problems
or
things
you
should
look
at,
and
so
as
part
of
that
work
I
have
at
least
a
couple
initiatives
to
improve
those
reports.
Those
diagnostic
reports
in
core
and
so
I
think
I
send
a
pull
request,
hopefully
later
today,
to
add
some
information
that
is,
in
my
opinion,
missing
from
the
report.
A
So
it's
just
kind
of
like
what
I
am
up
to
not
directly
related,
but
in
case
anybody
was
wondering
what
the
hell
I'm
doing.
Instead
of
other
things,
that's
what
I'm
doing
so
looks
like
Michelle
left
I
was
going
to
ask
him
if
you
had
anything
else
to
bring
up,
but
since
you
left
I
cannot
anybody
got
anything
they
want
to
bring
up.
F
B
The
basic
idea
is
that
maybe
this
maybe
this
would
be
something
we
should
eventually
have
it
note,
or
is
the
ability
to
package
very
precise,
very
concise,
binary
applications
that
just
some
model
of
NPM
modules
find
with
the
node
runtime
and
the
Joey
who
works
on
bed?
No
Jess
project
was
saying
that
they
were
actually
kind
of
close
in
terms
of
a
guy.
To
do
this.
It's
just
not
very
well
documented,
so.
B
A
A
I
mean
to
me,
it
sounds
like
this
is
something
that
we
would
absolutely
be
interested
in,
because
essentially
it
enables
more
tools,
better
tools,
things
and
would
you
know
they
can
be
distributed
more
easily
and
I.
Think
that
is
a
good
thing.
There
are
a
few
different
ways
to
go
about
it.
I
thought
I
remembered
something
about
v8
snapshots
in
core
I.
Don't
remember
who
I
talk
to
about
that
or
if
that
was
even
in
this
group
or
not,
but
that's
like
another
way
you
could
go
at
it.
I
think.
A
C
A
Then
a
part
part
of
the
the
thing
is,
then
you
know
people
you
do
this
in
what
you
distribute
is
essentially
node
and
a
bunch
of
JavaScript
or
something
like
that.
Right
and
people
are
gonna,
start
complaining
like
they
knew
about
electron
right.
Oh
there's,
all
this
stuff,
it
takes
up
too
much
memory
and
it's
just
not
the
load
times
to
slow
and
I.
Don't
know
like
so
like
it.
If
you
could
trim
the
things
out
of
node
that
you
didn't
want.
A
A
Think,
and
even
if
it
was
like,
how
would
you
you
would
have
to
have
some
sort
of
tool
to
like,
like
essentially
like
a
webpack
thing
where
you
say:
okay,
I
want
this,
and
that
and
ignore
these
other
things
and
I
wouldn't
want
to
try
to
foist
something
on
the
release
team
that
says
okay
now,
instead
of
the
all
these
various
LTS
versions
of
note.
For
all
these
different
architectures
were
going
to
exponentially
increase
the
size
of
that
build
matrix
by
having
a
node.
A
E
So
I
had
I
was
thinking
about
the
similar
like
and
I
think
that
we
can
look
at
it
in
terms
of
like
the
deployment
such
a
tool
and
release
in
a
different
manner
than
the
issue
of
the
full-blown
node
released.
I
think
it
would
be
definitely
more
useful
for,
like
the
three
major
platforms
and
probably
will
require
less
Ike,
LTS
and
backwards
compatibility
was
I
was
thinking
any
way
of
like
making
such
you
know
just
tip
of
the
tree
for
the
three
major
platforms.
E
Yeah,
like
a
trim
down
and
and
like
different
batteries,
included
sort
of
package.
I
think
that's
a
really
interesting
proposal
for
for
CLI
tools,
etc
and,
like
small
apps,
local
apps,
where
you
don't
need
opens
cell,
you
don't
need
httpd,
actually
be
to
like
wherever
a
lot
of
stuff,
that's
useful
for
servers
and
web
service,
not
so
much
for
say
like
tools
and
small
apps,
yeah
and
and
so
it's
a
little
bit
different.
But
we
started
this
initiative
on
the
belt
workgroup.
E
They
call
it
an
official
builds
for
you
know,
semi
often,
platforms
like
on
six
and
FreeBSD
and
even
Linux
on
32-bit,
where
we
supply
the
knowledge
and
like
basic
infrastructure,
and
we
run
those
builds
on
a
best-effort
manner
whenever
there
is
early
start.
So
we
can
like
set
up
a
build
script
for
those
and
I
can
get
stuff
without
all
the
encumbrance
like
a
full-blown
node
release
and
then
then
support.
You
know.
E
E
A
you
said:
you
talked
to
build
its
it's
already.
It's
already
up
and
running
I
think
it's
on
official
build.
E
E
E
These
are
just
the
product
of
some
like
some
scripts
and
some
some
build
for
me
and
I
did
we
run
whenever
a
release
is
cut
for
stuff?
That's
not,
you
know
experimental,
that's
ongoing
and
encore.
So
this,
like
branch,
we
can
add
whatever
and-
and
you
know
it-
it
just
happens
again
and
then
and
whenever
it
breaks
the
the
official
like
that
the
party
line
is
fix.
It
yourself,
like
nobody,
is
gonna
support
this.
B
B
C
E
And,
and
in
terms
of
you
know
tree
shaking
the
mother
tree,
it's
it's
it's
based
on
tools
and
concepts
that
are
already
in
like
site
and
and
and
went
back
and
rolled
up,
etc.
So,
like
the
thing
is
already
there,
if
somebody
really
I
think
you
can
see
some
of
those
around
like
people
who
are
really
committed
has
made
that
those
guys
scripts,
that
we
package
note
binary
to
do
different
things
and
even
make
it
cross-platform
at
cetera.
So.
A
E
It's
a
small
extension,
it's
not
that
far,
so
so
the
fit
lossless.
Essentially
it's
it's
a
lot
of
glue
and
then
they're
like
big
chunks,
that
you
can
shake
off
like
open,
SSL
and
HTTP
to
and
HTTP
like
ll,
HTTP,
parsing
and
layer
burn
broadly
so
those
are
like
like
yet
now
we
have
histogram
rendering
so
like
you
can
shake
those
whole
things
off
and
those
are
big
chunks
and
you
know
what
note
what
we
keep
your
in
slice
ours.
It's
not
that
much!
It's
like
it's
a
tiny
bit!
A
E
Yeah
you
can
build
like
most
of
those
libraries,
especially
for
like
Debian,
will
strongly
advocate
having
everything
there's
a
lid,
so
we
build
no
there's
a
completely
dynamically
linked
to
everything.
They've
been
links
against
Libya,
V,
OpenSSL,
zlib
HTTP
to
everything
is
built
everything
you
can
create
as
dynamically
linked.
So
we
have
that
in
build
scripts
already.
E
So
it's
actually
a
kind
of
very
fairly
modular,
so
definitely
somebody
will
have
to
it's
not
gonna
be
free.
Somebody
will
have
to
if
somebody
wants
to
make
his
own
tool
and
I
have
to
figure
out
some
things
and
find
out
the
right
parameters
and
and
test
it.
But
it's
not
like
years
away.
It's
like
it's
two
weeks,
work.
A
E
Then
nobody
uses
yeah
right.
It's
it's
for
it's
essentially
for
adding
stuff,
not
removing
yeah
I,
threw.
E
A
F
I
mean
you
could
also
stuff
a
loader
in
there,
and
so,
if
you
look
at
the
issue
that
we
have
open,
so
Bradley
farias
just
put
something
together
like
four
or
five
years
ago.
That's
pretty
similar
to
this
concept,
and
so
Jodi's
already
commented
on
that
and
made
some
stuff
so
probably
makes
sense
to
let
this
play
out
in
the
issue
a
little
bit.