►
From YouTube: 2021-06-18-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
B
Yes,
we
released
the
restaurant
400
api,
so
yeah
dropping
the
support
for
node
10,
because
it's
out
of
mountains
and
yeah.
This
is
my
announcement.
A
Okay,
great
now,
that's
thank
you
for
doing
that
release.
Anybody
else
have
any
other
announcements.
A
C
A
A
A
Okay,
I
look
at
npm
node
add-on
api.
A
D
A
Complete
because
this
is
quite
a
while
ago,
so
I
don't
think
there's
anything
new
to
discuss
on
that
front.
A
Actually
am
I
looking?
Maybe
I'm
not
looking
at
the
right
label.
So
let
me
there
we
go
okay,
so
we've
gone
through
that
one
after
that
one,
I
know
I
haven't,
enabled
the
debug's
debugger.
So
I
guess
now
we're
on
to
just
talking
about.
Are
there
any
issues
in
either
the
repos
that
we
should
talk
about?
E
I
guess
there's
one
for
these
issues
here
on
no
doubt
on
api.
The
most
recent
issue
and
it's
basically
the
examples
that
we
have
for
object,
wrap
are
not
instant,
are
not
context
sensitive.
E
So
if
people
are
taking,
you
know
just
copying
pasting
from
the
examples,
they're
not
context
sensitive
and
the
api
that
we
added
for
context
sensitivity.
I
guess,
is
the
node,
I
guess.
If
you
scroll
down,
I
said
when
it
was
added
six,
so
I
don't
know
if
that
like.
If
we
can
use
like
how
should
we
modify
our
examples
to
be
context
sensitive
so.
A
E
A
E
Okay,
so
that's
why
I
left
that
issue
open,
so
I
can
work
on
updating
the
examples
for
that
as
well.
E
E
So
this
was
a
closed
issue,
but
what's
happening
a
lot
of
times
is
people
are
asking
how
to
use
how
to
store
multiple
constructors
on
the
instance
data,
because
you
know,
if
you
use
set
instance
data,
it
basically
clears
out
what
was
there
already
yep.
So
I'm
wondering
if
it
would
be
beneficial
to
add
some
sort
of
helper
method
to
node
add-on
api
that,
because,
if
you
scroll
down,
I
put
a
little
code
block
here
as
well
a
little
further.
E
E
Yes,
that's
the
example
to
use
it,
but
a
little
further
up
in
the
same
comment.
I
created
these
sort
of
simple
template
functions
right,
use
an
object,
reference
on
the
right
instance
data,
and
then
you
can
attach
multiple
things
there.
I
don't
know
if
that
would
be
been
like.
I
have
there's
been
three
or
four
people
different
issues
that
I've
written
that
I've
been
asking
about.
This.
D
E
A
E
E
Okay,
so
then
I'll
work
on
making
this
making
an
example
with
this
and
then
there's
another
pr
that
I
have
on.
I
guess
that
finishes
this
conversation.
A
Man,
okay,
so
we
were
just
looking
at
issues,
but
if
you
so,
if
you
have
another
one,
then
let's
move
to
that
one.
E
It
was
on
the
node
add-on
examples
issue
for
because
I
guess
you
closed
out
the.
I
guess,
there's
a
pr
for
this
one
here,
this
one
yeah
and
it
was
to
add
the
type
thread
say
function.
It's
failing
now.
It's
the
first
latest
one,
sorry.
E
I
guess
it's
failing
now,
because
that
was
to
show
the
failure
for
the
gcc
bug
that
we
had
right
now
that
you
closed
it
I'll
finish
this
one
up,
so
that
it
can
be
merged
into
the
examples.
E
So
hopefully
right
this
one
and
then
the
new
one
with
the
instance
data
coming.
E
C
A
A
D
C
So
it's
very
simple
change:
we're
just
making
the
default
value
to
be
zero
instead
of
one
when
there
is
anything
unpredictable
exceptions,
it's
not
javascript's
exceptions,
but
it
may
be,
let's
say.
C
When
the
let's
say
when
the
reference
it
goes
down
to,
let's
go
down
from
zero
to
negative
one,
then
the
another
core
will
complain
about
it
and
the
united
states
will
be
returned.
So
in
that
case
we
retaining
a
one
and
a
default
value
would
cause
confusion,
since
the
actual
value
will
be
zero,
since
it's
we
are
going
to
decrement
it
to
negative
one.
So
that's
the
problem.
A
C
E
C
Only
I
the
only
exception
I
can
find
in
medical
is
that
when
the
reference
count
is
going
to
be
negative
value,
so
the
only
part
I
can
see
is
that
the
throw
is
the
default
value,
the
value
we
can
like
say
the
fallback
value
of
33
only
when
the
electron
is
being
zero.
So
in
that
case
I
can
see
that
zero,
our
default
value,
will
be
very
intuitive
to
what
we
have
already.
A
C
A
C
C
C
A
A
What
is,
what
is
naf
does
not
be
reference
set
an
exception,
so
not
be.
A
D
C
Right,
it
will
be
unref.
You.
A
C
A
D
C
Yeah
they
do,
let's
say
when
this
function
do
not
call
into
c
plus
do
not
clean
javascript
right
retaining
next
box
with
right,
convenient
convention,
c,
plus,
plus
error
handling.
A
C
A
C
A
F
So,
as
a
for
mentees,
I
heard
from
kevin
that
there
is
a
few
things
to
pick
up.
I
picked
up
the
I
think
arbitrary
task
for,
for
you
know,
for
testing,
doing
running
single
tests.
Is
that
what
I
pick?
Is
there
an
issue
for
that
for
that
or
something.
A
Sorry,
for
so
the
test
for
which
thing
for
which
I
mean
for
running
a
single
test
versus
running
all
the
tests.
Yes,
that's
right,
yeah!
I
don't
know
if
there's
a
an
issue
for
that.
B
E
C
A
E
E
Binary,
I'm
not
sure
the
best
implementation
method
to
do
that.
Maybe
it
would
be
various
defines
or
targets-
I
don't
know,
but
I
think
from
looking
at
it
as
the
end
goal
of
being
able
just
to
compile
and
run.
One
test,
I
think,
is
beneficial
in
the
long
run,
but
I
really
haven't
thought
of
the
implementation
details
too
much.
A
A
E
A
E
So
that's
another
thing
that
we
can
take
a
look
at
because
when
you
rebuild,
obviously
it
has
to
do
everything,
but
if
you
build
it
does
the
differences.
E
A
E
E
But
then
yeah
it
does
still
require
you
to
build
everything
up
front,
at
least
which
I
think
like.
In
the
long
run,
it
may
be
too
too
complicated
of
a
system
in
order
for
it
just
to
build
one
specific
set
of
sources.
I
don't
I'm.
A
Not
sure
yeah,
I
think
I
I
think
I
you
know
I'd
see
value
in
that
first
thing
of
like.
Can
we
have
it
so
that
it
doesn't
rebuild
everything
on
you
if
it
doesn't
need
to
and
then
sort
of
the
second
one
of
can
running
it
still
would
be
nice
to
have
a
target
that
says
just
run
this
this
one
test
or
a
set
of
tests
versus,
because
I
know
I've
been
in
cases
where,
like
I'm,
like
commenting
out
tests
and
stuff
like.
D
A
E
E
E
E
So
if
there
was
a
way
where
we
only
compiled
the
specific
test
targets,
then
modifying
the
header
wouldn't
be
such
a
big,
a
nuisance
right,
but
definitely
have
some
benefit
just
to
the
rebuild
for
the
normal
incremental
build
for
now
and
then
maybe.
D
F
E
Yeah,
so
we
can
either
so
the
one
thing
of
doing
an
incremental
build
that
could
be
fixed
by
changing
our
package.json
script
for
npm
test,
because
right
now
that
runs
nodejib
rebuild
as
the
command
and
rebuild
will
clean
everything
and
then
build
everything
again.
If
we
just
change
that
to
build
or
create
a
new
script
task
that
uses
build,
then
it
will
do
the
incremental
build
instead.
F
F
E
F
A
It's
a
little
harder
like
in
the
index.js.
I
usually
go
in
there's
some
existing
code,
which
already
splices
out
tests
so
like
I've.
I've
in
the
past
said:
okay,
like
let's
splice
out
everything
except
for
a
few
things
or
you
can
go
and
run
the
like.
They
all
they
have
a
usually
the
tests
have
a
js
file
which
you
can
run,
but
often
you
also
have
to
figure
out
well.
A
Whole
thing
yeah
so,
like
I
don't
know
like
if
npm
is
going
to
start
another
process,
that's
going
to
get
us
in
trouble
as
well,
but
ideally
you
know,
at
least
in
the
cases
I've
been.
You
want
to
run
this
test
possible
by
itself
and
then
also
you
may
want
to
run
it
under
val
grinder.
You
might
want
to
run
it
under
under
under
the
the
debugger,
so
if
we
can
make
it
a
little
bit
easier
to
do
that.
A
E
All
right
I
have
to
sign
off,
though
now
so
we
will
be
in
touch
online
yep
thanks.
A
Talk
to
you
later,
any
sorry
go
ahead.
A
A
Let
us
just
take
a
look.
I
don't
see
anything
too
brand
new
here.
Let's
take
a
just
a
quick
look
under,
although
I
guess
legend
of
cass
I
did
have
one
question
in
there
is
maybe
one
in
here.
So
that's
worth.
A
A
Right
so
I
just
my
one:
question
was
understanding
a
little
bit
for
me,
the
the
different
options,
because
I
think
it's
reading
it's
reading
pretty
pretty
good.
Now,
except
I
still
wondered
about
this
one
thing,
which
was
where
we
files
changed.
C
A
A
A
Right,
okay,
so
it's
it's
kind
of
like.
Let
me
just
where's
the
implementation
of
our
helper.
C
C
C
A
C
A
Doing
nothing
right,
but
but
that's
sort
of
like
our
test
code,
is
kind
of
like
not
best
practice,
because
you
know
it's
only
test
code
right
yeah.
I
I'm
almost
wondering
if,
like
in
here,
it
would
be
the
like
the
if
we
were
checking
all
those
checking
for
exception
in
all
those
places
in
the
else.
It
would
be
something
like
you
know
if
pending
exception,
then
abort
otherwise
return
the
value
right.
A
Okay,
okay,
so
you
can't,
we
can't
do
that.
Okay,
that
makes
sense.
I
was
just
wondering
like:
is
there
any?
Would
it
would
it
make
any
sense
for
us
to
to
do
something
to
show
better
practice,
but
you
can't
really
the
maybe
is
what's
letting
you
do
better
checking
and
in
helping
the
compiler
enforce
that
so.
A
Right:
okay,
so
yes,
okay!
Now
that
helps
me.
Okay,
I
think
I've
got
it
if
you've
already
changed
all
this,
because
I
didn't
really
have
any
other
questions.
I
think
everything
else
was
made
sense
to
me.
So
cool,
okay,
thanks,
let's
see
there
so
in
there
I
didn't
see
anything.
Let's
just
quick,
take
a
quick
look
at
node
and
see
if
there's
any
issues.
Actually
we
can.
C
A
No,
it
sounds
good,
so
so
deepak
welcome,
thanks
for
for
joining
to
help
out
on
this
front,
and
I
think
you're
connected
with
with
with
kevin
there.
But
if
you
have
any
questions
and
you
want
to
reach
out
to
the
rest
of
us
as
as
do
you
have
our
emails.
A
A
Oh,
maybe
deepak
subtracted
anyway.
Okay,
so,
let's
just
make
sure.
If
you
know,
if
defect
you
don't
have
access
to
our
emails,
then
just
let
us
know
and
we'll
make
sure
we
connect
you.
So
you
can
ask
other
team
members
questions
too.