►
From YouTube: Node.js Tooling Group Meeting
Description
B
Very
well,
oh
sorry,
let
me
make
sure
my
mic
and
everything
is
set
properly.
Oh,
it
is
do
I
just
need
to
speak
up,
maybe
maybe
okay,
well
Los
Gatos,
Oh,
South,
Bay
area,
yeah.
A
B
B
May
I
I
have
still
not
adapted
fully
yet
from
having
lived
in
Texas
for
so
long
so
yeah.
B
A
A
B
A
D
A
D
D
B
B
Yeah
I
think
it
would.
It
would
help
a
lot
for
like
one
of
the
things
I'm
looking
at
is
some
like
writing
some
shims
for
stuff.
So
in
enough
flicks
we're
trying
to
figure
out
what
our
story
is:
gonna
be
for
some
global
management
or
central
management
of
some
of
the
workflows
people
do
and
configurations
and
and
being
able
to
shim
and
then
process
replace
if
we
need
to
would
be
would
be
I
think
a
pretty
good
workflow,
but
I
haven't
figured
out
how
to
do
that
without
just
like
writing
some
bash
or
something
well.
B
A
You
yeah,
okay,
so
yeah,
we'll
figure
that
out
Wes.
Are
you
gonna
want
to
talk
about
like
import
maps
at
some
point?
Is
it
do
we.
A
Been
following
that
issue:
nah
no
I
mean
I
saw
that
you
sent
so
west
and
a
pull
request.
I
think
it
was
no.
B
B
But
we'll
see
yeah
III
could
I
could
talk
about
it
if
you
want
but
go
ahead.
Ben
sorry.
C
B
No,
it's
whether
or
not
it
should
ever
be
implemented
in
node.
There's
question
on
the
fact
that
it's
not
implemented
in
browsers,
yet
there's
questions
that
it's
a
what
wig
standard,
which
looks
to
be
insurmountable
as
far
as
Bradley
mech
is
concerned,
URL
or
wet
wig
standard,
yeah,
I,
don't
know
yes,
so
that's
why
I
said
I
asked:
what
can
we
do
to
change
this
and
he
said
I
don't
know
I,
don't
think
there
is
anything
you
can
do.
B
Maybe
why
he
has
this
opinion.
Okay,
I
think
he
has
some
some
bad
experience
with
them,
so
we'll
have
to
see
if
there's
a
way
around
that,
then
the
thing
I
and
I
presented
this
was
that
yesterday
word
that
we
chanted
yeah,
so
I
I
looked
I,
don't
a
proof
of
concept
of
how
NPM
could
build
these
and
then
and
built
a
loader
that
would
consume
them
and
then
I
pulled
out
some
of
that
work
and
that's
what
I
posted
in
the
in
that
issue,
which
I
think
would
be
interesting
from
it.
B
It
would
definitely
be
a
tooling,
but
if
we,
if
no
core
decided
to
support
it,
because
then
we
would
need
to
figure
out
how
all
the
tools
would
then
consume.
And/Or
generate
them
properly.
You
know
to
make
so
like,
for
you
know.
If
we
had
a
testing
tool
that
needed
to
discover
things,
it
would
probably
need
to
respect
them.
There's
all
sorts
of
things
that
I
think
would
be
affected,
but
none
of
that
really
matters
unless
we
can
get
support
behind
it
and
the
modules
working
group
I
think
so.
A
A
Involving
it's
I
mean
it
doesn't
work,
but
I
mean
it
it's
like
because
it
leaks
memory,
but
it
you
can
essentially
like
instantiate
new
new
loader
instances
and
like
abuse,
that
mechanism
to
load
like
very
loading,
GSM
module
multiple
times,
but
it's
just
again.
It's
it's
like
it's
leaky.
So
it's
not
something
anybody
could
really
use
at
this
point.
We
we
just.
We
need
something
that
allows
you
to
just
dump
them:
dump
the
module
somehow
and
I,
don't
know
what
the
I
mean:
Wes
you're,
probably
in
the
modules
are
you
in
the
modules
working
group.
B
A
Are
you
know,
that's
like
things
that
somebody
needs
to
figure
out
or
know
about,
but
again
Brian
was
looking
at
this
I.
Don't
know
if
he's
made
any
more
progress
on,
it
should
follow
up
with
them,
and
so
that's
probably
what
I'm
gonna
do.
Does
anybody
else
have
anything
they
want
to
talk
about
on
this
particular
topic.
A
All
right
meeting
it
opened
JSF
summit.
This
should
not
be
on
the
agenda.
Let's
just
skip
that.
So
this
was
issue
44,
which
should.
A
B
A
Sorry,
pardon
my
pardon
my
cussing
issue,
44.
A
Yeah,
that's
all
I
know,
but
yes,
this
should
be
closed
all
right.
So
let's
move
on
that
one.
So
a
better
way
to
detect
processes
exiting
this
is
issue
42
and
it's
I
don't
know.
What's
going
on
with
this,
it
might
be
just
a
quarry
thing
and
right
now
and
I
don't
know,
I
have
no
further
information.
Does
anyone
else
know
I.
C
A
C
C
And
then
the
only
other
thing
I
was
gonna
say
is
I,
did
talk
to
I
was
testing
it
out
with
express
and
I
was
having
a
conversation
with
Doug
Wilson
about
trying
to
get
it
working
with
express
and
it
turned
out.
I
was
wrong.
It
does
work
with
Express
already
as
soon
as
we
fixed
that
bug
that
was
making
Express
throw
exceptions,
so
it
actually
we
tested
and
it
works
with
Express.
C
So
next
steps
for
me,
I
guess
the
questions
kind
of
for
Chris,
unfortunately,
he's
I,
don't
know
where
he's
gone
I'm
but
but
I
was
thinking
maybe
like
I
feel
like
we
have
this
feature
now,
but
it's
not
very,
the
community
doesn't
know
we
have
it
so
like
I
was
thinking
I,
don't
know
if
you'd
be
open
to
it.
Wes,
maybe
I
wasn't
having
a
little
blurb
in
the
docs
somewhere
for
express
and
say
if
you're
running
typescript.
You
have
this
option
available
to
you.
B
C
Yeah
I'll
have
the
example
right
now,
but
turned
out
it
worked
for
expressed.
So
I
would
like
to
maybe
go
up
to
a
few
runtimes
and
be
like
hey.
You
know
we
have
this
available
to
you
for
introspection,
but
what
I
was
wondering
is
a
few
years
ago
I
wrote
a
blog
post
for
note,
4
and
I.
Think
I
used
medium
and
I
just
kind
of
wrote
up
about
coverage.
Basically
I
was
wondering
if
there's
still
like
PR
facilities
on
the
note
project.
D
A
C
A
C
C
B
C
Good
and
I
linked
the
kind
of
demonstration
of
typescript
working,
which
was
supposed
to
show
it
not
working
but
yeah,
but
I,
don't
know,
I'm
excited
I,
think
it's
a
win.
I
think
will
be
maybe
a
few
months
before
we
see
a
lot
of
adoption,
but
with
the
coverage
stuff
I'm,
just
starting
to
see
a
lot
of
adoption
now
and
in
Denver
like
two
or
three
years
in
so
things,
just
patience.
C
Don't
think
there's
any
other
action
items.
I
created
an
open
issue
to
try
to
see
if
we
could
bring
some
chromium's
chromium
has
actually
a
more
up-to-date
implementation
of
a
source
map
loader
than
v8,
but
I
started
looking
at
chromium's
and
it
has
a
lot
of
dependencies.
So
I
was
kind
of
thinking
of
closing
my
issue
and
saying:
let's
just
address
issues
if
we
run
into
them.
C
The
only
thing
I
saw
chromium
did
that
we
don't
do
that.
We
probably
should.
Is
it
sorts
the
source
Maps
in
order
of
their
position
in
the
codebase,
I,
guess
and
Cory
said
that
he
could
take
advantage
of
this
for
some
of
the
stuff
he
wants
to
do
so.
So
it
looks
like
Cory
had
asked
for
this
and
then
I
noticed
chromium
does
it,
so
it
must
be
that
they
realized
it
was
beneficial
before
d8
down
before
v8
downstream
get
yeah,
but
that's
it
features
there
play
with
it.
C
Be
willing
to
let
me
look
at
my
calendar.
I
would
potentially
Roy
you
willing
to
just
do
a
hacking
session
next
Friday
for
an
hour
in
the
afternoon
or
something
right,
cool
yeah.
If
we
think
we
could
both
make
an
hour
in
our
calendar
because
I'm
excited
about
this,
but
it's
I'm
not
gonna,
do
any
work
unless
I
carve
out
work
for
it.
D
D
C
A
C
C
I,
when
I
landed
that
PR,
we
added
a
special
environment,
variable,
that's
sticky,
so
that
you
can
test
some
some
processes
in
in
node
yeah,
okay.
So
this
would
be
basically
taking
that
and
making
it
something
that's
blessed
so
that
other
people
could
use
this
sticky
environment,
variable
approach
and
it's
really
valuable
for
tooling,
because
you
can
be
like
I-
want
to
get
monitoring
information
for
this
process,
plus
all
its
sub
processes,
even
if
someone
in
their
unit
tests
is
blowing
away
the
environment
I'm.
C
A
C
Way
we
did
it
with
coverage.
Was
this
special
variable
called
note
underscored
the
8
underscore
coverage
and
it
doesn't.
It
gets
maintained
in
a
subprocess,
even
if
you
cleared
out
the
environment
argument,
but
you
can
unset
it
so
there's
a
mechanism
to
unset
it,
but
by
default
it's
a
little
stickier
than
the
default
environment
variables,
so
I
think
Cory's
argument,
which
would
be
good
to
have
this
for
other
types
of
tooling,
where
you
want
to
make
sure,
even
if
someone's
writing
unit
tests
that
it
trickles
down
to
that
thing
being
instrumented
by
your
unit
tests.
C
But
we've
had
it
in
note:
we've
had
it
for
this
one
thing
in
node
for
two
years
now,
probably
I
think
and
it
hasn't
created
any
real
stirs.
So
I
don't
think
it's
really
stepped
on
anyone's
toes
I
could
imagine
if
a
bunch
of
people
were
doing
it
for
more
common
environment
variables,
though,
like
you
start
to
get
in
this
world,
where
maybe
your
braking
unit
tests
or
say
I,
don't
know
it
could
be.
I
could
see
where
it
could
be
a
problem
too.
C
B
There
are
reasons
you
might
want
to
do
this
so
again,
I
mentioned
I've
been
working
on
how
we
can
centrally
manage
configuration
for
node
and
other
tools
in
the
JavaScript
ecosystem
here,
and
one
of
the
things
I've
been
working
on
is
getting
in
between
the
users
and
the
and
the
tool
and
setting
environment
variables
and,
and
that
you
know
as
a
way
to
manage
configuration,
so
I
think
as
a
general
purpose
tool.
There's
certain
reasons
why
this
might
be
nice
to
expose.
B
A
C
Issac
reported
a
couple
Mick
maker
recursive
bugs
yesterday.
One
is
related
to
it
not
populating
path
in
an
error
situation
which
is
actually
reported
in
another
thread
and
the
other
one
was
related
to
it.
Returning
a
Ino
exist
instead
of
a
permission
error
when
I
think
you're
trying
to
create
a
folder
in
a
folder,
you
don't
have
permission
to
create
a
folder
with
them.
C
So
I
don't
know,
I've
been
just
with
bringing
that
up.
I
sure
I
can
I
might
honestly
see
later
this
afternoon.
If
I
have
the
energy
and
willingness
to
take
a
look.
I
haven't
I
haven't
looked
at
that
in
a
couple
years.
So
it's
you
know.
Hopefully
it's
not
a
huge
bug,
but
if
it's
like
super
nitty
gritty,
yeah
I,
don't
know
it
couldn't
be
like
a
two
second
fix
and
it
could
be
a
giant
pain.
So.
C
A
A
Okay,
well
I
would
say
if
you're
not
gonna,
be
able
to
get
to
it
or
something
Pingping.
The
group
cool
sounds
good,
all
right
cool,
so
we're
at
about
a
half
hour,
and
this
is
everything
that
we
had
on
the
agenda,
not
not
a
whole
lot
of
attendees
today,
some
reelers
couldn't
make
it
so
is
there
anything
anybody
else
would
like
to
bring
up
at
this
time
or
show
we
get
our
half-hour
back.
Yeah.
D
I
have
no
more
thing,
you
know
actually
I'm
just
starting
to
work
on
all
the
work
to
support
workspaces
on
NPM
so
with
anyone
else
from
the
group
I'm
already
in
touch
with
Wes.
If
anyone
else
wants
to
participate,
just
maybe
just
okay
time
to
have
some
conversation
right
now,
I'm
just
sourcing
ideas,
I'm
having
a
talk
with
a
bunch
of
people
from
the
community.
So
if
anyone
wants
to
at
least
talk
just
reach
me.
D
D
A
You
kind
of
give
a
like
a
high
level
overview
of
what
you're
trying
to
do.
You
know
yarn
and
lerna,
but
what
exactly
is
this
from
yarn?
What
exactly
are
you
looking
at
from
Lerna
I
mean
it
sounds
to
me
like
this
is
going
to
end
up
being
better
support,
for
you
know
mono
repos,
but
what
is
that?
What
does
that
mean?
I,
don't
actually
know
what
yarn
workspaces
do,
because
I
don't
use
yarn,
so
lay
it
on
me.
Man.
D
D
The
package
maintainer
right
so
we're
we're
kind
of
following
the
lead
yarn
on
at
least
aphasic
today's,
except
for
we've,
probably
copied
some
things
from
there
api's
and
but
there
is
also
learning
which
is
a
big
open
source
project
that
tackles
the
same.
The
same
problem
of
managing
normal
repos.
D
B
The
one
thing
learner
does
that
is
sort
of
different
here.
Is
it's
not
doing
any
package
resolution
logic?
Really,
it's
relying
on
the
tools
you
know
NPM
and
yarn
to
do
that,
for
it
right
so
so
learn
adjust
is
like
some
workflow
things
for
managing
a
bunch
of
packages
in
a
single
repo,
and
then
it
calls
out
to
the
underlying
tools
for
when
it
needs
actually
like
install
and
resolve
packages.
B
D
I
had
a
good
chat
with
Daniel
Stockman
from
Lerna
from
the
loop,
the
maintainer
there
and
yeah.
We
had
a
great
conversation
yeah.
Ideally
he
does
a
bunch
of
stuff
to
actually
support
the
NPM
use
case,
because,
right
now
we
don't
support
workspaces
so
by
implementing
that
we'll
be
taking
a
lot
of
the
heavy
load
from
Lerna
so
that
they
actually
can
just
like
shell
to
yarn
and
then
PM
to
do
the
heavy
lift
of
managing
the
package,
and
they
can
focus
on
like
things
like
publishing,
all
the
multiple
packets
managing
their
version
yeah.
D
A
Okay,
so
the
short
answer
to
your
question
is
no:
what
I'm
trying
to
understand
is
so
I
know:
I
use,
NPM,
I
use,
lerna
I
have
a
mono
repo
I,
don't
understand
what
like
I
mean.
I
could
go
google,
this
stuff
sure
but
like
what
is?
What
what
are
you?
What
do
you
aren't
workspaces?
Give
you
wait
a
minute.
You
say
you
use
all
that
I
use,
Luna
I
have
mono
repos
I
use.
D
D
B
I
can
maybe
I
can
jump
in
here
a
little
bit.
So
what
your
workspaces
does
is
when
you
have
a
package
Jason
that
has
a
key
of
workspaces,
which
is
an
array
of
paths.
It
goes
and
hoists
the
modules
out
of
all
of
those
paths
and
up
to
your
top
level.
So
it
does
the
version.
You
know,
resolution
logic
and
we'll
it's
like.
Normally,
when
you
and
Kim
install
in
directory
right
and
then
Kim
does
that,
for
you
hoist
as
much
up
as
it
can
learn.
B
Sorry
yarn
workspaces,
takes
it
another
level
and
treats
it
like
one
whole
project
where,
if
you
had
a
package
Jason
at
the
top
and
all
the
dependencies
of
and
all
the
dependencies
of
the
top
are
your
workspaces.
It
then
takes
and
hoist
another
level
up.
So
that's
the
technical
details
of
what
yarn
workspaces
does
and.
A
A
I,
don't
I
don't
use
it
because
it
seems
like
kind
of
ink
II
but
like
yeah.
It
seems
like
it
would
try
to
do
something
like
that,
for
you
I,
don't
know
like
D,
dupes
or
something
weird
anyway,
but
it
sounds
like
what
you're
describing
is
is
just
like
kind
of
makes
it
easier
to
work
with
that
stuff.
I.
D
A
C
A
B
So
I
have
I
expressed
some
of
these
to
Rory,
but
I.
Think
there's
I
started
talking
a
little
bit
about
this
at
the
club
summit
as
well.
I
really
do
think.
There's
a
space
for
something
in
between
these
I.
Don't
know
so
I'm
working
a
little
bit
on
some
of
this
sort
on
the
side,
but
I
haven't
had
time
to
polish
anything
up
and.
B
B
You
know,
but
I
think
that
if
we
and
you
know
if
there's
help
there,
that
that
would
help
you
think
bigger
without
having
to
overcome
it
and
and
have
to
try
to
deliver
on
something
that
you
can't
timeline-wise.
You
know
maybe
that's
something
where
we
could
I'd
be
willing
to
help,
and
then
maybe,
if
we
can
get,
you
know
some
peeps
some
eyes
on
it
from
from
this
group
to
say,
like
yeah
that
looks
useful
or
well
no,
there's
a
lot
of
problems
with
that
approach.
D
Yeah,
yeah
and
yeah
so
to
clarify
Chris
I'm
like
I'm,
not
a
motor
repo
user
at
all,
so
I
have
never
used
your
words
faces
nor
learner.
So
that's
why
I'm
reaching
to
the
group
like
if
your
interest
I'd
love
to
hear
your
opinions
on
it.
So
it
seems
like
you,
you
are
a
user,
so
if
you're
free,
if
you
have
some
time
during
the
week,
I'd
love
to
connect
yeah,
so
I,
just
because
right
now
I'm
kind
of
new
this
research
during
this
week
so
I
had
the
chat
with
them.
D
C
C
D
A
B
B
In
that
so
this
des,
maybe
this
does
relate
a
little
bit
to
the
import
Maps.
So
in
that
issue,
I
did
offhandedly
mentioned
the
work.
I
showed
you,
which
is
this
like
implementation
of
workspaces
using
implements
instead,
and
he
called
that
out
and
said
well,
there's
much
better
ways
to
do
this
and
he
was
like,
and
then
he
presented
to
yarns
specific
concepts
and
I'm
like
okay,
but
that
doesn't
like
you
made
these
up
like
these
aren't
specs.
B
These
aren't
anything
right
like
I
want
to
work
on
us
coming
to
some
central
thing
that
every
tool
can
build
toward.
You
know
and
we're
not
just
like
saying:
oh
yeah
use
Internet
Explorer,
it
works
they're
like
we
know
how
that
goes
right
so
like
so
he
has
these
two
concepts,
portals
and
I.
Guess
the
other
one
is
links
right,
I,
think
it's
portals
and
lakes
I
think
it'd
be
interesting.
B
You
know
they're
interesting
concepts,
they're
related
to
workspaces
in
that
they're
V,
the
yarn
v2
work
looks
like
it's
going
to
be
using
these
quite
heavily
and
and
one
of
the
big
things
that
I
think
is
really
problematic.
With
this
approach
that
they're,
taking
and
I
don't
know
how
to
fix
it,
cuz
I
just
don't
want
to
necessarily
work
on
yarn,
so
that's
whatever,
but
if
they
do
this,
these
are
in
the
package
Jason
as
dependencies
right.
So
your
dependency
declaration
will
have
a
you
know:
hello
package
I'm
your
HelloWorld
package
with
it.
B
Like
that
and
how
we're
gonna
reconcile
that
with
between
yarn
and
NPM
users,
is
just
I,
don't
slick
a
disaster
as
far
as
I'm
concerned
like
I,
just
don't
I,
don't
see
that
as
a
good
way
and
portals
are
similar
unless
NPM
and
yarn
can
come
to
you
know
the
CLI
scheme
can
come
to
a
convergence
on
that,
then
maybe
it's
fine
like
the
feature
is
good.
It's
just
like
you
know
proprietary
and
it's
not
obviously
proprietary.
This
open-source,
but,
like
the
you
know,
we're
gonna
go
our
own
way
and
be
totally
incompatible
to
me.
B
D
B
D
B
B
You
know
users
at
my
company.
It
makes
it
really
really
difficult
right
because
I'm,
obviously
not
gonna,
be
able
to
say
no
I'm,
not
gonna
go
tell
them.
No.
You
can't
have
this,
but
I
need
a
solution
that
I
can
trust,
and
that
is
going
to
be.
You
know
a
good
long-term
commitment
and
you
know
and
I
don't
think
we're
at
that
state
yet
with
unfortunately,
either
of
the
package
installers
and
it's
at
from
NPM
site
it's
only
because
it
doesn't
have
workspaces
today,
at
least
you
know.
B
A
I'm
back
my
computer
60a,
so
right,
yeah
I
would
love
to
give
you
some
feedback.
Awesome.
So
I
mean
you
can
try
it
like
schedule,
meeting
with
me
or
whatever.
If
you
want
to,
if
you
just
would
chat
or
whatever
you
want
to
do,
but
I
am
in
I,
am
in
the
boat
of
I
use,
mana,
repos,
I,
use,
NPM
and
learn
and
I
have
some
I.
Don't
know
if
I
have
ideas
for
solutions,
but
I
can
tell
you
about
pain,
points
for
sure,
yeah.