►
From YouTube: 2022-09-02-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
A
So
welcome
to
the
mauston
11
before
we
get
started,
anybody
have
any
announcements
or
news
that
they
want
to
like
to
share.
C
A
Think
the
first
one
again
we
have
end
of
summer
or
whatever
we
have
a
few
people
away.
So
I
think
the
first
two
adding
a
list
of
non-c
language
bindings
and
better
coverage
of
node
api
and
youtube.
I
think
nick
and
or
kevin
were
looking
at
those
and
since
they're
away.
I
don't
think
we
have
any
updates
on
those
or
somebody
else
has
something
to
add.
A
Okay,
the
next
one
is
drive
towards
full
coverage.
I
don't
know
jack
if
you
have
anything
any
update
on
that.
A
B
A
Yeah,
okay,
I
guess
anything
else
we
should
discuss
on
that
one
before
moving
on.
I.
A
B
A
B
I
don't
know
I
have
a
pull
request
opened
last
time.
B
A
B
So
thankfully,
at
this
point
probably
I
want
to
ask
your
opinion.
So,
as
you
see
my
example
right
now,
only
against
plain
and
an
api,
we
could
maybe
work
to
it
c,
plus
plus
node
api
as
well.
Thank
you.
A
B
C
B
A
So
if
we
can
try
and
take
a
look
and
review
and
and
then
get
that
one
landed,
that'd
be
great
all
these,
I
assume
assume
all
these
warnings
are
just.
We
have
a
problem
with
the
yeah.
These
are
not
on
any
of
the
files.
You've
added
right,
the
unchanged
files;
okay,
no,
never
mind
so
yeah,
okay,
okay,
good,
so
yeah.
It's
just
on
the
rest
of
us
to
go.
Take
a
look
at
that.
A
Yep,
okay
tracking
issues
for
things
that
are
ported,
I
don't
see
anything
new
this
time
you
just
take.
A
A
C
A
C
A
C
So
previously
we
have
been
discussing
about
hosting
the
and
the
hosting
the
cleanup
of
the
environment,
and
so
that
we
can
find
the
chance
to
evaluate
and
evaluate
finalizers
at
the
shutdown
before
the
before
the
timings
that
we
are
disallowed
to
evaluate
javascript.
But
in
this,
in
this
example,
we
don't
have
such
timing,
since
the
isolator
is
interrupted
so
which
made
it
which
made
the
assumption
of
hoisting
the
shot
down
to
be
impossible.
A
Right
is,
and.
A
C
Yeah
with
an
error
code
is
a
yes,
they
could
infer
if
they
are
served
calling
to
javascript
but
but,
like
I
said,
even
with
an
error
code,
they
have
to
choose
an
api
dedicated
for
testing
if
it
is
safe
saved
according
to
javascript,
so
that
api
called
totally
and
no
op,
since
they
are
not
doing
anything
else,
they
are
just
to
checking
if
they
are
saved,
calling
the
javascript
so
adding
a
new
dedicated
api
for
that
check,
which
seems
to
be
the
most
reasonable
way
to
do
that.
Right.
A
C
A
A
The
one
thing
I'm
just
checking
here,
I
think
you
might
have
commented
about
it
but
like
this
doesn't
look
like
it's
added.
Oh
there,
it's
right,
it's
under
it's
under
the
experimental,
so
yeah.
Okay,
so
I
mean
that
that
all
sounds
good
to
me
and
the
pr
looks
good.
You
know
from
your
opinion.
Is
it
ready
to
go.
C
It's
a
requirement
for
us
to
discuss
this
pr
in
this
meeting
first,
so
that's
the
first
step
and
I
will
I
will
continue
to
review
this
pr,
and
I
I
see
that
the
cia
is
failing.
So
maybe
we'll
need
the
author
to
and
cooperate
with
us
together.
Passing.
A
B
I
only
have
a
question
like
I
was
a
little
bit
confused
later
that
sometimes
we
have
new
apis
have
prefix
node
api.
This
one
has
like
an
api
prefix
like
what's
what
should
be
our,
I
think
definitely
always
know
the
api
new
prefix.
It
has
something.
Let's
say
it's
like
I
don't
know.
What's
current
take
on
it.
A
B
A
B
A
Yeah
well,
the
history
is,
you
know.
Somebody
complained
that
nappy
had
a
negative
context,
so
we
said
okay,
we'll
move
over
to
using
node
api
instead,
so
we
did
that
in
all
the
docs,
but
we
couldn't
change.
You
know
since
it's
api
stable,
we
couldn't
change
everything
else,
but
we
said
for
new
ones,
we'll
add
it
as
node
api.
A
A
A
C
So,
but
we
don't
have
a
test
case
in
the
core
report,
so
I'm
afraid
we
may
missing
a
corner
case
in
this
one.
So
I'm
I'm
going
to
add
a
test
case
in
the
core
repo
and
then
we'll
come
back
to
this
pr
to
see.
If
this
pr
satisfies
that
use
case,.
A
B
And
also
kind
of,
I
wonder
if.
B
C
The
only
problem
is
with
the
weak
reference
on
these
values,
but
since
they
are,
information
already
have
implemented,
not
api
references
with
without
weaker
reference
support,
so
I
suppose
they
can
go
ahead
and
add
a
strong
reference
to
primitive
values,
and
that's
it
I
mean
we
don't
have
a
guarantee
on
how
weak
reference
works
in
another
apis
and
as
they
are
determined
by
the
engines,
and
you-
and
I
mean
that's-
that's
already
the
how
they
how
this
I
have
a
link
in
my
comments
that
how
currently
those
node
api
implementations
works
on
the
reference
part.
C
A
C
B
We
just
simply
say
like
our
weak
semantic,
would
only
work
for
objects
or
like
or
maybe
like
or
like
you
said,
javascript
does
not
support
it.
I
think
I
think
javascript
standards
supposed
to
support
vcref
the
new
standards,
so
thankfully
I
would
expect
that
most
of
javascript
engine
which
support
latest
and
greatest
javascript
they
support
supposed
to
support
some
kind
of
big
semantic.
A
C
Yeah
but
I
mean
the
problem:
is
that.
C
C
C
They
can
support
evangelion
tables
in
not
api,
weak
references,
but
but
that,
but
but
I
mean
the
weak
semantics
and
how
do
I
describe
it?
I
mean.
C
C
The
add-on
didn't
have
a
way
to
observe
the
node
add-on
implementations
how
the
garbage
collection
works,
since
we
didn't
expose
any
like,
say,
engine
details
to
the
node
add-on
node
api.
So
these
implementations
are
free
to
discard,
collect
values
when
the
node
api
reference
comes
to
reference
contact
comes
to
zero.
So
in
our
document
we
have
said
that
when
the
reference
count
is
zero,
when
the
reference
column
is
zero,
there
is
no
guarantee
that
you
can.
You
can
actually
get
the
javascript
value
from
the
reference
since
the
value
came
already
being
collected.
C
B
A
C
Yeah,
but
we
didn't
say
when
will
it
be
collected
since
we
didn't
provide
a
final
analysis
in
when
creating
a
reference?
Sorry,
I
don't
cannot
infer
when
the
value
is
collected,
so
it's
it
is
safe
for
implementations
to
actually
to
to
to
to
to
to
implement
another
hiv
reference
counting
mechanism
rather
than
the
rather
than
how
v8
works
or
how
right
how
this
modern,
modern,
modern
browser
works.
B
Right,
we
still
need
to
keep
required
that
all
the
references
must
be
deleted
explicitly
because
otherwise,
we'll
change
existing,
be
here.
It's
unfortunate,
but
yeah.
A
A
A
Okay,
as
long
as
we're
confident
that
you
know
it's
implementable
across
all
the
platforms,
the
one
thing
we
do
need
to
think
a
little
bit
about
is
how
we
handle
node
api
versions,
because
it's
kind
of
like
we're,
adding,
if
we
add
the
ability
within
the
existing
function
to
now,
do
it
on
different
types.
That's
effectively,
adding
new
functionality,
which
you
know
it's
the
you
might
compile
against.
I
guess
it's.
A
Yeah
you
could
so
here's
the
problem
that
I
could
see
is
like
you're
running
with
the
latest
node,
and
you
specify
an
older
version
of
node.
Api
say
like
that.
That
was
from
a
new
an
older
version
of
node
you'll,
compile,
okay
and
you'll
run
okay,
because
that
newer
version
of
node
supports
adding
references
to
these
new
types
right.
A
C
Yeah
right
currently,
we
didn't
have
any
runtime
checks
regarding
the
node
api
versions.
It's
it's
mainly
used
in
the
real
time
right
since
it's
used
to
to
expose
another
apis
declaration
right.
C
A
B
Then
I
would
propose,
I
remember
we
discussed
about
this
features.
What
we
can
do,
we
can
add
this
feature,
and
people
right,
you
can
simply
check
for
this.
A
feature
exists,
a
feature
actually
can
feature
can
be
in
in
api
is
just
kind
of
macro.
If
macro
is
defined,
the
feature
is
defined.
If
macro
is
not
defined,
then
feature
is
not
defined
right.
A
B
But
in
this
case
it
should
be
compile
time
right,
like.
C
B
But
okay,
just
kind
of
quickly
one
scenario
like
say:
somebody
created
a
node
module
and
compiled
against
a
new
version
of
node.js
now
exactly
same
module.
They
want
to
run
against
all
the
version
of
node.js,
so
think.
At
this
point
we
still
need
to
have
some
kind
of
runtime
check.
A
Basically
the
if-def
should
basically
make
sure
you
can't
link
against
any
like
functions
that
are
in
six
or
seven,
and
I
think
it
could
be
the
same
thing
that,
like
these
feature,
flags
wouldn't
be
defined.
So
you
try
and
compile
and
say
I'm
targeting
five,
but
it
would
basically
say
well,
I
don't
know
what
that
feature
is.
A
B
Okay,
let
me
let
me
then
change.
I
agree
before
both
of
your
points
and
let
me
change
this
cpr
in
a
way
that
we
don't
introduce
new
apis,
but
we
do
have
features
which
would
control
this
new
behavior.
A
Right
so
basically
the
feature
would
say
you
can
now
you
turn
this
feature
on
now.
You
can
make
references
on
types
you
couldn't
before
right
and
yeah.
That
makes
sense,
and
I
guess
like
if
we
were,
we
were
already
going
to
create
new
ones.
That
meant
we
were
comfortable.
Other
engines
could
implement
them
anyway,
so
that
that's
that's
totally
reasonable.
A
I
think
the
only
thing
that
maybe
we
haven't
touched
on
in
this
discussion
today
was
like
in
one
case,
and
maybe
that's
not
in
the
names
anyway
I
thought
like
it
might
have
been
like
if
we
were
giving
more
information
about
like
hey
this
reference
is
not
going
to
be
any
type.
Could
there
be
some
optimizations
like
if
it
was
only
an
object?
C
And
from
what
I
can
tell,
I
didn't
see
such
optimization
in
the
javascript,
but
I'm
not
sure
about
the
va
side.
I'll,
maybe
that's
worth
to
explore.
A
C
A
A
B
That
we
need
these
apis
and
they
implemented
this
gsi
api
kdpi,
but
letter
uses
for
react
native.
We
do
need
to
have
ref
counted
references
to
any
any
value
type.
So
technically,
I
need
to
effect.
I
need
to
just
this
feature
right,
so
I
just
yeah
so
kind
of
in
my
implementation.
Currently
I
have
the
special
extension
methods
to
know
the
api.
How
implemented
stuff,
but
I
want
to
have
it
be
part
of
our
core
node
api.
You
know
so,
if.
C
B
A
No
okay,
this
one,
I
guess,
is
a
new
right,
but
shenzhen
you've
already
commented
on
this
right.
So,
okay
yeah,
because
I
think
having
that
reproduction
is
important,
we
can
make
sure
there's
a
test
or
whatever.
A
B
Oh
yeah,
I
submitted
a
few
pr's.
I
completely
forgot
about
it
yeah.
I
was
updating
some
remember
last
time
we
discussed
that
we,
our
ci
kind
of
addresses
some
uses
some
old
versions.
Now
that
does
not
use
some
new
versions
so
think
I
try
to
walk
through
a
couple
of
for
examples
and
add-on
api
and
have.
B
What
will
okay?
So?
What
what
I've
seen
here
like
we
do?
Have
we
installing
a
node
version
using
some
kind
of
interesting
algorithm?
I
didn't
figure
out
why?
Because
I
thought
we
can
just
simply
use
github
command
to
install
a
required
version,
so
we
see
like
up
up
there
line
28
new
green
line
20.
I
said
like
a
action
setup
note
and
we
specifying
version
so
think
we
are
it's
supposed
to
replace
with
removed
lines.
B
A
B
A
B
A
B
C
B
A
A
Like
these
are
all
just
all
right
running
the
tests.
A
A
A
B
B
A
Okay,
well,
if
not
thanks
for
everybody
for
taking
the
time-
and
I
just
spilled
some
tea,
but
thanks
for
everybody
for
taking
time
and
we'll
see
you
all
next
time.