►
From YouTube: 2021-09-24-Node.js Node-API Team 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).
A
Welcome
to
the
node.js
node
api
team
meeting
for
september
24th
2021.
today
we're
going
to
follow
our
standard
approach
of
looking
at
the
issues
that
are
tagged
for
milestone
11..
Does
anybody
have
any
announcements
they'd
like
to
share?
First.
A
Okay,
hopefully
everybody
can
see
that
so
the
first
one
is
the
review
of
node
serial
port.
I
don't
think
there's
any
update
on
that
and-
and
we
don't
have
well-
I
guess
nick-
do
you
have
any
update
on
that?
One.
B
A
Okay,
that's
great
thanks
for
continuing
to
work
on
that.
The
next
issue
is
the
issue
with
issues
that
were
marked
stable,
so
the
first
one
here,
that's
still
active,
is
930.
A
B
Sir,
go
ahead
yeah!
I
I
won't
just
take
a
look
in
the
weekend.
If
you
can
give
me
this
time
and
yeah,
and
if
I
cannot
see
anything
to
to
to
stop
you
can't
land,
okay,
I'll,
wait
till
next
week,
then.
A
Okay,
great
thanks,
then
there
is
pull
request,
exactly
a
thousand
which
I
added
in
this
one
legenda
cast
opened.
Oh
no,
sorry
look
I
just
think
for
some
reason.
I
forget
what
I
thought
somebody
opened
it
basically
there's
a
crash
in
the
rebel.
A
It
looks
related
to
this
fatal
error,
although
I'm
not
sure
if
it's
like
well
yeah
like
it
looks
to
this
we're
getting
this
this
error
when
we
try
and
create
the
reference,
so
I'm
wondering
if
that'll
actually
be
related
to
the
one
that
you
know
jack,
did
the
change
in
core
and
has
been
looking
a
little
bit
at
in.
B
A
A
A
A
So
I
think
that,
basically,
if
we
go
to.
B
16
and
14
version
for
node.
Is
it
right.
B
Because
now
we
can
create
a
roar
from
stream.
Is
it
we
can
throw
the
exception.
A
I
don't
know
jack.
If
you
remember
the
the
node
core,
the
pr
pre.
D
Isn't
no
core
three
nine
nine
two
six.
C
D
A
How
about
that
sounds
good
yeah
if
you
could
give
it
a
run
and
see
what
happens.
That
would
be
great
okay,
okay,
so
that
was
the
only
other
stale
issue.
B
The
code
reported
by
in
these
in
this
issue,
we
we
we
could
use
this
code
to
test
the
work
that
jack
r.
He
is.
B
Oh
okay,
so
these
up,
and
only
when
yeah
on.
B
It's
happened
if
you
yeah
in
repl
and
and
if
you
use
the
code,
so
he
import
these
on
on
the
script
it
works
or
not.
A
The
you
know
this
seems
to
be
like
we're
failing
to
create
the
error,
and
so
maybe
we'll
actually
see
the
air,
and
then
we
can
go
back
to
the
you
know.
Why
does
that
actually
fail?
In
the
first
place
right.
C
A
A
Oh
looks
like
things
are
still
trending
up:
it's
yeah
4.7
million
per
week.
That's
yeah,
okay,
so
still
still
going
up,
which
is
good
right.
I
haven't
enabled
debug
sort
of
on
my
very
back
burner
create
matrix
of
tested
methods
so
jack.
Do
you
have
things
we
should
talk
about
on
that
front?.
D
So,
basically,
like
all
the
like,
I've
documented
everything
for
now
yeah
get
up
I'll,
get
up
issues,
and
for
that
actually
I
was
wondering
if
it's
okay
for
me
to
like,
I
guess,
advertise
this
repo
to
some
of
my
friends
because,
like
I
think
some
other
interesting
game
too,
like
I
guess
contributing
stuff
and
like
I
wonder
if
I
can
get
them
to
write
some
tests,
they're
interested
absolutely.
A
B
Yeah,
I
I
won't
suggest
these
so
jack.
B
We
we
can
mark
all
the
issues
that
now
are
marked
like
test
as
tests
with
with
good
good
first
issue
and
maybe
yeah
we
can
post
on
twitter
and
maybe
to
our
friends,
hey.
We
have
a
lot
of
good
first
issue
and
we,
if
you
want
to
contribute
to
know
that
on
api,
go
okay.
B
So
if
it's
good
for
you,
I
can
do
this.
B
There's
plenty
of
them
so
yeah.
I
want
to
know
the
issue
on
which
you
are
working
on
now
so
yeah.
We
cannot
create,
I
won't
about
to
create
overlap
so
for
because
I
I
think
that
you
are
working
on
some
of
test
cases
now.
Is
it
right.
D
Yeah,
I
I
think
I
just
pro
for
a
while.
I
they
got
to
this.
One
has
like
some
worse
conflicts.
That's
resolved,
but
I
couldn't
really
get
around
to
this
week
but
yeah.
I
have
like
this
one
should
cover
all
the
tests
for
the
function.
Reference
class.
B
Okay,
yeah,
okay,
so
you
you
already
have
the
pr
yeah
yeah,
okay,
okay!
Thank
you.
D
Not
for
testing,
but
for
the
for,
like
that
pr
for
wrapping
objects.
Oh
sorry,
I
wonder
what
we
should
do
about
like
the
like
those
sort
of
overloads,
and
I
got
I
remember
you
brought
up
about
like
the
values
and
returning
values
versus
objects.
D
D
A
D
But
yeah
cause
like
air
already,
like
I
think,
inherits
from
reference,
which
is
a
template
class
right.
So
I
feel
like
if
we
do
another
template,
that's
gonna
be
very
messy.
A
D
Yeah
because
yeah,
I
didn't
really
change
anything
from
the
it's
about
the
javascript
throughout
javascript
reception.
A
D
D
Yeah
sorry,
this
one,
I
think,
just
returns
like
the
unwrapped
value
wrapped
in
an
object
just
because
it
like
sort
of
because
this
just
follows
the
convention,
because
error
is
inherited
from
a
reference
object,
a
reference
templating
object.
So,
like
I
guess,
if
people
are
requesting
a
value
about
a
function
on
the
error
object,
I
feel
like
they
probably
expect
an
object
back
like
this
format.
This
is
value
right
and
then.
A
D
Yeah,
but
I
think,
if
for
the
just
case
for
like
error
handling,
I
think
nappy
throw
just
treats
object
as
like
just
like
just
like
a
value,
I
think
it
track
extracts
it
and
like
throws
it
like.
That's
like
the
primitive
type.
A
D
A
A
A
Maybe
that's
value.
A
A
A
It
might
be
yeah,
so
actually
maybe
getting
the
the
type
is
just
fine,
so
I
think
that's
fine
there
may
be
some
other
subtleties
like
you've
now
got
an
object
that
isn't
really
an
object
internally.
So
if
you
set
like
you
tried
to
set
a
property
on
it
or
something
it
might
not
work,
but
that's
possibly
okay,
so
I
think
okay,
so,
okay,
after
after
discussing.
A
A
A
D
A
A
Finding
the
scale
there
we
go
promote
okay,
so
yeah.
I
think
that
was
all
my
questions.
You
know
if,
after
that,
other
than
that
I
didn't
have
anything
if
other
people
can
take
a
look
too
to
comment.
That'd
be
great.
A
Okay,
any
other
ones,
jack
that
you
want
to
bring
up.
A
Okay,
so
now
that
we
have
d-pack,
do
you
did
you
have
some
things
that
you
thought
wanted
to
talk
to
us
about
this
week?.
E
That's
the
first
one
is
the
pr
enable
yeah.
Let
me
go,
let
me
shine
my
screen
and
sure
yeah,
okay,.
E
I'll
go
over
a
list
of
features
that
I
have
right
and
then
go
through
the
files.
Right
probably,
I
think
it
would
be
much
better
if
I
demo
it
first
and
then
go
over
the
files
all
right,
so
I
have
introduced
a
wildcard.
Such
one
and
options
to
you
know
include
multiple
options,
filter
options.
So
let's
see
what
what
we
have
here.
E
Under
the
unit
test,
you
know
we
have
all
these
files
and
each
one
of
those
is
for
a
specific
reason.
Match
modules
actually
is
for
matching
the
wild
cards,
so
we
can
give
wild
cards
like
this
right.
We,
we
don't
have
to
type
the
entire
of
our
file
names.
We
can
type
you
know
like
with
star
in
between,
so
that
it
would
match
with
the
wild
cards
and
give
us
back.
E
The
rest
of
the
you
know
match
with
so
async
star
with
match,
with
everything
that
starts
starts
with
a
star
right,
and
we
can
also
give
folder
names
right.
We
can
give
a
complete
folder
name
in
the
test,
folder
like
global
object
or
threads
function.
E
So
if
we
give
a
wildcard
that
matches
a
folder,
it
would
only
select
the
folder
name
right
and
then,
if,
if,
if
we
have
a
something
that
matches
a
file,
a
specific
file
within
the
folder,
only
then
only
that
would
match
like,
for
example,
type
star
extra
would
match
only
this
file
here,
because
it
has
ex
right
and
typed
in
it.
This
is
the
only
file
entire
touch
directory.
That
has
so,
it
would
only
you
know,
use
that.
A
E
Yeah,
it
will
just
so
yeah,
so
maybe
yeah
so
under
the
unit
test.
There's
also
list
modules
that
I
have
right
list
of
test
modules.
So
whenever
this
file
gets
loaded
right,
yeah
it
it
goes
over
the
list
of
files
that
are
there
and
it
automatically
creates
a
binding.
You
know
sort
of
configurations
and
everything
necessary
right,
so
we
don't
have
to.
We
can
keep
adding
files
as
long
as
they
add
to
a
particular
like
the
case
there's
a
certain
protocol.
E
We
want
to
want
the
test
files
to
follow.
Like
the
you
know,
the
snake
case
right
yeah.
We
want
all
of
them
to
follow
the
snake
case
that
we
already
have
like
underscore
right
yeah.
If
they
follow
the
snake
case,
it's
easier
and
not
just
follow.
The
snake
is,
but
also
have
the
you
know
the
exported
unit
function.
That
is
the
that
is
a
you
know.
E
That
is
a
camel
case,
yeah
that
is
specific
or
that
the
capital
first
letter
capital
k,
format
all
right
of
the
corresponding
format
for
the
snake
case
right.
Okay,
so
that
we
can
convert
between
both
of
them
yeah
yeah.
So
so
that,
and
and
until
we
follow
that,
that's
good,
if,
for
suppose,
we
are
not
able
to
follow,
we
can
always.
I
have
added
a
file
exceptions.js.
E
These
are.
There
are
certain
files
which
don't
follow
that
and
probably
like.
It's
also
valid
in
some
cases
like
async
worker.
Persistent
is
a
you
know,
it's
a
file
which
has
a
internet
object,
persistent
ac
worker
right
and
it
it
seems
good,
because
the
reason
we
have
async
worker
persistent
is
because
we
want
to
follow.
You
know
we
can
want
to
have
grouped
together
all
the
async.
You
know
together,
so
asic
underscore
worker
underscore
no
callback.
I
think
underscore
worker
underscore
persistent,
so
all
of
them
are
grouped
together
here.
E
E
Is
not
a
proper
name?
If
you
would
suggest
that
in
the
review,
then
I
would
change
it,
and
also
there
are
cases
where
we
want
to
skip
the
skip,
adding
a
file,
because
some
of
the
files
don't
have
init
object
at
all
right
right.
E
Yeah
so
we'll
just
skip
binding
them
into
the
binding,
so
those
are
the
things
I
have
added,
but.
A
E
Yeah,
sorry,
I
should
have
mentioned
that
so
so
for
every
file.
I
I
have
also
made
it
sure
that
you
know
so
that
if
something
goes
wrong
immediately,
somebody
can
you
know,
don't
have
to
put
console.logs
on
anything.
We
can
just
verify
by
putting
ourselves
conditions
here
and
the
file
test
cases
would
be
fired
for
because
these
are
already
within
the
test
infrastructure.
We
don't
have
to
write
separate
test
files
for
this,
so
what
I've
did
is.
E
I
have
added
this
way
of
testing
it
like
if
we
run
try
to
run
the
file
with
a
node
command
directly
from
the
terminal.
Only
then
like
this
make
sure
that
this
fire
is
right.
There
right.
A
E
A
E
Yeah
so
look
at
the
wifi
and
then,
if
you
want
to
run
an
entire
directory,
we
can
specify
the
darker
name,
like
thread:
save
function,
right
thread,
okay,
if
underscore
function
right
and
then
that
would
select
all
the
files
within
the
directory.
E
E
Still
want
to
be,
you
know
just
shorter
than
that.
I
can
push
thread
star
right
and
it
would
choose
with
wild
cards.
It
would
match
everything
within
the
threadsif,
because
the
wildcard
matched
of
entire
folder
right
thread
safe,
so
it
just
matched
everything
within
that
folder
right,
okay,
and
if
you
some
sometimes
if,
along
with
that,
we
have
a
thread
safe,
underscore
dot
cc
something
over
here.
You
don't
choose
that
because
it
matched
with
a
directory
already,
so
it
just
prioritizes
the
directory
and
runs
for
the
directory
alone.
E
Like
avoid
this,
the
running
I
put
an
iphone's
condition
for
that,
but
I
think
yeah,
that's
a
maybe
that's
not
required.
Maybe
if
that's
a
you
know
yeah,
I
did
it
because
if
you
look
at
the
threads
function
underscore
function
within
that
we
have
all
of
them,
starting
with
right
side
function
so
trying
to
match
on
the
top
of
the
folder
and
then
trying
to
go
inside
it
again
was.
Would
it
would
be
unnecessary?
E
That's
why
I
put
that
condition,
but
the
side
effect
of
that
is
that
if
we
put
a
form
a
file,
a
function
file
here
with
the
same
right,
yeah
it
wouldn't
match,
but
with
the
wild
card
it
should
match
right.
Ideally,
that's.
C
E
That's
true
yeah.
I
think
let
me
see
how
to
work
around
that
and
then,
if
I
put
the
star
in
before
it
matches
both
let's
say
function
and
type
typed
thread
say
function
right.
It
did
both,
it
would
run.
So
let
me
like
probably
this
will
take
a
little
longer.
I
can
stop
this
and
run
with
yeah,
something
else
like
say.
If
I
I
want
to
run
with
multiple
conditions,
I
can
space
space,
delimit
them
like
this
right.
Once
again,
let
me
choose
one
of
them
async
or
guessing
star.
E
I
want
everything
that
starts
with
async
and
I
also
want
to
have
object
track
I
can
at
with
and
without
wild
cards
as
well.
So
I
want
everything
that
starts
with
async
and
specific
the
object
wrap.
So
it
just
shows
everything
that
starts
starts
with
acing,
and
then
I
press
the
object
file.
E
So
this
is
space
delimited
here,
yeah
and
you
know,
with
codes
on
either
side.
A
E
There's
something
wrong
over
there,
but
most
of
the
other
files
ran.
I
guess,
but
I'll
take
a
look
at
it.
So
sometimes
some
of
the
files
are
like,
I
think,
having
a
export
like
I
have.
I
think
I
have
to
add
to
the
exceptions.js.
E
There
are
some
exports
that
I
don't
have
you
know
the
the
exported
property
name
is
different
from
what
we
expect
normally.
C
E
Yeah,
so
so
that's
all
right,
but
we
can.
We
can
keep
adding
stuff
like
that.
You
know
we
can
add
function.
E
Yeah,
we
can
give
any
number
of
arguments
there
100
match.
The
only
challenge
I
faced
right
now
is
that
the
linting
errors,
when
I
do
a
lint
linting
check
it,
it
is
also
checking
for
other
files.
Basically,
the
lint
fix
and
the
npm
run
link
both
are
trying
to
point
out
to
files
that
are
not
part
of
this
pr
that
are
already
there
in
the
code
base.
A
Yeah,
that's
that's
the
strange
part
in
that
it
should
only
do
things
which
are
like
that
are
basically
change
between
your
pr
and
the
so
like.
Can
you
just
show
that
and
show
the
linting
reports,
because
that's
something
we
just
landed
and
I
you
know
there
may
be
some
issues
with
that.
We
need
to
fix
up
yeah
this.
This
part,
okay,
so
that,
if
you,
if
you
right
here
so
now,
have
you
do
you
have
a
like?
Can
you
update
your
main
branch.
A
A
E
A
E
E
A
Well,
that
all
looks
good
and
if
everybody
can
take
a
look
and
it'll
be
great
to
get
that
landed
because
it
looks,
looks
cool,
okay,.
A
E
A
Me
go
back
to
here,
okay,
so
that
then
I
guess
we
will
be
back
to
just
looking
at
if
there's
any
issues
that
people
think
we
should
talk
about
in
the
repose.
A
The
other
thing
jack
you
might
mention
like
other
good
first
issues,
is
like
we've.
Now
that
we've
put
the
the
linter
in
place,
we've
got
a
bunch
of
files
which
don't
match
it,
and
every
time
somebody
goes
to
change
a
file.
They're
gonna
have
to
fix
up
more
stuff
than
just
what
they're
changing.
D
A
D
A
Sure
so
I
don't
see
anything
else
too
new
there
or
here
right.
This
issue
is
kind
of
where
we're
discussing
that
one
right.
We
can
list
out
files
where
that
you
know
we've
done
it
or
not
done
it.
A
So
don't
see
anything
there.
Let's
take
a
quick
flip
over
to
node.
A
So
I
don't
see
anything
too
new
on
that
front
either
so
and
unless
there's
anything
else
that
anybody
wants
to
bring
up
to
discuss,
we
may
be
finished.