►
From YouTube: Node.js Tooling Group Meeting
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).
B
Well,
my
window
says
it's
preparing
this
one
says
we're
live
so,
let's
that
we're
live
so
yeah,
hello.
Everyone
welcome
to
the.
B
October
1st
2021
yeah,
so
I
guess
let's,
let's
get
right
into
the
agenda,
I
can
find
it
here,
okay,
so
what
do
we
have
here?
First
on
the
agenda
is
alert.
End
users
features
that
are
added
to
node
core
when
using
a
package
shim
et
cetera.
I
think
we,
so
we
actually
we're
going
to
remove
that
from
the
agenda
that
I
I
was
initially
looking
at
that,
but
haven't
really
had
time
to
to
do
any
more
on
that
the
idea
there
is
just
you
know:
yeah.
B
Let
people
know,
for
example,
with
package
like
rimrock
or
something
that
we've
now
incorporated
into
node.
Let
them
know
they
maybe
don't
need
to
pull
that
dependency.
C
B
But
yeah
I
have
not
had
a
chance
to
make
any
progress
on
that
one.
D
B
Package
is
that
right,
yeah
we
were
gonna
rather
than
even
if
it's
built
with
eslint,
rather
than
adding
it
to
like
the
default
like
node.
Yes,
rules,
yeah,
we're
thinking.
Maybe
you
just
run
like
a
tool
to
kind
of
lint
or
check
your
project
for
those
kinds
of
things,
but
yeah.
No,
no
developments
on
that
one!
So
yeah,
let's
move
on
here
ben!
B
B
Yeah,
so
so
it
only
works
on
string
paths
right
now,
which
can
fail
for
can
fail
for
some
languages,
like
japanese
korean
chinese,
sometimes
we'll
have.
The
file
system
have
characters
that
don't
work
if
they're,
if
they're
a
bare
string
in
some
operating
systems,
which
is
why.
B
A
bunch
of
the
file
system
operators
were
extended
to
support
buffers
of
characters,
so,
unfortunately,
copy
is
a
little
more
complicated
than
a
lot
of
the
other
file
operations,
where
we
need
to
recursively
kind
of
perform
operations
where
we
like
walk
up
the
directory
structure,
walk
down
the
directory
structure
and
tldr,
because
the
path
helpers
in
node
don't
work
on
buffers.
B
I
guess
when
I
have
more
time,
I
will
try
to
finish
up
that
helper
library
and
then
my
only
concern
is
that,
like
it's
like
a
thousand
lines
of
code,
maybe
so
it's
like
yeah
like
it
introduces
a
little
complexity
to
node
and
I'm
like
at
some
point.
You
must
be
worried
about
the
size
of
the
bin
right.
So
I
don't
know
it's
probably
a
necessary
evil.
D
Challenge
to
review
as
well
is
that
a
part
of
the
I
see
in
the
issue
here
at
398?
It
looks
like
you
and
danielle
adams
are
working
on
the
ad
recursive
cp
method.
Is
that
what
you're
talking
about
or
is
it
something
different.
D
Yes
near
the
bottom
of
the
yeah,
all
the
linked
stuff
at
the
bottom.
D
B
And
james
snell
said
that
they
would
rather
like
they
basically
said
one
of
the
blockers
for
getting
to
stable
would
be.
If
we
can
that's
where
it's
landed,
one
of
the
blockers
would
be
getting
it
working
with
buffers
in
the
process.
I
read
through
rimraf
and
it's
a
it's
a
very
half
baked
buffer
implementation
and
I
think
that's
probably
true
of
a
bunch
of
file
operations
like
it
doesn't
actually
do
the
right
thing
in
some
cases,
so
I
don't
know,
guess
I
I
would.
B
C
B
B
B
D
B
Just
like
horrible
string
munching,
basically
that
this
ends
up
in
node
core,
like
I
see
you've,
got
it
in
your
own
repo
right
now,
but
I
did
it
outside
of
note
card
just
because
it
makes
my
iteration
faster,
because
I
don't
have
to
compile
the
code
to
test.
So
I'm
I'm
rating
it
just
my
intention
would
be
it
wouldn't
be
a
node,
and
I
realized
this
weekend
when
I
was
getting
ready
for
interviewing
someone
at
google
that
my
implementation
of
unicode,
my
my
implementation
of
utf
16,
is
off
too.
B
D
That's
funny,
let
me
ask
you,
since
it
isn't
your
own
repo,
but
the
hope
is
to
have
atlanta.
No
does
it
make
sense
to
do
like
we're
doing
with
parsegs
and
put
it
in
like
pkgjs
and
hack
on
it
there
and-
and
you
know,
test
it
there
and
get
people
looking
at
it
and
working
on
it
there
before
we
bring
it.
B
C
B
D
Yeah
darcy
or
wes,
you
know
or
michael
dawson
could
certainly
help
too,
but
I
think
darcy
got
the
the
parser
stuff
started.
D
B
That's
a
good
point
yeah.
I
think
it's
a
bigger
problem
than
I
think
it
will
take
me
for
realistically
a
month
or
two
or
a
few
months
to
get
this
work
done
because
I
just
realized.
I
didn't
realize
that
this
is
boring.
Utica
stuff,
I
didn't
realize
utf-16
was
a
variable
length
as
well.
I
thought
it
was
always
16
bits,
but
it's
actually,
I
think,
16
to
24
bits
or
something
so
you
can.
It
works
kind
of
like
utf-8.
I
think
where
you
can
have
like
a
controlled
character
that
adds
extra
bytes.
B
So
all
this
is
just
to
be
able
to
measure
the
length
of
a
path
is
all
I
want
to
do,
but
the
promise
you
need
to
like
completely
it's
it's.
You
know
what
I
mean.
First,
you
have
to
make
the
universe
before
you
can
make
a
cake,
basically
cool.
That's
I've
talked
way
too
much
about
that.
So,
let's
move
on.
B
I
think
that's
a
good
idea,
though
joe
I'll
maybe
do
the
do
the
work
somewhere
more
public,
okay,
okay,
next
on
the
agenda
here
we
have
source
map
v3
any
any
new
developments
there.
Just
looking
at
the
issue
here.
D
Yeah,
I'm
fine
with
it
too,
I'm
just
trying
to
scroll
through
and
see.
If
there's
anything
yeah
that's
been
open
for
a
while.
Is
that
why
we
had
it
open
just
to
see
if
anything
comes
up
with
it
or.
B
B
B
Okay
did
did
one
of
you
close
that
ticket
on
the
tooling
board,
so
it
doesn't
appear
again.
I
just
did
yeah
okay,
great
okay.
So
then
the
the
last
item
on
the
agenda
is
argument.
Parsing,
so
we've
got.
C
D
Yeah,
it's
great.
Thank
you,
jessica,
yeah
and,
as
I
mentioned
too,
you
know,
jessica
was
just
looking
at
the
examples
that
are
in
the
readme
and
you
know
trying
to
flesh
out
kind
of
the
minimal
implementation.
I
guess
to
start
to
fill
out
the
the
object
that
would
be
returned.
D
Yeah
so
there's
you
know
a
couple
of
spots
where
you
know
jess
and
I
reviewed
it
and
you
know
she's,
pretty
concise
with
the
getting
a
bunch
of
stuff
on
one
line
which
I
think
makes
sense.
But
if
anybody
has
any
objections
and
wants
to,
you
know,
break
it
up
and
then
also
there's
a
couple
of
spots
where
it's
feels
like
it's
repeating
a
little
bit.
But
I
don't
know
if
it's
time
to
optimize
that
yet
or
just
just
kind
of
let
it
roll
and
see
how
it
plays
out.
D
We
don't
need
to
go
through
it
all
right
now,
but
if,
but
if
you
all
want
to
take
a
look
and
just
see,
if
you
have
any,
you
know
improvements,
you
know
before
we
land
it
and
then
we
can
go
from
there
or
if
you
want
to
land
it,
and
you
can
go
from
there.
B
I
think
minor
minor
feedback
for
me
like
out
of
the
gate,
like
I'm
not
not
too
concerned
with
some
of
the
lines
being
long
I
mean.
Maybe
we
could
clean
that
up
a
bit,
but
I
think
the
I
think
would
be
worth
looking
at
how
node.js
approaches
their
errors
like
like
and
cleaning
up,
our
our
how
we
throw
and
just
making
our
errors
look
more
idiomatic
to
node.
So
there's
actually
a
separate
issue
for
that.
B
But
I
I
kind
of
agree
with
like
I
think
what
both
of
you
are
saying
that,
like
we
should
just
move
forward
with
this,
and
that,
like
shouldn't,
be
optimizing
it
right
now
we
shouldn't
worry
too
much
about
making
it
perfect.
You
know,
let's
just
keep
kind
of
iterating
on
it
and
we
can
improve
it
over
that.
D
Yeah
and
and
one
of
the
things
I
see
right
off
the
bat
which
is
no
fault
of
jessica's
or
or
anyone
else's
is.
We
should
probably
get
some
like
style
checking
in
there
and
just
make
sure
that
we're
all
sort
of
aligned
on
the
node.js
style
and
spacing
and
all
that
stuff.
B
There
is
also
an
issue
for
that
which
I
think
I
was
supposed
to
do
so
there
were.
I
think
there
were
two
things
I
was
going
to
do,
which
was
like
code
coverage
and
linting.
So
maybe
I
can
take
a
look
at
that
this
weekend.
Actually,
I've
got
a
little
bit
more
time
at
the
moment,
been
a
little
busy
with
the
new
version
of
create
react
app,
but
we're
very
close
to
having
that
done
so
yeah.
I
might
have
a
bit
of
time
to
work
on
those
things.
B
My
ask
would
be
my
plate.
Ask
because
I
have
no
authority
that
we,
like
you
say,
would
be
if
we
could
get
an
eslinter
in
that
literally
enforces
the
same
coding
guidelines
as
the
node
code
base.
That'd
be
great,
because
I
would
use
that
in
my
I'd
use
that
in
my
path,
library
as
well
and
then
and
then
we
can
just
like
when
we
do
pull
them
into
node.js,
we
already
have
the
exact
formatting
that
we
that
we
need
and
we
just
plop
it
in
yeah.
B
That's
exactly
exactly
what
I
was
thinking
as
well,
since
that's
where
it's
you
know
heading.
I
guess
maybe
that's
not
an
easy
thing
to
do,
or
maybe
that's
not
like
well
packaged
up
or
something
to
use
in
other
projects.
B
I've
always
like
thought
about
doing
it
and
never
done
it,
because
it's
just
it's
probably
not
that
hard.
I've
just
never
tried
doing
it
like.
I
think
the
way
the
lyncher
runs
is
a
little
weird
in
node.js.
It's
it's
fendered.
I
think
in
a
like
a
depths
folder
right,
but
I
it
probably
just
runs
eslint
config,
like
any
other
eslinter.
So.
D
C
D
Not
it's,
I'm
not
sure.
I
have
to
look
at
it
again
because
there
are
a
few
things
like
error
handling
and
everything
like
I
was
like.
Oh,
but
then
I
looked
and
was
like,
oh
okay,
but
we
should
definitely
look
at
it
and
see
how
we
can
make
sure
we're
aligned
so
that
you
know
the
goal
is
to
move
it
over
there
and
have
it
as
frictionless
as
possible.
Even.
B
If
it's
as
close
as
possible,
like
you
know
to
the
node
style,
without
going
too
far
into
making
it
identical,
that
would
probably
be
a
big
help.
Yeah
yeah!
That's
that's
what
I
feel
about
errors
as
well
like
like
they
should
look
like
node
errors,
but
let's
not
try
to
use
that
like
errors.js
pattern
until
we
actually
integrate
into
node.js
because,
like
we
don't
want
to
like
pull
that
file
over
right,
I
think
yeah.
D
Yeah
that
that
being
said,
though,
I
was
hoping
to
influence
node.js
errors
and
start
to
use
the
whoops
comments.
So.
B
B
D
D
You
know
80
20
kind
of
implementation
and
help
us
out
there.
B
That
would
be
a
good
addition
to
the
package
like
the
the
package.org.
D
B
B
Not
to
I
put
a
tiny
bit
of
new
business
on
there,
which
is
kind
of
basically
rin
raf,
isn't
isn't
working
on
like
some
linuxes
there's
two
issues
open
about
it.
Oh
is
this
you
and
I
talked
about
one
of
these
issues
last
time.
Didn't
we
yeah?
Is
this
a
different
one?
B
No
well,
there's
two
that
are
essentially
the
same:
oh
yeah,
that
was
not
closing
file
handles
or
something
right.
D
D
So
this
is
august
23rd
and
I
don't
know
he
hasn't
come
back.
B
But
here's
the
other
one
too,
oh
yeah
before
and
I
haven't
looked
at
this
one
for
a
little
while
but
yeah
looks
like
he's
still
or
they're,
still
not
being.
B
B
Does
it
help
build
a
community?
No?
I
was
reading
through
before,
and
I
remember
thinking
to
myself
that
you
were
being
very
patient
and
yeah.
D
B
But
it's
a
real
issue,
which
was
why
I
haven't
closed
it.
Should
I
it's
annoying
because
it's
a
real
issue,
but
it's
also
probably
should
be
shut
down
by
comms.
So
I
don't
know
what
the
best
approach
is
there,
but
interesting?
Okay!
Well,
that's
anyways!
That's
interesting!
That
there's
a
second
kind
of
related
issue,
though.
B
I'm
having
this
issue
at
work,
a
little
bit
right
now
too,
where
unrelated
to
tooling
right
we're
having
some
like
a
few
bugs
related
to
http
2
and
I've
been
encouraging
my
colleague
to
like
contribute
to
node
if
they
want
to,
if
like,
if
we're
seeing
these
issues
with
http
2.
But
yeah
he's
like
why
I
haven't
even
seen
it
triaged
in
two
months,
like
that's
a
fair
point,
but
like
little
words
for
the
more
gnarly
parts
of
the
node.js
codebase,
maybe
are
suffering
from
a
not
a
ton
of
contribution.
Right
now,.
D
Yeah,
do
you
know
ben
or
have
you
forgive
me,
I'm
not
sure
if
you're
on
the
tc
or
tsc
or
or
what
but
have
issues
been
being
triaged,
I
know
girish
was
was
spitting
up
like
a
triage
group
and
it
seemed
like
there
were
a
couple
people
who
joined
it
seemed
like
issues
in
general,
getting
triaged
or
just
gnarly
ones
that
are
kind
of
getting
overlooked.
B
D
B
And
I
mean
I
work
for
a
large
company
like
like
it's
like
on
my
side.
I
can
try
to
nudge
people
towards
working
on
it
right.
That's
one
thing
I
can
do
because
it's
an
open
source
code
base
yep.
So
I
don't
want
to
like
this.
Isn't
a
critique
of
node,
it's
more
of
a
do.
We
need
to
find
ways
to
get
more
resources
on
parts
of
the
system
right,
but
it's
definitely
outside
of
our
arch,
our
charters,
so.
B
D
Yeah,
it's
interesting
to
think
about,
though,
if
we
could
figure
out.
I
mean
you
know
not
just
this
group,
but
the
larger
group,
how
to
really
kind
of
surface
some
areas
that
we
could
really
use,
help
in
and
make
it
sound
kind
of
fun
and
exciting
and
and
reach
the
people
that
we
think
you
know
would
find
it
fun
and
exciting.
I
don't
know
it's
always
a
constant
challenge.
B
What
I
saw
with
with
with
my
colleague
is,
I
think,
as
the
outside
looking
in
there's
this
assumption
that
there's
an
expert
in
that
part
of
the
system-
and
maybe
they
don't
want
to
contribute
a
patch
because
maybe
it's
intended
behavior
or
maybe
it's
just
that
the
triage
hasn't
happened
yet
or
something
along
those
lines,
and
I
don't
think
that's
always
the
case.
B
I
think
I
think
patches
are
appreciated,
so
it's
like
yeah
for
sure,
just
figuring
out
that
community
figuring
out
how
to
communicate
that,
like
I'm
feeling
the
same
way
about
this,
like
these,
some
of
these
file
system
bugs,
like
I
don't
think,
they'll
be
fixed
unless
we
get
some
eyeballs
on
them
and
like
find
a
way
to
carve
out
time
that
a
lot
of
us
don't
have
to
actually
do
it
so
yeah,
I
don't
know
no
solution.
Just
maybe
I
need
to
start
attending
some
more
meetings
too.
B
Really
this
stuff.
That
used
to
be
like,
I
feel
like
our
collaborator
summit,
which
would
probably
be
a
good
venue
for
this
this
this
kind
of
conversation
yeah.
I
don't
know,
hopefully
that
stuff
is
back
soon.
I
don't
know
if
there's
is
there
a
plan
for
like
any
kind
of
like
node
interactive,
like
virtual
conference,
this.
D
Winter,
I
don't
know
of
one
I
mean
typically
node
conf
was
the
the
you
know
the
off
season
or,
however,
you
can
phrase
it
but
node
interactive
and
the
node
conf,
and
I
don't
think
that
you
know
they're
doing
remote
again,
no
conf,
I'm
on
the
open,
js
world
planning
committee
and
so
we're
working
on
that
already
it's
going
to
be
in
austin
and
in
the
summer
june
or
july
camera
which-
and
I
think
the
expectation
is
that
you
know
we
would
have
space
to
do
a
collaborator
summit
there.
B
December,
it's
before
summer
could
be
nice,
though,
like
maybe
we
could
plan
for
like
first
quarter
or
something
yeah
yeah
or
that
yeah.
Hopefully,
if
it's
virtual,
it's
not
as
much
of
a
challenge
to
plan
with
the
collaboration
which
we
used
to
do
that
was
really
good.
Was
invite
a
few
experts
who
weren't
necessarily
always
collaborators
but
could
maybe
bring
a
perspective
to
that
part
of
the
system.
So
so
maybe
I
could
like
nudge,
my
colleague
having
a
sheepy
two
issues
to
come
to
the
summit
and
and
talk
about
it.
That
would
be
valuable.
D
B
D
You
no,
no,
I
guess
you
know
we'll
just
look
at
jessica's
open
pr
and
try
to
land
that
soon
and
and
then
kind
of
iterate
from
there
see
what
is
kind
of
left
in
terms
of
the
features
that
we
wanted
to
have
implemented.
But
also
do
these
other
related
things
like
linting
and
and
and
whatnot.
B
Yeah,
I'm
happy
for,
like
my
comments
to
just
be
follow-up
work
like
jessica.
Would
you
be
interested
in
doing
with
the
like
the
eslant
and
the
errors?
Follow-Up
work
like?
What's
what's
your
plan
for
how
involved
do
you
want
to
be
going
forward
on
this.
C
I'd
like
to
take
on
a
few
minutes,
I
could,
I
guess,
just
make
the
changes
that
jordan
suggested
I'll
hold
off
a
day
or
two
just
to
see
if
anyone
throws
anything
in
otherwise
I'll
deliver.
We
can
always
put
the
comments
later
and
I
can
look
into
the
eslint
to
try
and
get
it.
I
guess
like
node.js,
but
I'll,
see
how
complicated
there
is
otherwise
I'll.
Just
try
and
do
like
is
get
it
as
close
as
possible.
D
Yeah-
and
I
can
you
know
the
three
of
us
me
and
you
and
and
and
our
friend,
kai
from
eslint,
we
could
take
a
look
at
it
together
too
and
see
you
know
he
could
maybe
help
point
us
in
the
right
direction
and
get
us
over
any
humps
there.
D
What
I
was
gonna
ask,
though,
is
I'm
not
exactly
sure,
but
I'm
under
the
impression
that
yeah
we're
still
not
like
feature
complete
in
terms
of
what
we
want
to
see
with
parsogs,
but
I'd
have
to
take
a
look
and
and
make
sure
that
we're
kind
of
fleshing
that
out
further,
which
may
also
be
a
good
way
for
jessica
to
continue
if
she
wants
to
keep
doing
that
specific
work
that
she's
already
gotten
familiar
with.
D
So
maybe
once
we
land
it,
we
can
see
what
we're
lacking
and
start
to
make
sure
that
we
have
that
documented
and
we
can
implement
those
features
as
well.
Maybe
even
build
up
the
test
first
and
go
from
there.
D
C
I
I
think
it
was
honestly
the
only
thing
that
was
remaining
well.
I
honestly,
I
haven't
read
the
full,
like
all
the
features,
but
I
think
I
covered
most
everything
else.
Okay,.
D
Yeah,
I
mean,
I
guess
the
examples
here
in
the
readme
aren't
very
long.
So
if
that's
all
covered,
then
that's
awesome
and
we
should
just
see
if
there's
we
can
discuss
further.
If
there's
more
that
we
expected
of
this.
C
B
D
Yeah
and
with
your
experience
with
with
the
args
and
everything
you
know,
if
you
yeah
see
what
you
think
of
the
implementation
and
if
it's
feature
complete
or
what
we
would
want
to
add
to
it
or
what
not
that'd
be
great.
B
D
B
Awesome:
okay,
all
right,
yeah!
Well,
thanks!
Everyone
yeah
have
a
good
weekend.
I'll
talk
to
you
later.