►
From YouTube: 2021-11-12-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
A
A
A
I
think
we
had
a
brief
discussion
last
time,
but
I
think
in
the
end
it
was
just.
We
need
to
find
some
time
to
triage
this
issue
and
help
move
it
forward,
and
I
didn't
get
time
this
week
to
do
that.
So
I
don't.
I
don't
have
any
update.
I
don't
know
if
anybody
else
has
anything
else.
A
A
A
C
Yeah,
so
I
think
I
addressed
most
of
the
comments
minus
one
where
it's
like,
I
think
kevin
and
someone
else
suggested
to
use
a
symbol
to
sort
of
replace
that
magic
value.
Yep,
and
I
tried
with
that
implementation,
and
I
ran
into
some
issues
in
particular
like
when
I
create
that
symbol
and
because
I
I'm
using
like
symbol,
four,
which
basically
returns
a
new
symbol.
If,
like
the
description,
doesn't
exist,
we
turn
one
already
in
place.
C
But
the
thing
is
that
that
one
like
when
it
it
basically
like,
gets
the
global
object
and
then
gets
the
symbol
property
on
a
global
object
and
then
calls
the
function
on
an
object
to
basically
create
the
for
that
way.
But
the
issue
is
that
sometimes,
when
I
call
like
get,
it
will
throw
a
nappy
pending
exception,
and
so
when
I,
when
I'm
running
like,
for
example,
air
terminating
environment.js,
this
is
part
of
the
swallow
exceptions.
C
So
when
we
stop
so
when
we
swallow
exceptions,
this
will
still,
I
think,
bubble
up
and
so
crash.
I'm
not
sure
if
I'm
doing
anything
wrong
there
or
like
there's
something
we
can
do
about
that.
A
C
D
C
A
B
B
E
B
So
that
which
is
fine
but
that's
kind
of,
but
then
we
are
basically
saying
the
user
is
now
committed
to
only
using
nf
dot,
get
instance
data
instead
of
using
the
core
api
directly,
which
we
have
allowed
so
far.
A
B
A
B
A
B
Yeah
yeah,
I
think,
if
we
make,
if
we
make
the
property
like
not
visible
and
and
not
deletable,
then
that's
as
good
as
it
gets.
And
yes,
the
object
will
will
be
decorated
with
this
really
ugly,
looking
property,
but
it
is
what
it
is.
A
B
I
mean
we
can
make
this
even
more
unique
by
by
appending,
like
you
know
that
on
api
is
wrapped
object,
because
then
you
know
we're
name
spacing
it
in.
A
A
A
D
D
A
Sounds
good,
so
maybe
if
you
make
that
update
and
then
just
do
like
an
app
mention
for
the
people,
who've
been
involved,
so
we
get
a
notification
sure
we
might
get
that
automatically.
But
that
would
be
like
the
signal
like
okay,
let's
get
the
final
review
and
get
it
landed.
Okay,
cool.
C
A
Okay,
that's
good,
then
so
yeah,
so
basically
nothing
to
discuss
until
we
get
that
landed.
We'll
take
another
look
at
it.
So
that's
our
stale
issues
tracking
for
modules
that
are
ported
nothing
new
there.
Although
we
always
take
the
chance
to
know
the
add-ons.
G
Yeah,
it's
the
number
of
dawn
is
increased
because.
B
G
F
B
C
No,
but
I
just
want
to
curious
about
like
the
scope
of
this,
are
we
just?
Is
this
just
a
matrix
of
test
methods,
or
is
it
more
like
just
like
have
full
coverage
of
everything,
because
if
it's
a
matrix,
I
think
we
have
that
already
in
our
issues,
but
if
it's
sort
of
full
coverage
we
still
need
to
work
on
it.
A
Yeah,
maybe
we
should
we
should
rename
change
that
right,
because
definitely
it
sounds
like
so
what
I'd
be
interested
in
is?
A
Do
we
think
it
makes
sense
that,
like
we,
I
know
you've
done
a
bunch
of
work,
we
got
issues
opened,
we've
got
things
we
talked
about,
like
tagging
them
as
good.
First
issues
yeah.
I
wonder
if
we're
at
the
point
where,
like
trying
to
promote
that
a
little
bit,
we
could
write
a
little
blog
post,
which
is
like
hey.
A
A
A
E
A
G
I
don't
know
if
jack
is
in
the
team,
so
in
not
the
dawn,
api,
repo
and
so.
G
G
I
I
think
that
yeah
we
we
should
aim
to
the
active
members
yeah.
G
G
I
I
don't
know
the
the
how
these
things.
H
D
H
A
A
Is
like
pr
yourself
into
this
list
of
people,
and
you
know.
G
G
A
A
Access,
okay,
so
that
actually
should
add
you
to
both.
I
think
that
was
the
one
I
just
added
you
node
api
right,
so
that
should
give
you
access
right
access
to
both
of
the
the
the
two
repos.
If
you,
if
there
is
something
you
don't
have
access
to,
let
me
know
and
I'll
fix,
that
up
too
michael,
there
is
cabin.
J
Michael,
no,
unfortunately,
sorry,
I
didn't
have
a
much
chance
to
work
on
this
I'll
continue
to
work
on
work
with
great
beer
and
gabriel
and
close
this
before
the
next
meeting.
Okay
sounds
good:
okay,.
A
A
Okay,
so
let
us
go
back
to.
E
E
A
So
then,
we're
now
just
down
to
burning
down
issues
in
the
repo
themselves.
So
I
don't
know
if
there's
any
ones
that
people
want
to
call
out
for
us
to
start
with.
G
Yeah
we
have
two
new
issue:
yeah.
G
G
E
G
G
Seems
to
be
caused
by
the
number
of
the
functions,
so
more
larger
is
the
library
and
more.
I
is
overreach.
I
don't
know
if
it's.
G
It's
not
clear
to
me
if
he
did
the
same
thing
with
the
the
module
exporting
the
distinct
function
and
and
then
the
same.
The
same,
the
really
same
things
using
the
model
with
475
functions,.
A
G
So
because
maybe
a
with
the
model
with
the
distinct
function,
he
just
tried
to
do
something
and
he
saw
that.
Okay,
it
works,
and
now
it's
time
to
to
to
create
the
the
the
the
dawn
and
so.
G
This
is
not
clear
to
me
and
I.
A
F
A
G
B
The
the
only
thing
I
can
think
of
here
is
that
an
object
with
lots
of
properties
is,
is
slower
at
retrieving
a
given
property
than
an
object
with
few
properties,
because
you're
you're
retrieving
a
property
named
function,
name
from
an
object
named
export.
So
if
that
object
has
what
is
it
initially
13
functions,
then
it
may
have
to
traverse
a
smaller
list
to
find
the
function
by
its
name.
H
B
Assign
each
property
of
the
add-on
of
the
exports
object
to
a
local
variable
and
then
call
the
functions
using
that
local
variable,
rather
than
by
saying,
like
exports,
dot
function,
name
right,
because
then
there's
no
property
lookup
that
may
be
faster
for
them.
Okay.
So
what
is
it?
You
can
do
that
very
conveniently
in
javascript
you
can
just
deconstruct
the
the
object,
so
you
can
say,
like
you
know,
brace
function.
G
A
B
E
B
A
A
B
B
Well,
well,
if
it's,
if
it's
well,
no,
I
mean
anything.
Anything
can
be
plucked
from
the
exports
object
right
and
then
and
then
the
only
thing,
the
only
difference
is
you're
not
saying
like
exports,
dot,
blah
you're
saying
blah
directly,
and
that
should
be
fine
right.
Oh.
A
Yeah,
you
can
do
that,
but,
like
I'm
thinking
like
in
a
case
where
you
create
a
whole
bunch
of
objects,
so
say
you
have
a
thousand
different
objects,
each
of
which
you
know
you.
You
may
pass
to
different
paths
and
eventually,
when
that
object
gets
into
one
of
the
the
call
paths
you
want
to
then
call
one
of
the
methods
right.
B
Right,
but
there
is
only
one:
exports
object
right
like
if,
if
let's
say,
if,
let's
say
the
exports
object,
contains
a
constructor
for
a
class
right
because
that's
the
add-on
provides
a
javascript
class
right
and
that
construct
or
the
or
instances
of
that
constructor
have
475
methods.
Then
yeah,
then
you've
got
a
problem.
A
E
A
Because
yeah,
I
guess
I
could
see
that
maybe
yeah,
maybe
it's
just
the
pure
javascript
side
of
things
and
that
might
okay,
okay,
so
there
was
that
one
you
said,
and
then
there's
also
this
one.
A
We
can
hear
somebody's
background,
not
that
it's
bothering,
but.
A
B
A
B
A
A
E
G
The
next
is
nappy,
create
syntax
error,
and
now
we
have
the
power
request
on
the
node
core.
G
Yeah,
I
reviewed
something
and
it
seems
okay
for
me.
Yes,.
K
A
A
A
I
So
I
mean
what
I'm
reading
from
this
comment
is.
It
just
sounds
like
we
need
to
have
a
differentiation
between
progress,
events
and
signal
user
user,
initiated
signals
and
then
inside
there,
because
I
guess
we
have
some
null
pointer
checks
and
that's
because
signal
was
sending
null
pointer
as
the
data.
K
I
Yeah
and
yeah,
it
makes
sense
I
just
hopefully
I
can
have
some
time
to
work
on
this.
We
have
another.
I
have
another
company
event
next
week
for
the
whole
week,
so
I
don't
know
if
I'll
have
any
time,
but
if
I
do
I'll
try
to
work
on
this,
some.
E
I
I
A
Right
it
was
like
asking
to
make
it
constant,
unconstitutional,
yeah
yeah,
and
it
was
like,
I
think
we
discovered
we
didn't,
have
a
test
for
it
and
then
it
was
like
well
wait.
A
sec
yeah,
it
was
kind
of
like
we
signal
could
never
have
worked,
and
that's
like
okay.
Well,
that
means
yep.
We
don't
have
a
test.
So
that's
consistent
with
that.
I
Right
and
then,
since
he
then
made
signal
compilable
by
changing
it
to
non-const,
then
he
saw
that
signal
was
not
even
triggering
the
progress
call.
So
that's
what
this
issue
is
for
yeah
and
hopefully.
A
E
A
E
C
Sorry,
I
think
I
have
a
pr
up
for
that
for
the
inside
node
core,
that's
kind
of
I
think
as
a
ci
cam
feeling.
So
I'm
not
sure
what
else.
A
Like
time
I
mean
windows,
I
think
like
some
of
the
timeouts
and
that
kind
of
stuff.