►
From YouTube: 2022-09-09-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.js
node
api
team
meeting
for
september
9th
2022
we'll
go
through
our
standard
approach
of
looking
at
the
agenda
before
we
get
started.
Does
anybody
have
any
announcements
they'd
like
to
share.
A
I
think
the
one
I
might
mention
just
is
there
is
an
upcoming
collaborator
summit
being
planned
in
dublin,
and
so,
if
anybody's
in
that
area
or
is
going
to
no
coffee,
you,
which
is
the
the
right
after
the
collaboration
summit,
be
great
to
see
you
there.
A
A
Okay,
so
we
can
start
up
with
the
add
to
c
non-c
line
language
bindings
and
I
think
the
better
coverage
of
node
api
and
youtube.
I
think
it
was
was
nick
who
is
looking
at
those
two
and
and
he
let
us
know
he
couldn't
make
it
this
time.
I
assume
some
see
he'll
be
back,
but
next
time,
I'm
so
messed
with
that
the
drive
towards
full
coverage
jack.
I
know
you've
been
working
on
that
anything.
You
should
touch
on.
A
A
A
A
Right,
okay,
so
here
we
were
that
takes
us
to.
A
A
I
know.
Vladimir,
you
were
looking
at
this
one
right.
A
C
A
It
looks
like
legendarcast
was
ready
to
had
already
approved
that
one
is
that
one
so
that
one's
ready
to
land
or
is
it
that
you
still
have
more
work?
You
want
to
do
on
that
one
first
you
were
going
to.
I
know
you
were
going
to
do
some
more.
If
I'm
remembering
now
you're
going
to
do
like
a
c
plus
version
too
right.
C
A
B
A
A
Okay
and
that's
it
all-
we
had
from
the
stale
issues,
so
that's
good
tracking
issue
for
modules
that
we've
noticed
that
reported.
I
don't
see,
there's
anything
new
there,
but
I
did.
I
did
notice
one
thing
which
I
thought
it
would
be
good
to
share
here.
B
A
Feature
but
like
this
used
by,
I
just
noticed
so
basically
github
says:
there's
like
1.6
million
repos.
I
think
who
were
who
have
this
like
independencies
or
something
like
that.
B
I
am
actually
a
little
bit
confused
by
these
numbers,
since
my
I've
seen
regulators
that
they
are
not
directly
dependent,
but
it's
marked
as
dependencies.
So
I'm
I'm
not
sure
how
that
calculates
the
dependencies,
but
I
I'm
sure
this
is
a
valuable
numbers,
but
I'm
not
I'm
I'm
just
sometimes
confused
about
it.
A
A
Okay,
so
it
says
10
million
so
yeah.
So
I
don't
know
what
the
the
calculation
is,
but
it's
just
another
indicator
of
usage
and
it
seems
to
be
quite
a
lot
there.
So
that's
good.
A
Okay,
I
haven't
done
anything
with
big
debugging
testing,
so
now
it's
like
particular
issues.
Does
anybody
have
any
particular
ones
they
want
to
pull
up
to
discuss.
C
To
use
this
references
all
for
all
types
yeah,
I
did
this
small
prototype.
If
you
guess
you
can
look
at.
A
Which
pr
is
that?
Well,
it's.
C
So
it's
it's
a
draft
at
this
point.
It
just
just
has
changes
to
the
code.
No
tests,
no
document
changes
yet,
but
that
apparently
quarter
of
the
change
is
very
simple.
C
Yeah,
no,
no
public
api
change,
the
only
flag
area
that
the
value
can
be
potentially
be
represented
as
a
weak
pointer
so
see
during
construction
initialize.
It
I
think:
if
value
is
object
or
function,
then
it
can
be
potentially
a
weak,
pointer
and
everything.
What
I
do
like,
then
we
say
in
clear:
weak
we're
just
checking
if
this
flag
there
would
we
do
we
we
do
something.
Otherwise
we
do
nothing.
But
if
we
set
in
weak
reference,
apparently
our
ref
count
becomes
zero.
C
A
C
So
it
was
saying
like
if
it's
not
object.
If
it's
not
function,
it
can
be
a
big
reference
and
it's
it's
very
simple
change.
In
the
end.
A
A
A
C
But
english
speaking,
what
what
will
happen
if
we
have
like
non-object
type,
if
we
bounce
from
zero,
we
perfectly
like
our
value,
whatever
value
inside
of
reference
will
be
just
simply
invalid,
like
this
will
be
no
value
at
all.
Yes,
the
reference
counter
can
be
incremented,
but
it's
pretty
much
like
referencing.
Now,
after
that,.
C
A
Right
so
I
guess
it's
that
does
it,
but
still
it's
the.
I
think
the
feature
part
was
around
like
we're:
adding
new
functionality
right.
So
if
you,
if
you
start
to
use
it,
you
could
still
break
the
sort
of
you
know
the
model
of
you
target
a
certain
node
api
version,
and
then
it
doesn't
actually
run
on
older
versions
of
node.
A
Right
exactly
like
you,
you
know
say
you
target
note
api.
You
know
I
don't
7,
that's
supported
in
the
earliest
node
that
you
want
to
support,
but
you
start
to
use
this
because
you
don't
realize
that
it's
not
in
node
api,
seven
right.
A
C
Okay,
but
how
we
would
do
it
like
it
cannot
be
in
this
case,
compile
time
error
or
something.
A
Yeah,
it
would
be
compile
time
because,
like
we
already
have
guard
like
you,
you
can
set
a
define
that
says
I'm
targeting
node
api
version
x
and
if
you
set
that
version,
then
the
include
file
like
doesn't
include
the
things
that
aren't
in
that
version
so
like.
If
you
have
a,
if
you
have
a
function
that
isn't
in
that
version,
it
won't
let
you
compile
against
it
and
similarly,
the
define
for
the
feature
flag
could
not
be
included
right.
C
Oh
okay,
so
thank
you.
What
you're
saying
that
we
can
do
it
on
this
level?
See
if
you,
if
you
say
if
you
target
some
kind
of
latest
version
of
node,
so
this
this
behavior,
I
will
be
light
up.
If
you're
saying
you
target
on
some
previous
version
of
node
api,
this
this
behavior
will
be
not
available.
A
Exactly
like,
so,
if
we
go
to
the
node
api,
just
native
api
dot,.
C
Okay,
yeah,
I
can
do
it.
I
just
want
to
kind
of
discuss
first,
this
core
from
core
implementation.
As
for
the
features
like,
I
also
have
a
question
about
some
design.
Ideas,
like
my
initial
implementation
feature,
was
more
like
bit
flags
right,
but
we
can
probably
have
only
probably
64
such
bit.
Flags
should
be
enough
and
all,
but
the
second
idea,
what
I
have
I'm
entertaining
right
now
is
actually
to
have
the
whole.
This
feature
to
be
just
as
one
string
and
effectively
in
the
string.
C
We
can
put
just
some
semicolon
separated
values
if
you
like,
and
we
can
be
kind
of
future
proofed,
and
we
can
put
anything
in
this
string
if
you
like.
C
Right
like
we,
we
need
to
have
probably
three
different
additional
apis.
What
I
think
about
like
ability
to
test
a
feature
available
or
not,
and
also
being
able
certain
or
remove
feature
like
during
runtime
improvement,
but
also
I
want
to
have
this
set
of
features
to
be
passed
during
module
registration,
it's
pretty
much.
What
and
during
module
registration.
I
want
to
use
one
of
four
available
slots.
We
have
four
pointers
reserved
in
our
an
api
module
structure.
C
So
previously
I
was
planning
to
pass
there
like
whatever
can
be
converted
to
pointers
just
integer,
but
now.
A
Yeah
and
performance
you're
only
calling
it
once
so.
Like
performance
shouldn't
be
a
big
deal,
I
mean
internally,
we
probably
have
to
convert
it
to
a
bit
string
or
you
know
something.
That's,
and
even
I
guess
for
setting
it.
Maybe
you
want
to
because
basically
somebody's
going
to
need
to
have.
We
probably
want
to
define
the
feature
flags
right
somehow.
C
A
A
But
yeah,
something
that
is
that
is
not
limited,
would
would
be,
would
be
nice.
C
Because
I've
read
like
64
bits
can
like
32
bits.
I
don't
know
if
we're
still
using
32-bit
platform,
maybe
not
enough.
A
B
A
C
Right,
yeah
yeah,
let
me
think
more
about
it.
I
thought
alternative
design
was.
I
was
thinking
about
passing.
Maybe
an
array
of
integers
in
this
case
we'll
have
just
each
right.
That's
this
integer,
and
we
just
for
example.
If
we
say
this
array
must
be
zero
terminated.
So
in
this
case
we
can
use
only
one
pointer
to
this
array.
It
would
still
it
would
work
too.
Probably.
C
But
what
I
want
to
go
from
today's
meeting,
I
want
to
kind
of
get
your
general
idea
if
it
might
work
the
only
caveat
here
like
previously.
We
we
kind
can
allow
to
use
a
weak
reference
for
symbols,
but
at
least
in
hermes
engine
I
don't
know
how
to
implement
a
weak
reference
for
symbols.
C
So
that's
why,
like
for
here,
we're
saying
it
can
be
weak,
only
object
of
function
which
has
more
more
generic
javascript
laptop
approach.
B
B
A
C
I
I
understand
previously
we
put
symbol
here
because
we
most
probably
need
to
have
really
a
strong
reference
to
symbols,
because
of
I
think
it
was
a
scenario
related
to
errors
right.
A
I
think
like
if,
if
it's
something
we're
concerned
about
it
being
supportable
on
different
engines,
then
the
like,
maybe
it
does
make
sense
like
in
this
feature
flag
to
turn
it
off.
I
don't
know
I
don't
know.
What's
in
the
cast,
do
you
think
like?
Basically,
it
would
be
if
you
opt
into
this
feature.
Well,
okay,
you
can
now
do
more
types,
but
you
know
symbol
isn't
or
should
they
be
different
feature
flags?
I
don't
know.
B
B
A
B
A
A
C
So
simple
behavior
for
strong
reference
will
be
exactly
the
same.
We're
just
simply
saying
that
the
weak
reference
will
not
be
there
because
currently
javascript
standard
does
not
support
it.
Essentially,
right
because
we're
saying
that
node
api
is
supposed
to
be
kind
of
more
aligned,
if
whatever
standard
does
so
kind
of
to
set
expectations.
A
Right,
I
could
just
see
where,
like
maybe
we,
we
introduced
a
feature
flag
that
ops
that
basically
says.
Okay,
I
want
to
remove
symbols
being
able
to
be
weak,
and
you
know
people
who
want
to
target
the
broadest
support
could
then
turn
that
on
right,
like
if
he
thinks
it's
going
to
break
somebody,
but
I
think
if
legendary
cast
is
going
to
think
more
about
it,
you
know
we
can
wait
for
that
recommendation
and
figure
out
sounds
good
yeah.
We.
A
Well,
yeah,
otherwise,
you're
right
that
this
is
a
pretty
small
like
it's
basically
just
lets
other
types,
not
throw
an
error
and,
with
the
feature
flag
turning
it
on,
it
seems
like
a
pretty
simple
thing
to
do
so.
It's
good.
A
B
B
There
is
a
new
issue
about
the
belgran
campaign
complaint.
It
has
already
been
closed
since
we
we've
answered
in
the
issue.
The
number
is
445
18
yeah.
B
And
as
a
status
call,
we
cannot.
We
cannot
close
the
dynamically
loaded
library
since
we
cannot,
we
are
not.
We
cannot
assure
that
the
library
is
cleanly
closed
or
then
we
are
ready
to
clear
the
code.
Well
remember
it
can
be
clearly
closed.
So
that's
the
fact
that
we
didn't
unregister
and
register
any
non-modules
unknown
add-ons
so
which
can
also
applies
to
add-ons
that
are
not.
That
depends
on
know
that
I
don't
know
the
api,
so
I'm
wondering
that
so.
B
A
So
this
we
have
this
dock
on
investigating
memory
leaks
with
bell
grind.
I
wonder
if
adding
a
section
in
here
makes
any
sense.
B
Yeah
right.
A
Because
it
could
be
like
a
section,
you
know,
I've
noticed.
B
This
document
is
mainly
for
contributing
to
the
node.js
core,
which
means
it
can
be
a
internal
documentation.
So
guiding
people
to
here
might
be
introducing
much
more
things
suggested
than
investigating
their
own
add-ons.
Yeah.
A
True,
I
did
so,
I
guess
are
you
thinking
like
if
we
put
something
in
one
of
the
the
node
add-on,
repos
or
somewhere
else.
A
B
A
C
B
A
A
I
think
that'd
be
great,
any
other
ones
there
that
we
should
chat
about.