►
From YouTube: 2021-10-08-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
So
welcome
to
the
node
api
team
meeting
for
october,
8th
2021
we'll
follow
our
standard
approach
of
looking
at
what
we
have
in
the
milestone
12..
So
let
me
get
there
before
I'm
doing
that.
Does
anybody
have
any
announcements
they'd
like
to
share.
A
Okay,
so
the
first
one
is
the
the
ask
for
review
of
node
serial
port,
so
I
think
kevin
and
nicola
you
both
been
looking
at
that.
So
I
don't
know
if
there's
an
update.
B
No,
I
haven't
looked
at
it
recently.
I
do
know
that
they
have
still
been
working
on
it,
though
I
do
see
some
updates
to
their
branches
that
they've
been
working
on.
Hopefully
I'll
have
some
time
this
weekend.
A
Okay,
then
we
can
move
on
to
the
next
one,
which
is
looking
on
stale
issues,
I'm
just
going
through
there
to
see
what
we've
got
so
we're
down
to
these
two.
C
D
A
D
D
E
A
D
It
only
happens
in
repo
yeah,
it's
when
you're
typing
and
the
variable
will
try
to
detect.
If
the
method
is
is
that
is
side
effect
3
so
that
it
can
invoke
it
and
show
the
previews
in
the
repo.
So
the
problem
only
occurs
in
repo,
so
we
don't
have
it
in
script
mode
or
any
other
mode.
We
run
in
production.
E
A
D
D
Yeah,
but
I
don't
remember,
their
script
has
any
let's
say,
disallowing
javascript
execution,
but
it
may
be
how,
since
any
javascript
function,
may
throw
so
typically
saying
that
I
don't
have
to
handle
the
have
to
handle
the
javascript
exceptions
properly.
So
they
won't,
they
won't
be
like
say,
leaking
leaking
resources
just
going
to
accept
those.
D
But
when,
but
since
the
problem
of
this
issue
is,
is
specifically
happens
in
the
dynamic
api,
so
I
believe
we
have
to
fix
it
in
modern
api.
A
D
Yeah
the
exception,
the
exception
is
what
we
are
talking
about
previously
about
the
throwing
primitives,
since
the
air
is
throwing
primitive,
throwing
a
low
strings
when
the
javascript
execution
is
disallowed,
so
that's
causing
the
crash.
E
D
A
Yeah,
I
think
I
think,
because
I
thought
my
understanding
was-
is
like
that's
what
jack
tried.
So
it's
like.
He
tried
running
with
the
changes
which
we
thought
would
fix
that,
but
anyway
sounds
like
we
should.
We
just
need
to
continue
to
look
at
that.
One
yeah,
okay
and
we
start
working
on.
So
that's
good,
keep
it
on
the
list
tracking
issue
for
modules
that
have
been
ported,
nothing
too
new
there.
I
think
this
was
yeah.
It
was
reported
last
time
if
we
just
look
at
say
npm,
no,
that
on
a
guy.
A
A
Yeah,
maybe
there's
a
new,
I
don't
know
if
these
are
ordered
in
terms
of
use
of
downloads.
Maybe
are
they.
C
A
It's
closer,
these
ones
at
the
top
are
do
seem
to
be
more.
The
higher
higher
numbers.
A
So,
okay,
anyway,
that's
it's
good.
Let's
go
back
here.
A
A
Okay
sounds
like
he
isn't
quite
back
yet
so,
let's
loop
back
to
that,
so
we
can
take
a
look
at
issues
in
the
repo.
A
A
Looks
like
it's
good
that
you
know
there's
some
discussion
back
and
forth.
That's
good.
A
Is
potentially
worth
looking
at,
I
know
it
was
reported
that
this
const
was
causing
signal
to
not
work,
but
I
wonder
if
we
have
concerns
removing
this
const.
B
B
A
D
D
A
Jump
from
two
to
three
tfsn.
A
B
E
B
D
A
I
think
that's
a
good,
that's
a
good
suggestion
like
so
in
the
pr
do
you
want
to
jump
in
there
and
suggest
that
we
should
make
this
one
constants
dead.
C
Kevin
the
pr
is
a
1086
yeah.
Sorry,
this
one
just
flipping
there.
E
A
A
This
one,
I
don't
know
like
I
I
answered,
but
I,
if
like
kevin,
you
might
have
a
sanity
check
in
that
I
think,
like
async
worker,
if
you
cue,
multiple
things
could
start
multiple
threads
depending
on
the
uv
thread,
loop
or
thread
pool.
B
A
D
D
D
It's
not
the
thursday
function.
If
I
don't
know,
okay.
B
C
In
a
sync
worker,
we
use
the
the
libya
v
thread
mode
and
it's
yeah.
We
we
have
this,
this
limitation
and
yeah
all
the
code.
All
of
the
work
that
we
create
of
in
the
execute
method
will
be
queued
if
you
run
more
than
three
three
tasks,
no
three.
C
This
is
what
I
I
I
I
know
yeah.
That
sounds.
C
Yeah
and-
and
maybe
we
could
document
this
on
the
documentation
for
async
worker.
B
B
E
C
If
I
will
remember
it's
a
native
dom
from
sub
or
or
even
say
our
port-
I
don't
remember
but
yeah.
If
you
create
a.
C
More
than
four
tasks
yeah
you,
you
will
be
cute
and
you
need
to
wait
that
other
thoughts
will
finish
and
in
in
this
case,
if
you
try
to
connect,
you
know
to
the
airport,
and
you
want
more
than
for
connection
yeah,
you
need
to
wait
for
the
the
release
of
the
the
previous
one
of
the
previous
connection.
C
So
this
was
the
discussion
that
I
I
I
I
remember.
A
I
do
agree
that
we
should
look
at
the
docs
and
maybe
you
know
explain
a
little
bit
more
how
it
works
in
the
interaction
with
that
uv
thread,
pool.
A
A
A
C
Yeah,
the
reporter
asked
us
about
the
trade-off
between
libya
vmworker
threads
because
yeah
they
have
the
limit
for
the
the
connection,
no
count
to
four
because
of
of
the
other
thread
of
or
probably
uv
so
yeah.
That
was
on
node
yeah
rfc.
F
Hey
yes,
I'm
here:
okay,.
A
Perfect
then,
we've
unless
there's
any
other
issues
that
people
think
we
should
discuss.
We
could
loop
back
to
the
the
work
you've
been
doing
on
the
test.
Suite.
F
Yeah,
if.
F
F
A
If
not
thanks
for
everybody's
time
and
we'll
see
everybody
in
github
and
next
week,.