►
From YouTube: Node.js Tooling Group Meeting 2021-04-16
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).
A
B
All
right
here
I
can
jump
in
this-
is
a
meeting
of
the
node.js
tooling
working
group
live
on
youtube
as
if
you
would
like
to
get
involved,
you
can
find
us
on
github.com
node.js
tooling,
and
we
basically
work
on
features
around
tooling,
related
stuff,
which
is
a
broad
topic.
It
can
be
test
related,
can
be
file
system
operations,
but
essentially
things
that
end
up
being
command
line
operations
generally.
B
Personally,
this
isn't
on
the
agenda,
but
I'll
throw
it
into
this
announcement.
B
A
little
while
ago
we
landed
the
crypto
random
uid
in
node.js,
so
that
you
can
create
a
v4
uid
in
node
and
james
snell
was
basing
this
somewhat
on
the
spec.
I've
been
working
on,
but
it's
getting
pretty
good
momentum
now
and
we
just
landed
in
chromium
behind
a
flag.
So
I'm
excited
about
that.
So.
B
C
B
B
Yeah,
that's
good.
I
should
put
that
in
the
argument
I'm
having
about
whether
or
not
it's
necessary
to
be
a
one-line
method
like
it's
only
20
lines
of
code.
Why
don't
you
just
copy
that
20
lines
of
code
everywhere?
I
think
it's
not.
Everyone
knows
that
20
lines
of
code
and
it's
and
if
you
screw
it
up,
you
can
have
colliding
euids,
which
is
bad
for
for
you.
So
that's
my
argument.
B
C
Package
on
npm
that
we
use,
like
I
said
like
in
pretty
much
every
single
service.
B
So
this
is
a
hammer
we
can.
I
understand
this
process
better
now
this
is
a
hammer
we
can
occasionally
use.
If
we
see
something
that
we
think
is
so
universally
useful
to
tooling
we'd
like
it
to
be
in
both
node
and
the
web
context,
we
can
occasionally
work
through
working
groups
and
and
try
to
get
it
up
leveled
even
into
like
w3c.
B
A
I
don't
think
anything
has
happened
here.
Am
I
on
mute?
No,
I'm
not.
Okay,
good.
I
pings.
I
think
chris
about
this,
and
I
think
I
even
asked
michael
about
it.
Oh
somebody
said
ben.
Maybe
while
we're
here,
can
you
look
and
see
if
you
you're
not
listed
as
a
maintainer,
but
you
may
have
access,
I
don't
know.
B
A
Yeah,
I
will
ping
michael
in
this
issue
here
in
the
comments
and
ask
if
he
can
make
a
couple
of
folks,
maintainers
ben
roy
ian.
B
B
C
To
the
repo
access,
but
it
does
not
look
like
I
can
do
anything
with
the
team.
Okay,.
B
D
I
was
just
gonna
say
there
is
like
a
unspecified
set
of
maintainers
on
on
here,
so
it
looks
like
tierney
and
mateo
could
also
support
us
on
this.
Oh
really
yeah.
So
it's
like,
if
you
actually
sort
by
role
for
maintainer,
it's
it's
via
it's
not
just
chris,
actually,
based
on
the
access
and
permission.
A
All
right,
let
me
let
me
I'll
just
ping
tyranny
before
creating
well,
I
can.
I
can
ask
tierney
or
michael
to
to
make
you
two
maintainers
or
u3
or
ben
roy
and
ian
sure.
B
D
Again
I'll
specify,
I
would
like
to
be
opted
out
of
that
responsibility,
because
eventually
somebody
will
ask
to
update
that
list,
and
I
can
pleasantly
say
that
I
don't
have
accidents
sounds
good.
B
A
A
D
So
what
was
was
the
time
we
I
I
personally
was
there
suggested
time
other
than
I.
A
Think
I
think,
because
you
and
roy
had
something
moved
so
maybe
you
were
open
at
1pm
eastern
time
I
don't
know,
I
make
sure
I'm
clear
about
what
time
zone
you're
in
we.
D
Yeah
yeah,
I
I
dictate
roy's
schedule.
Most
often
you
can
speak
up
and
say
otherwise.
Other
than
you
know
lunchtime
is
usually
blocked
out
around
noon
for
us,
and
that
would
be,
I
think,
nine
nine
a.m
for
you,
folks,
so
yeah,
if
you're,
okay,
with
10
a.m,
on
the
pacific
time,
that
would
be
one
p.m.
Eastern
time
for
us
would
totally
work.
I
think.
A
B
A
C
Oh,
that's
me
no
update
for
me
for
this.
I
was
mentioning
before
the
call
that
the
last
few
weeks
have
been
a
bit
chaotic
for
me
with
some
flooding
in
my
condo
and
being
out
out
of
here
for
some
some
time
so
yeah
I've
just
been
scrambling
to
get
caught
up
at
work.
So
no
real
progress
on
this.
For
me
right
now,.
B
No
worries
what
I
was
gonna
suggest
was.
I
would
happily
pair
with
this
on
you
and
I'm
like,
I
feel
like
I'm,
reaching
a
stopping
point
on
my
random
uid
stuff.
Hopefully
I
think.
B
They
said
that
he
implemented
most
of
it
for
fs
extra,
so
I
think
here's
the
thing
like
just
for
in
terms
of
code
providence
like
if
I
would-
rather
it's
not
build
this
thing
from
scratch,
because
I
think
it's
a
complicated
problem
yeah,
but
I
I
usually
like
to
have
the
buy
in
and
have
talked
with
someone
before
we
just
lift
code,
even
if
it
is
mit
licensed
like
just.
B
I
think
it's
nicer
to
get
them
involved
in
the
implementation
so
yeah,
I
agree,
yeah
see
if
we
can
reach
out
to
manny
and
so
that's
kind
of
an
action
item.
I
can
take
that
on
if
you're
still
dealing
with
insurance
and
stuff
ian.
B
Good
cool.
B
B
C
Yeah,
I
think
that's
better,
even
if
even
if
you
can
help
me
kind
of
get
the
recursive
copy
stuff
kicked
off,
maybe
and
then
maybe
it'll
free
you
up
after
that
sounds
good.
C
B
Basically,
we
backported
a
change
that
shouldn't
affect
c
plus
plus
at
all,
and
it
started
triggering
tons
of
testason
issues,
which
I
think
tests
for
memory
leaks.
Basically,
access
outside
of
appropriate
memory.
B
B
B
I
commented
on
the
sanitizer
issue
to
see
if
mary
had
no,
I
think
it's
just
that
everyone
is
really
busy
and
I
haven't
gotten
feedback
from
anyone
on
whether
we
can
land
without
testis
as
asin
running.
So
what
does
this
mean?
We
have
source
map,
support
in
node,
12
and
node
14
already
it
just
isn't
the
stable
version
that
we
landed
on
in
node,
15
and
6.
What
will
be
16
so.
C
So
does
that
mean
in
node
14
it's
the
version
where
we
get
like
the
interleaved
source
or
stack
traces
rather.
B
B
B
D
I
was
just
topping
up
on
what
joe
sent,
which
is
like
the
release.
Repo
has
at
least
a
schedule
for
14x
releases,
so
I'm
not
sure
if
that's
all
of
them
roy
would
actually
should
know
this.
B
I'm
at
the
point
of
just
needing
to
make
people
to
see
if
I
have
approval
to
land
without
that.
If
I
thought
that's
passing.
E
B
B
A
Yeah,
I
mary,
I
think
was
you
know,
had
stuff
going
on
and
wasn't
available
for
yeah.
D
A
Of
time-
and
I
think
that
they're
back
now
so
maybe
or
something
yeah.
B
Maybe
give
them
another
king
or
give
I'll
give
richard
lau
another
ping
as
well
and
yeah
one
more
go
and
see
if
we
can
get
anyone,
because
the
problem
is
I
like,
it
doesn't
happen
when
I
build
on,
I
even
built
on
linux
as
well,
just
to
see
if
it's
like
a
linux
specific
issue,
and
I
just
have
not
managed
to
throw
the
same
errors.
B
I
think
test
essence
is
supposed
to,
in
theory,
be
testing
memory
leaks
in
c.
So
it's
but
like
our
javascript
code
can
exercise
c
code
paths,
so
it
can
cause
like
appropriately
be
flagged,
but
I
think
usually
your
expectation
would
be.
You
did
something
weird
in
c
plus
and
this
catches
it
so
not
sure,
what's
happening
to
us
right
argument.
Parsing
is
the
next
agenda
item.
A
Yeah,
I
saw
your
comments
ben
earlier
today,
so
I
need
to
spend
some
time
with
those.
Where
are
they
just
this
other
screen
here
is.
C
That
on
that,
first
pr
that
you
put
up.
A
Yeah
I'll
drop
a
link
in
the
chat
here
and
yeah
it
was.
It
was
a
very
simple
kind
of
start.
I
was
looking
through
chris's
code
and
pulling
some
stuff
over
that
implemented,
some
of
the
things
that
are
in
the
design
dock
there
and
yeah.
I
just
opened
this
pr
to
show
people
where
I
was
and
the
things
that
I
was
doing
so.
If
I
was
kind
of
on
the
wrong
path,
we
could
make
adjustments
got.
C
It
I
was
gonna
say
I
actually
approved
that
pr,
because
my
thoughts
were
like.
Let's
just
merge
this,
and
then
we
can
all
start
iterating
on
it.
That
might
be
more
efficient
than
I
haven't.
Haven't
looked
at
ben's
comments
here,
though,
but.
B
Mine
are
mostly
recommendations
and
it's
like
for
like
linting,
because
I
hate
ever
having
a
code
review
talk
about
whether
I
need
a
semicolon
or
not.
Yep
just
make
that
automatic,
and
I
suggested
test
coverage
because
I
think
that's
important
for
command
line
argument
parser,
because
we'll
otherwise
we'll
catch
parts
of
the
parser
we
haven't
actually
exercised.
B
So
those
don't
need
to
those
don't
need
to
land
in
that
pr
or
they
could
they're.
Probably
like
two
minutes,
yeah.
C
Yeah
great
but
yeah,
like
I
said,
I'm
kind
of
in
favor
of
like
let's
just
merge
it
and
just
start
chipping
away
at
it.
A
That's
that
sounds
good,
and
I,
I
think
what
you
mentioned
ben
makes
sense.
I
can
add
the
test
coverage
and
and
the
linting
and
then
maybe
capture
some
of
these
things
like,
like.
I
think
you
already
got
one
of
them
in
an
issue
and
just
make
sure
we're
kind
of
going
through
and
getting
things.
B
A
I
agree
I'll
let
darcy
chime
in
if
you
have
more,
but
I
I
think
sure
we
should.
We
should
implement
short
codes.
D
Yeah
so
like
the
idea,
there
is
just
that
shorts
can
only
be
a
single
character.
I
think
that's
the
like.
That's
the
rule
that
we
have
to
enforce,
and
we
it
hasn't
in
that
initial
document
or
readme
that
we
put
together.
I
don't
think
that
that
was
explicitly
outlined
and
what
that
means.
What
that
means
in
terms
of
also
the
how
that's
configured
is
is
interesting
then,
because
like
do,
we
then
throw
if
you
try
to
provide
a
short
option
or
alias.
D
A
D
Yeah,
so
so
the
shorts
then
in
the
spec
that
was
written,
could
actually
become
aliases,
maybe
sure
whatever
the
terminology
is
I'm
not
so
well.
It's
just
a
way
to
essentially
combine
it
and
say
that
these
two
things
are
the
same.
So
if
you've
said
with
value
foo
and
there's
a
short,
and
you
expect
that
the
dash
f
is
actually
supposed
to
map
to
foo,
then
you
could
create.
D
Then
we
should
maybe
define
in
the
spec
and
then
the
option
and
and
support
in
the
options
for
you
to
say,
alias,
f
tofu,
so
that
when
those
two
things
are
are
seen
together,
they
won't,
they
don't
aren't
individually,
understood
they're
they're
clobber,
they
clobber
each
other.
A
B
A
B
A
Maybe
I'll
just
make
a
quick
issue
to
add,
you
know:
are
they
called
short
codes?
What
are
the?
What
are
they
called?
It's
like
I've
called
them
a
short
option.
Group.
A
Short,
ops,
yeah,
okay,
I'll,
create
an
issue
to
add
short
ops
to
the
design,
doc
and-
and
you
know
I'll-
try
to
implement
that
soon
as
well.
C
C
It's
probably
a
lot
easier
to
discuss
this
kind
of
thing
like
if
someone
does
put
up
a
pr
for
it,
and
then
we
have
something
concrete
to
talk
about.
D
So,
just
to
reiterate
here,
though,
we
did,
I
did
have
short
options
like
configurable
in
the
initial
like
draft
of
that
or
the
initial
the
secondary
draft.
It's
just
that
the
what
we're
talking
about
now
in
this
original
sort
of
draft
of
that
spec.
D
It
would
be
possible
to
essentially
have
multiple
character
shorts,
which
wouldn't
make
sense
for
the
what
we're
talking
about,
which
is
like
combining
allowing
for
like
combined
shorts,
so
so
before
you
could
have
done
dash
rf
and
that
could
be
associated
with
like
the
option
or
argument
like
recursive
force
dash
force
right,
like
it
wasn't
separate,
separated
right.
So
I
think
it's
it
this
strategy.
What
we're
talking
about
right
now
makes
a
lot
of
sense.
It's
just
like
shorts
should
always
be
single
characters.
D
The
way
that
you
would
map
a
short
to
another
like
argument
or
another
option,
would
be
to
change
to
create
some
sort
of
like
ability
to
define
aliases.
D
B
Yeah-
and
I
think
like
that's
what
I'm
advocating
is
that
that
dash
f
would
be
well,
I
think,
dash
f
would
work
in
isolation,
but
dash
foo
would
not
work
like
dash.
Foo
would
not
set
the
variable
foo
to
something.
That's
what
I'm
saying.
I
think
it
would
make
more
sense
for
dash
foo
to
be
f-o-o
or
something
I
think
we
can
talk
about
it
in
an
issue
too.
D
B
Yeah
in
practice,
I
don't
think
you're
usually
going
to
have
a
right
hand,
value
for
shorts
like
like.
I
don't
think
I
can't
think
of
something
where
you'd
be
like
dash.
Rf
equals
some
file
name
or
something
because,
like
like
that's
weird
like
usually
it's
like
shorts,
are
usually
like
a
bunch
of
boolean
flakes
where
you're
like
saying
turn
on
these
four
things.
While
I
do
a
git
command
or
turn
on
these
three
things,
while
I
do
a
curl
command
or
something.
D
Yeah
there's
a
couple
options
that
we
can
noodle
on,
but
yeah
there's,
that's
one
option
is
that
the
what's
returned
also
has
a
shorts
array,
but
I
think
that's
it's
like
obviously,
then
tougher,
because
you're
gonna
have
to
still
like
put
those
two
things
together.
A
B
We
could
start
there.
I
I
just
might
still
not
allow
single
dash
arguments
just
so
you're
open
to
doing
it's
just
so
you
haven't
created
an
ambiguity.
If
you
decide
you
want
to
do
multi-character
shorts
in
the
future,
so
I
would
just
like
skip
that
feature
for
now,
which
I
think
wasn't
mentioned
in
the
readme.
D
So
yeah
we're
gonna,
get
pushed
we're
gonna
get
pushed
back
by
an
individual
that,
I
think,
doesn't
see
the
value
here.
What
which
is
true
or
not-
and
we
don't
have
to
be
subservient
to
a
single
opinion
but
doesn't
see
the
value
if
we
we
don't
go
a
little
bit
further
and
have
a
little
bit
more
opinions
in
our
argument.
Parser
yeah.
B
Well,
I'm
thinking
like,
I
think,
it's
a
kind
of
a
bug
in
the
argument
parser
for
maybe
we
just
need
to
update
the
fact
too,
because
I
don't
think
it
jumped
out
at
me
in
the
faq
that
we
were
doing
single
dash
or
I
missed,
whichever
one
it
was
here.
I'm
looking
for
one
specific
line
in
here.
Okay
is
stash
food,
the
same
as
dash
dash
food.
The
answer
is
yes,
I
feel
like
I
would
expect
a
lot
of
people
would
expect.
Let
me
edit
that
this
is
from
the
faq.
B
I
feel
like
a
lot
of
people
would
expect
that
to
be
like
dash,
f,
o
o
or
dash
f
o,
if,
if
it
was,
if
it
was
an
option
group-
and
I
don't
know
like,
we
don't
have
to
support
option
groups
out
of
the
gate,
but
I
don't
see
why
someone
can't
just
type
double
dash
foo
like
to
me
like
it's
real,
it's
it's
pretty
common,
that
a
command
line
argument.
Parser,
won't
support
dash
foo.
B
A
A
The
second
to
last
faq
is
dash
dash
dash
triple
dash
foo
the
same
as
double
dash.
No,
but
but
would
you
would
someone
really
want
that
triple
dash
food
to
be
parsed
as
dash
foo.
D
But
it's
like
a
mistake.
It's
kind
of
that.
The
problem
is,
this
is,
would
protect
you
against
make
a
mistake
or
for
us
to
infer
what
you
meant
by
right.
A
D
That's
why
it's
a
no
in
that
case
and
then
it
should
probably
be
a
no
then
as
as
ben's
saying,
then
we
should
also
just
like
not
support
short
ops
for
now.
So
what
what
that
would
then
mean
is
like
well,
what
do
we
do
when
we
see
that
like?
Do
we
just
throw
it
out?
Do
we
not
parse
it?
Do
we
not
give
it
back?
Does
it
become
a
positional?
I
think
we
have
to
have
an
opinion
on
that.
One
way.
D
Yeah,
so
I
would
actually,
I
was
gonna
say
like
we
should
actually
try
our
best
to
support
than
short
ops
in
a
way,
but
just
right
now
the
design
doesn't
seem
to
like
lend
itself.
Well
to
that,
because
I
think
we're
kind
of
all
agreeing
they
should
only
be
single
character.
Like
that's
an
opinion
we
can
make
or
agree
or
disagree
on
that
they
only
should
be
one
characters.
So
now
it's
about
like
how
do
I
map
or
how
do
I
define
that?
D
That's
that
these
are
supported
so
that
we
can
get
them
back
in
one
of
the
three,
and
maybe
we
need
to
expand
how
many
return
values
are
there
are
but,
like
I
feel
like,
we
could
probably
find
a
way
to
get
short
ops
mapping
back
to
either
args
values
or
positionals,
which
are
the
three
return
values.
So
it's
all
about
just
yeah.
B
Well,
yeah,
so
I
think
what
I'm
advocating
in
the
short
term
is
is
just
like
drop
the
dash
foo
support.
Then
we
are
open
to
extensibility
in
the
future
and
we
don't
have
like
an
ambi
and
a
big.
U
it
doesn't
it's
not
a
nightmare
where
we're
like
we've
told
people
dash
foo,
will
parse
and
then
oh
shoot.
Everyone
want
a
dash
rf
and
we
can't
do
it
yeah
right
yeah.
So
I
think
that
just
success
yeah.
D
Just
like
ian
said,
like
joe
like
feel
free
to,
I
think,
merge
this,
and
we
can
continue
to
develop
it.
I
I
would
love
to
take
a
snap
at
just
like.
Maybe
what
that
design
looks
like
again
for
shorts,
then
to
to
try
to
clean
that
up
and
I'll
make
an
issue,
maybe
just
to
keep
this
conversation
going
for
for
short
ups
that'd.
B
D
A
So
I'm
gonna
make
a
note
to
myself
I'll
I'll,
add
the
linting
and
the
test
coverage
stuff
and-
and
I
may
address
the
eating
the
dashes
bit
and
and
then
I'll
I'll.
You
know
ping
you
guys
and
look
to
merge
it
soon.
A
Cool
cool!
This
is
awesome
great!
Yes,
it's
it's
not
a
lot
yet,
but
as
long
as
I'm
in
the
right
direction,
and
then
people
can
hack
on
it
with
me,
that'd
be
great
cool
cool.
B
D
C
The
indici
people
are
ethan
arrowood,
I
think,
is
working
on
a
fetch
implementation
built
on
top
of
adichie,
oh
great,
and
so
this
is
like
unblocked
work.
That's
just
happening
now
it
I
don't
know.
If
I'd
say
it's
unblocked,
but
it's
it's
things
are
happening.
A
Sorry,
oh
yeah,
so
I
talked
to
ethan
a
week
or
two
ago.
I
don't
think
this
undieci
wait.
No,
he
has
a
f.
Is
this
new?
A
I
think
that
he
actually
is
not
going
to
work
on
this
and
is
going
to
focus
more
on
doing
it
in
dc.
If
I
remember
correctly,
I
have
some
notes
somewhere,
but
I,
if
we're
talking
about
fetch
and
sorry,
I
got
distracted
by
a
text
message
for
a
second
there.
A
I
talked
to
james
and
he
actually
gave
a
presentation
on
an
event
a
couple
weeks
ago
that
I
was
involved
in
and
it
sounds
like
and
correct
me
if
somebody
knows
better
than
what
I
have
here,
but
you
know
james
is
pretty
focused
on
getting
fetch
done
and
trying
to
actually
get
it
done
this
year
and
trying
to
get
maybe
near
form
to
even
sponsor
some
folks
to
work
on
it,
and
you
know
likely
doing
it
in
mdc
and
you
know,
there's
a
lot
of
underlying
work
that
needs
to
happen
and
that
he's
kind
of
focused
on
that
first
and
then
you
know
what
the
hopes
that
that
fetch
can
be
kind
of
layered.
B
B
A
C
A
Yeah,
I
think,
if
I'm
reading
my
notes
correctly
ethan
said
he's
gonna
go
back
to
the
drawing
board
in
terms
of
what
he
did
in
the
umichi
fetch.
So
I
think,
like
that
specifically
is,
is
not
something
that
that
he's
going
to
continue
building
on,
but
that
they're
working
on
it
folks
are
working
on
it.
B
D
B
C
Anyways
yeah
speaking
of
evolving
things,
so
I
was
actually
reading
a
node
book
recently
try
to
find
some
good
books
like
for
my
team
and
stuff
on
like
typescript
and
node
and
yeah.
I
was
reading
like
a
new
notebook
and
the
guy
was
using
the
make
derp
package.
C
C
A
One
other
thought
on
that:
I'm
good
friends
with
kai
one
of
the
lead
folks
on
eslint
and
he's
talked
about,
like
figuring
out
ways
to
contribute
more
to
node.
So
that
could
be
a
way
to
sort
of
bridge
the
gap.
If
we
wanted
to
do
some
stuff
with
eslint
and
if
he
could
get
involved
with
us
and
we
could
work
together.
B
I
think
that's
a
really
good
idea,
because
that's
worked
really
well
for
tc39,
where
they've
asked
people
from
babel
to
join,
so
that
babel
can
track
the
new
features
that
are
coming
into
the
language
yeah.
So
I
mean
there's
a
good
precedent
for
that
like
having
someone
who
for
like
from
eslint
who
could
help
us
make
sure
we
communicate
changes
to
the
platform
out
to
the
community
would
be
brilliant.
A
Yeah
yeah
so
I'll
talk
to
kai,
it's
funny
that
you
mentioned
babble
and
kai's
a
part
of
babel
as
well,
but
henry
and
kai
I
used
to
manage
both
of
them
at
adobe,
so
oh
cool,
yeah
and
they're
both
they're,
both
kind
of
I
want
to
say
junior
or
new
or
something,
but
they
were
kind
of
yeah.
They
were
they're
fresh
back
then,
and
it's
great
to
see
how
far
both
of
them
have
come.
They're
really
now
they're
jaded.
A
D
Because,
like
the
other
option,
here
is
like
actually
just
to
be
throwing
that
warning
or
potentially
adding
that
to
derp
itself
since
there's
an
established
relationship
with
us,
potentially
yeah,
unless
the
mapping
isn't
like
100
like
the
future
set,
that
was
copied
over,
isn't
100.
That
might
be
a
reason.
Why
not
to
do
that?
But.
C
B
C
In
really
yeah
there
was,
there
was
yeah.
I
can't
remember
if
it
was
make
drip
or
something
else
where
we
actually
asked
about
this
like
hey,
would
you
be
willing
to
print
like
a
deprecation
warning,
and
I
again
I
don't
know
if
it
was
him
or
a
different
package.
C
C
Oh
sorry,
I'm
just
going
to
say
that
yes,
one
thing
is
maybe
another
option
I
mean
the
nice
thing
there
right
is
that
it's
like
we'll
be
adding
a
rule.
That
does
that
you
don't
have
to
use
that
rule.
You
know,
I
think,
maybe
arguing
to
get
that
rule
added
to
the
default
rule
set
might
be
another
matter,
but
I
think
just
you
know
giving
the
option
doesn't
seem
that
objectionable
to
me.
B
I
agree
I
think
darcy
brings
up
a
fair
point
that
we
should
be
cognizant
of
people's
feelings.
While
we
do
it,
though,
so
we're
not
like
someone's
like.
D
It
does
feel
like
subverting
like
the
package
maintainer
or
like
superseding
like
their
their
interests,
whereas,
like
I
totally
understand
if
we
think
that
that's
like
a
code
smell
and
that's
like
a
recommendation,
we
want
to
be
making
is
like
stop
using
this
and
and
then
iceland
or
those
there's
like.
I
don't
know
what
kind
of
plug-in
that
would
be
create
eslint
plug-in
to
like
enforce
that
rule.
But
I
I
think
that
also
like
working
with
the
maintainer
to
say,
hey
like.
I
think
this
is
a
better
option.
D
It
sounds
like
I
I
if
I
remember
correctly-
and
this
is,
I
think,
maybe
a
couple
years
back
now-
the
discussion
with
isaac
was
actually
pretty
productive
and,
and
we
were
able
to
copy
maker
pretty
much
very
closely.
B
That
was
rim,
raff
and
isaac
was
super
productive
yeah,
I
think
victor
was
sub
stack,
so
I'm
guessing
maybe
handed
some
of
his
dependencies
over
to
isaac
at
some
point
as
it
might
be
what
happened
and
I
like,
where
you're
coming
from
darcy.
I
just
wonder
if
maybe
the
thing
to
do
is
to
reach
out
to
like
a
maintainer
like
isaac
and
see
if
they'd
be
willing
to
opt
into
the
eslint
rule
and
then
never
never
add
an
eslint
rule
that
directs
people
away
from
a
package.
D
Yeah
it's
just
like,
then
you
require
like
the
projects
using
eslint
right
so
like
it
doesn't.
I
don't
know
if
you
get
the
same
impact
like
yeah
versus
like
a
post,
install
script
that
could
be
running
to
check
your
like
node
for
the
node
version
and
say
hey
like
this.
Node
version
actually
supports
it's
like
a
defecation
warning,
almost
like
that,
like
like
there's
now
this
other
way
of
using
this
kind
of
tooling
like
you
should
use
the
native
like
you,
don't
need
us
like
a
post
and
soft
script.
D
Almost
would
be
perfect
for
that
right.
Like
a
warning
printing,
a
warning
like
that.
C
B
B
I'd
happily
add
a
suggestion
to
yarg's
parser
that
you
just
use
node's
built
built-in
one
but
well.
I
think.
D
B
Yeah,
I
guess
at
the
end
of
the
meeting.
Okay,
you
know
what
I've
been
like.
I've
been
working
way
too
much
on
yard
17.
Over
the
last
six
months
like
it's,
I
decided
I
wanted
to
solve
the
asynchronous
behavior
problem,
which
turned
out
to
just
be
a
rabbit
hole
of
hundreds
of
issues.
So
I've
been
like
just
cranking
on
it.
Oh
wow
yeah,
but
I
think
it's
gonna
work
really
well.
I've
been
I've
been
reached.
Every
fact
I
I
was
looking
at
the
code
and
it
was
so
hideous
I
refactored
into
a
class.
B
A
That
could
be
a
good,
you
know
when
you
break
them,
you
can
just
say
just
use
the
the
art
parts
or
the
parsers
from
exactly.
B
You're
gonna
have
this
problem.
If
you
weren't
taking
it
all
right
all
right.
Well,
I'm
excited
to
be
back
in
this.
I
guess
we
can
end
the
regular
scheduled
meeting
there
and
I'm
excited
to
be
back
in
the
swing
of
things
and
it
sounds
like
we
have
some
fun
stuff
in
the
works.
So
I'll
see
everyone
in
two
weeks
yep,
if
someone's
watching
on
you,
I
was
gonna
say
if
everyone
anyone's
watching
on
youtube
feel
free
to
join
the
actual
meeting.
A
Yeah
we
had
a
couple,
people
say
hello,
at
least
so
that's
nice.
What
else
was
I
going
to
say?
I
don't
remember
so
it
doesn't
matter
cool,
see,
y'all
on
slack,
see
you
next
time.