►
From YouTube: Node.js Tooling Group Meeting
Description
A
Okay,
we
are
live
on
YouTube,
all
right
hi,
so
this
is
the
node.js
tooling
meeting
here
on
Tuesday
July,
2nd
2019
and
not
a
lot
of
people
today.
So
what
did
we
have
to
talk
about?
We
there
was
we'll
get
to
in
your
stuff,
but
there
was
a
some
chatter
a
couple
weeks
ago
about.
A
Essentially,
packaging
command-line
tools
as
binaries,
just
something
that
can
be
distributed
easily
without
having
people
having
to
install
node
or
NPM
and
I,
definitely
think
that's
something
we
should
follow
up
on
there.
Some
also
chatter
inside
my
company
about
you
know
we
have
the
need
for
that
sort
of
thing
too,
and
so
you
know,
maybe
we
can
try
to
try
to
get
some
resources
together.
I
mean
no
no
promises
or
anything,
but
I
know
it's
on
people's
minds.
A
Not
just
you
know
a
mod
or
whatever,
but
it's
something
that
that
I
think
quite
a
few
people
are,
if
they
don't
know
they
need
it
like
once
they
have
it.
They'll
say:
oh,
how
do
I
live
without
this,
so
I
think
that's
something
we
should
definitely
keep
keep
tabs
on
and
see.
If
we
can
maybe
move
that
conversation
forward.
A
Yeah,
if
something
about
like
maybe
export
restrictions
or
or
government
contracts,
saying:
okay,
you,
if
it's
not
source
available,
it
needs
to
be
in
a
binary
format
or
something
like
that
and
so
and
I
don't
I,
don't
know
the
whole
legal
and
the
requirements
around
it.
But
this
is
kind
of
the
gist
I
got
was
that
somebody,
one
of
our
clients
needs
like
these
tools
in
a
certain
format
or
even
an
application
in
a
certain
format,
which
is
essentially
a
self-contained
binary
and
so
I
know,
that's
one
of
the
ways
to
approach
it.
A
A
You
know
your
code
is
and
even
then
like
de
novo
and
and
gain
cracks.
You
know
you
can't.
Really
you
can't
keep
it
hidden.
Security
through
obscurity
is,
is
not,
it
doesn't
work,
but
that
said,
it
ticks
boxes
for
some
people,
and
so
it's
something
that
people
want
people,
meaning
probably
bureaucrats.
A
Anyhow,
that's
like
another
use
case
for
it,
but
still
it's
a
it's
a
you
know
means
to
an
end.
It's
all
the
same
result,
self
self,
executable,
binaries,
and
so
that
would
be
cool
but
I
don't
know
there
was
some
talk
about
like
how
we
could
what
needs
to
happen,
maybe
to
buy
Sam
what
needs
to
happen
to
make
that
work
but
and
yeah.
So
the
other
thing
then,
was
the
Shu
till
or
rim
wrapper
or
whatnot,
and
so
you
know
I
guess
I'll.
Let
you
just
go
talk
about
where
you're
at
with
that
all.
B
B
Yeah
so
I
mean
I,
put
up
the
PR
or
I
think
just
before
a
previous
meeting.
There
was
definitely
a
lot
of
feedback
about
the
Shu
till
library
seems
to
be
at
least
one
of
the
consensus.
One
of
the
major
consensus
is
there
is
that
people
want
to
see
this
in
the
FS
module
mm-hmm,
which
I'm
not
opposed
to
so
now
the
question
is
kind
of
how
do
we
get
it
into
the
FS
module?
A
On
glob,
which
has
a
dependency
on
FS,
real
path
and
in
flight,
which
has
an
appended
c
on
once,
and
wrapping
inherits
and
mini
match,
embrace
expansion,
etc,
etc.
Exactly,
and
so
you
would
have
to
essentially
just
like
take
the
tree.
I
mean
it's,
it
sounds
worse
than
it
is
right.
You
you
just
you
tar
ball
it
and
throw
it
in
or
not
tar
ball
it,
but
I
mean
you
just
copy.
All
the
files
right
is
that
is
that,
essentially,
what
what
how
you
do
it
or
I
mean.
B
So
yeah
I
mean
that's,
it's
possible,
there's
a
way
to
get
that
to
work.
I
think
the
other
option
would
be
like
we
patch
rim
ref,
when
we
pull
it
in
to
remove
glob,
but
that
I
don't
know
that
sounds
kind
of
tedious,
otherwise
yeah.
We
have
to
go
like
the
fork
route.
I
guess,
which
I
see
some
of
the
concerns
that
people
have
with
that.
So
I'm
not
100%
sure
what
the
best
way
forward
is
I.
B
A
B
B
Right
yeah,
so
I
don't
exactly
know
like
I,
don't
think
those
all
get
built
into
the
binary
I
don't
know
I
mean
I
can
dig
into
this
further.
Like
I
said,
I
was
just
going
off
of
miles.
Example
of
fetch,
which
I
think
has
no
dependencies.
I
can
yeah,
maybe
I'll
look
into
how
like
NPM
is
being
pulled
in
here.
Well,.
A
B
B
A
A
A
A
And
so
then
you'd
have
this
patch
file.
That
would
need
to
be
part
of
the
build
that
would
get
applied
to
rim
ref.
Before
it's
rolled
in
and
I
know,
we
do
have
some
air
I
thought
we
did
at
some
point.
I
don't
know,
have
some
patches
somewhere
against
things
like
v8,
because
I
know
we
do
that
we're
right.
We
need
a
fix
in
v8
that
it
hasn't
gotten
upstream.
A
Yet
we
have
to
float
it
until
it
does
right,
but
in
this
case
it
would
be
like
more
of
a
permanent
thing,
and
people
may
have
opinions
about
that
in
I.
Couldn't
tell
you
what
those
opinions
are,
but
I
could
see
somebody
being
like.
No,
we
don't
want
to
have
this
patch
file
around
just
go
ahead
and
vendor
the
whole
thing,
and,
and
so
I
mean.
A
B
B
Right
yeah,
I'll
post
in
the
issue
and
see
if
we
can
get
some
kind
of
direction
there
and
then,
as
soon
as
we
do,
I'll
get
the
PR,
updated.
I
think
like.
If
we're
one
nice
thing,
if
we're
ven
during
it,
we
don't
have
to
add
many
tests
because
it's
already
tested
we
just
have
to
test
the
integration
on
our
end.
Yeah,
maybe
I
mean
I,
hope
so
yeah.
So,
okay
I'll
do
that
I'll
find
out
later
today.
All.
A
C
From
a
new
forum,
yeah
yeah
yeah,
so
yeah
I
was
mentioning
because
he
had
just
reviewed
yes,
PR
and
I.
Had
my
thing
going
on
too
with
the
argument.
Parser
right-
and
one
thing
he
was
talking
about-
is
that
there
is
actually
this
consensus
of
not
adding
any
new
top
level
package.
So
if
you
want
to
it
needs
to
go
through
the
TRC
and
be
approved
and
everything.
So
he
was
just
saying
that
is
easier
to
just
open
those
against
anything
like
for
the
argument.
Parser,
it
was
suggested.
C
Maybe
just
do
we
don't
look
he'll
have
it
live
in
there
for
the
as
an
experiment
and
like
if
it
stabilizes,
you
might
eventually
get
its
own
top-level
package,
but
like
for
just
opening
the
PR
I'm
just
making
our
lives
it'll
be
easier,
it's
better
to
just
find
somewhere,
maybe
go
to
at
the
end
yeah.
You.
C
B
Of
make
sense,
yeah
I
was
gonna,
say
just
about
argue.
A
parsing
I
actually
like
that
came
up
for
me
at
work
last
week.
I
was
writing
just
like
a
command-line
tool
and
then
at
some
point,
I
was
working
on
it
I
needed
to
accept
a
single
flag.
There
you
go,
it
happened
like
but
I'm,
not
gonna
install
yards
or
whatever
yeah.
It
was
just
you
know,
process
arc
v2
equals
whatever
do
this
mm-hmm.
It's
like
it's
such
a
slippery
slope
like
I,
want
to
add
another
flag
or
I.
B
B
C
B
C
B
C
B
I
saw
that
I
should
be
being
mentored,
but
anyways,
so
I
have
a
mentee
now
and
I
think
like
she
was
specifically
interested
in
some
of
them,
like
tooling,
related
stuff.
So
if
there's
any
little
things
like
that,
like
writing,
Docs
or
tests
or
whatever
it
would
be
like
good
first
contributions,
just
yeah,
maybe
keep
that
in
mind.
So
it
was
my
way
or
something
and
I
can
see
if
she's
interested
in
working
on
them.
You.