►
From YouTube: Node.js Tooling Group Meeting 2021-06-25
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
C
Hello,
everyone-
this
is
meeting
of
the
node
tooling
group,
it's
friday
june
25th
thanks
for
joining
us
small
small
group
today,
so
yeah.
Let's
take
a
look
here.
What
do
we
have
on
the
agenda?
C
So
it
looks
like
first
up
there
was
this
discussion
about
you
know:
do
we
want
to
use
eslint
or
something
to
maybe
point
out
packages
that
have
been
sort
of
pulled
into
node?
I
think
I
I
would
say
that
was
not
well
received,
although
it
was
really
only.
I
think
it
was
jordan
that
was
kind
of
giving
feedback
on
it
and,
and
he
definitely
had
some
some
valid
feedback
there.
So
I'm
not
really
sure
how
to
proceed
with
that.
I
don't
know
if
we
really
should.
You
know.
A
C
C
Seems
like
kind
of
the
wrong
move.
So,
oh,
it
looks
like
darcy's,
so
yeah
anyways,
that's
a
fair
point
and,
like
honestly,
I'm
not
really
sure
what
the
the
path
forward
would
be
there
and
it's.
I
would
still
like
to
do
something
there
like
it
would
be
really
nice
it's
kind
of
a
bit
frustrating
if
we're
like
building
these
new
things
into
node,
and
then
people
don't
know
about
them.
So
don't
use
them.
A
I
have
a
suggestion:
maybe
we
close
this
issue
and
just
open
up
a
new
issue.
That's
more
generic
like
how
do
we
alert
people
to
these
new
features,
and
then
we
can
kind
of
brainstorm
there
and
figure
out
what
might
be
good.
C
Yeah,
okay,
I
think
that's
a
good
good
way
to
handle
that.
So,
let's
I
guess
moving
on
next
on
the
agenda
recursive
copy,
I
have
not
made
any
progress
on
that.
C
I'm
sorry
and
I
didn't
mean
to
talk
over
you,
I'm
sorry.
I
was
just
going
to
say
I
had
kind
of
mentioned.
I
think
in
a
previous
call,
I'm
I'm
actually
a
little
bit
more
interested
in
working
on
the
command
line.
Argument
parsing
right
now
and
I
think
we
kind
of
decided
as
a
group
that
that's
where
we
should
focus
our
effort
in
the
short
term.
So
yeah
no
updates
from
me
on
the
recursive
copy.
B
B
I
think
I'm
looking
to
pick
up
something
like
like
it
looks
like
euid
ships
in
30
days,
and
that
was
like
my
big
open
source
project,
so
I'm
looking
for
something
new.
I
think
that
would
be
good
yeah.
That
sounds
good
to
me.
C
Okay,
well,
let's,
let's
move
on
from
that
for
now,
then
I
guess
next
on
the
agenda
was
a
better
way
to
detect
a
process
is
exiting,
I
think,
ben
you
had
a
you
had
originally
said.
You
were
interested
in
that.
B
I'm
interested
but
have
not
done
any
work
on
it
at
all
and
I
think
in
the
grand
scheme
of
things
I
become
less
interested
in
this
with
my
hacks
working
currently,
so
it
feels
like
maybe
it's
a
problem
that
only
comes
up
for
like
a
for
people
who
are
actually
writing,
mocha
or
or
nyc
or
c8.
Maybe
it's
not
a
problem
that
the
whole
community
has.
C
Exactly
okay:
let's
move
on
to
source
map,
v3
support.
You
said
you
had
a
couple
couple.
Developments
on
this
ben
couple:
bug
fixes.
B
And
kind
of
their
they
patch
a
really
glaring
kind
of
just
hard
failure
for
users,
but
they,
I
think
both
my
fixes.
B
Aren't
perfect,
let
me
see
here
basically
the
exception.
We
don't
properly
apply
source
map
logic
to
our
helper
message
that
we
show,
if
you've
screwed
up
an
esm
import,
which
we
didn't
notice
until
esm
started
getting
adopted.
But
it's
actually
not
easy
to
do
that
so
kind
of
a
request
for,
if
anyone's
looking
for
a
place
to
contribute
to
source
maps,
I
left
some
to-do's
and
that
first
link
I
shared
and
what
was
the
other
bug.
B
Oh
source
map,
re-key
logic
didn't
work.
If
you
throw
a
string
or
number
it's
just
a
really
weird
bug,
I
hadn't
noticed
and
it
doesn't
seem
like
we
even
need
the
re-key
logic
anymore.
So
I
just
deleted
it.
So
that's
more
boring
so
shows
people
are
using.
The
good
thing
is,
it
shows
people
are
using
the
source
maps.
I
suppose
it's
two
weird
two
weird
edge
cases,
so
that's
just
an
update.
I've
fixed
two
bugs
for
source
maps.
B
B
B
If
a
module
fails
to
load,
I
believe
it
never
gets
cached.
So
there's
no
like
there's
nothing
for
us
to
kind
of
tie
the
file
name
onto
because
it's
no
longer
exists.
B
B
D
B
Now
it
looks
reasonable.
It
says,
like
failed
to
import,
failed
to
import
this
symbol,
but
before
it
basically
threw
an
error
in
our
source
map
handling,
rather
than
an
error
in
in
dsm
import.
B
B
B
B
So
it's
kind
of
like
the
long
tail
of
if
you're
using
source
maps,
you
should
always
be
told
what
happened
in
your
original
code.
Not
your
transpiled
code
is
the
goal.
Another
long-standing
open
thing
in
that
category
is,
I
think,
in
the
terminal.
We
don't
properly
work
for
throwing
exceptions
in
the
terminal
either
because
they
do
a
bunch
of
rewriting
of
exceptions
as
well.
A
C
Okay,
I
guess
next,
if
we're
done
with
that
topic.
Next
up
is
argument:
parsing
everyone's
favorite.
A
Yeah,
it's
a
good
one,
but
I
don't
have
any
news,
I'm
looking
forward
to
having
news
and
I'm
hoping
to
have
more
time,
thursday
of
next
week
and
beyond,
but
up
until
then.
I
don't
think
I'll
have
any
time
to
work
on
this.
C
I
have
a
sort
of
somewhat
crazy,
related
idea.
I've
been,
I
know
the
the
cfp
for
node
conf
remote,
which
I
think
used
to
be
node
conf
eu
is.
It
was
actually
coming
up
like
right
away
here.
I
think
they
extended
it
to
july
30th.
If
I'm
not
mistaken,.
A
C
But
yeah,
I
don't
know,
I
thought
like
something
like
the
the
the
argument.
Parsing
could
make
an
interesting
talk.
I
don't
think
we'll
have
it
landed
in
node
by
then,
but
even
if
we
had
our
sort
of
like
like
polyfill
and
like
you
know,
if
it
was
working
the
way
we
kind
of
expected
it
to
work
and
and
had
like
proposed
it,
I
think
even
that
could
be.
A
Yeah
yeah
for
sure
deadlines
are
crucial
like
is
it
something
that
you
would
propose?
Are
you
just
suggesting
it.
C
I
mean
it
could
go
either
way.
I
I
would
feel
I
mean
at
least
up
to
this
point.
I
haven't
been
as
involved
as
other
people
in
the
argument.
Parsing
work,
so
I
would
maybe
feel
a
little
bit
weird
presenting
about
it,
but
on
the
other
hand
I
mean-
maybe
maybe
I
will
be
helping
out
more
here
in
over
the
next
couple
months,
so.
C
Yeah,
I'm
not
sure
if
they
are,
but
that's
not
a
bad
idea.
We
could.
We
could
also
do
it
potentially,
like
you
know,
a
couple
of
us
could
get
up
there
and
and
talk
about
it.
Maybe
maybe
I'll
work
on
putting
something
together
for
a
proposal,
and
we
can
kind
of
figure
it
out
after
that,
like
who's
gonna,
do
this
or
and
I'll
check
it
out
and
see
what
they
have
for
yeah
like
what,
if
they're
looking
for
for
like
panel
type
discussions
or
just
talks
or
what.
C
Okay,
yeah
I'll
I'll,
follow
up
with
more
info.
A
C
B
D
Mediocrity
yeah
might
maybe
we'll
do
something
with
npm
I'll
get
somebody
from
the
team
to
to
do
something.
That's
a
good
one
yeah,
but
we're
we're
constantly
shipping
stuff
yeah.
I'm
interested
in
a
deadline,
though,
like
I
having
something
like
a
conference
coming
up
that
like
forces
you
to
ship
is
always
great,
especially
if
you
want
to
like
showcase
something
working.
So
I
can
try
to
find
dedicated
time
to
like
help.
This
make
it
real
like
that,
a
reality
yeah.
D
It
helps
when
it's
like
you
know
your
face
is
on
a
website
with,
like
a
date
attached
to
it
and
there's
like
a
community
of
people
and
maybe
even
people
that
paid
to
like
watch.
You
be
mediocre,
which
is
like
you,
you
said
you
did
one
talk
that
was
mediocre
ben.
I
I'm
like
I've
got
a
like
whole
like
career
of
mediocre
ducks,
but
yeah.
No,
I'm
I'm
definitely
interested
if
you
do
that
in.
Like
that's
that's
great,
like
definitely
talk
about
this.
I
I
want
this
so
badly.
A
A
B
I've
started
having
people
have
been
sniffing
around
performance,
ddos
attacks
on
yargs
recently,
and
I
had
a
security
firm
reach
out
to
me
about
starting
to
open
cves
about
performance
problems
in
the
yards.
So.
B
B
B
D
B
C
Okay,
anyone
have
anything
else
on
that
topic.
Nope,
okay,
see,
we've
got
one
last
thing
here.
I
think
you
just
added
this
one
ben
windows,
permissions
issues.
B
Yeah
and
this
one's
a
kind
of
a
challenging
one,
because
someone
who's
made
some
really
good
contributions
to
node
feels
very
strongly
that
we're
overstepping
our
responsibility
in
in
rimraf
by
fixing
eprim
issues
on
windows.
As
we
try
to
delete
this
behavior
has
been
brought
over
from
rimroaf.
B
It's
been
in
rimrap
for
eight
years
and
I
believe
I'm
going
to
half
describe
the
problem,
because
I've
only
maybe
partially
understand
the
issue,
but
basically
certain
ways
one
might
create
files
makes
them
in
such
a
way
that
I
believe
it
has
to
do
with
the
it's
either
the
owner
or
the
file
setting
the
the
chmod
setting
on
the
on
the
folder.
B
But
you
basically
can
easily
create
a
you,
can
easily
create
a
folder
with
tools
like
git,
where
on
windows,
only
you
now
don't
have
permission
to
remove
it.
Unless
you
address
the
permission
issue
and
then
try
to
delete
it
so
rimra
for
many
years
has
kind
of
said.
Oh
you
have
this
specific
type
of
permission,
issue
I'll,
try
to
fix
this
permission
issue
and
then
I'll
try
to
delete
it,
and
this
hack
is
only
necessary
on
windows.
B
So,
what's
crummy
is,
if
you
were
to
remove
this
behavior,
that's
only
there
for
windows.
Suddenly,
node's
own
code
base
starts
leaving
to
get
folders
around,
as
if
I
understand
it,
so
it's
like
we
ourselves
run
into
this
bug.
I
know
I
would
run
into
this
bug
with
some
libraries
I
maintain
because
we
create
git
folders
for
unit
testing.
B
I'd
understand
the
argument
about
overstepping
your
bounds,
but
I
also
don't
want
to
the
whole
community
to
spend
the
next
10
years
on
stack
overflow
learning
about
windows,
permission
errors
for
their
unit
tests
and
having
to
fix
the
permission
error
in
an
extra
line
of
their
unit
tests.
For
so,
I
feel
pretty
strongly.
We
shouldn't
fix
the
issue,
but
I
feel
bad
to
take
the
stance,
because
I
understand
the
perspective
of
the
the
other
contributor
as
well.
C
So
I
mean
it
sounds
like
it
would
be
kind
of
a
big
step
back
at
least
on
windows,
if,
like
suddenly
no
longer
work
kind
of
the
way
you
would
expect
it
to,
especially
since
this
behavior
has
been
in
rimrap
for,
like
you
said,
like
eight
years
or
something
I
think
like
I
I
mean
you
can
only
modify
the
permissions
on
a
file
like
that,
if
your
own
permissions
allow
it
right.
So
it's
not
some
kind
of
like
privilege
escalation,
so
that
I
mean
that
does
seem
like
reasonable
behavior
to
me
personally,.
B
B
So
it
kind
of
comes
back
to
this
argument
of
you
know:
well-defined
standard
apis
versus
ergonomics
and
like
there's
advantages
to
standards
and
defining
things
well,
because
we
can
all
kind
of
write
things
to
the
same.
Spec
there's
also
an
advantage
to
ergonomics,
and
sometimes
the
two
things
are
are
at
odds
with
each
other.
D
D
C
One
isn't
that
I
mean
part
of,
like
you
know
the
rmrf
command.
Is
that
force
flag
right
to
me?
That
seems
like
the
kind
of
thing
that
true
you're
saying
you
want
by
by
using
that
kind
of
behavior.
You
know,
I
think
it
works
differently
on,
I
think,
on
unix,
it's
like
it'll
it'll
succeed.
Even
if
a
file
doesn't
exist,
I
think
that's
what
force
actually
does,
but
I
just
mean,
like
yeah
expectation,
wise.
C
B
I
just
I
wonder
if
we
should
try
politely
following
up
on
the
thread
one
more
time,
or
maybe
we
should
say,
would
it
make
sense?
Speaking
as
the
node
tooling
group
and
say
we
talked
about
this
today,
we
seem
to
come
we're
kind
of
all
in
agreement.
We'd
rather
have
the
permissive
behavior.
Would
he
be
open
to
working
with
us
documenting
this
properly,
rather
than
removing
the
behavior.
B
We
could
all,
I
feel,
like
that's
kind
of
that's
basically
saying
no,
and
it
might
be
better.
This
might
be
one
case
where
it's
kinder
to
just
say
no
right,
because
no
one,
like
I'm
just
trying
to
picture
the
world
where
you'd
set
that
option
and
it
feels
like
now,
we
just
have
an
extra
option.
No
one's
gonna
set.
C
C
B
I
mean
I
don't
I'm
worried
that
I
don't
use
windows
at
all,
so
the
like
the
the
one
place
I
use
windows.
Isn't
when
my
test,
suites
and
and
my
concern
is
we've
merged
this
and
then
suddenly
millions
of
people
have
weird
bugs
in
their
test
suites
and
we
end
up
rolling
this
back
in
two
months.
So
right,
yeah.
D
Rimmer
yeah
like
recursively
removed,
but.
C
C
So
I'm
probably
going
to
learn
a
whole
lot
about
windows
and
node
in
the
next
little.
While.
C
Oh
sorry,
we
got
a
lot
of
like
windows,
related
issues
and
create
react
cap
too
so
kind
of
figured.
It
wouldn't
hurt
to
have
a
windows
machine
around
because
yeah.
I
also
people
report
things
that
I'm
like
I
have.
I
don't
know
I
can't
reproduce
this.
I
I
can't
really
help
you.
You
know
so.
Anyways
probably
have
some
learnings
to
share.
B
B
A
I
mean
if
you
want
to
give
it
the
weekend
or
something
and
comment
early
next
week.
I
think
it
wouldn't
be
bad
to
just
pop
something
else
on
there
saying
that
we
discussed
it.
You
know
at
the
very
least
yeah.
C
C
B
Right
now,
I'm
hoping
to
stuck
I'm
hoping
this
turns
out
management's
hard.
So
it's
taking
a
lot
of
my
time,
but
I'm
excited
to
have
a
bit
more
open
source,
I'm
hoping
to
again
have
like
an
hour
of
open
source
blocked
out
each
week
and
just
kind
of
pick
a
pick,
a
task-
that's
most
valuable,
so
hoping
to
get
in
that
routine
again.
So
maybe
that
will
be
coffee
recursive.
It
seems
like
we
have
a
lot
of
folks
working
on
command
line
already,
so
I'd
be
willing
to
take.
A
A
Yeah
I'll
I'll
I'll,
just
on
that
note,
you
know
collab
summit
thoughts
are
still
kind
of
a
thing
as,
as
our
north
american
area
sort
of
opens
up
a
bit.
We
might
want
to
just
think
about
it
for
the
future,
and
you
know
whether
it's
can
you
can
you
explain
that.
A
Sorry,
just
nothing,
nothing
has
happened.
Nothing
has
changed
just
in
the
sense
of
like
I
know
people
are
talking
about,
you
know
getting
together
in
various
forms
or
whatever.
So
I
don't
know
just
kind
of
planting
the
seed
like
if
we
want
to.
A
I
would
love
for
a
larger
collab
summit
to
happen.
You
know,
maybe
it
wouldn't
happen
until
austin
summer
next
year,
which
is
the
next
open,
js
world
events,
but
you
know
if
we
see
any
opportunities
to
do
something
before
then
or
if
we're
all
at
the
same
event
or
whatever.
Let's,
let's
just,
I
guess,
keep
it
in
mind.
Just
planting
the
seeds.
C
Of
us
getting
together
at
least
you
know,
could
be,
it
sounds
like
it
was
like
july
5th,
or
something
they're,
getting
rid
of
the
quarantine
requirement
if
you're
vaccinated,
so
hopefully,
hopefully
that
helps.
D
I'll
be
in
canmore
in
a
week
and
a
bit.