►
From YouTube: 2021-08-13 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
All
right,
hello,
everybody
and
welcome
to
today's
this
week's
node
add-on
node
api
team
meeting
for
august
15
august
13
2021.
Before
we
get
started,
does
anybody
have
any
announcements
that
they
would
like
to
share.
A
All
right
welcome.
Welcome
so
again
I'll
ask
before
we
get
started.
If
anyone
has
any
announcements
that
they
would
like
to
make.
A
All
right,
can
everyone
see
my
screen.
A
Yeah,
yes,
okay,
so
first
we
have
the
still
issues
to
discuss.
Let's
see
we
had
this
one
that
was
added,
but
it
seems
like
this
was
closed.
B
Okay,
I
only
wanted
to
remember
that
I
have
paragus
on
unknown
headers
so
where
I
try
to
improve
the
documentation
and
if
anyone
had
time
to
review
I,
after
that,
I
can
publish
this
on
mpm.
B
So
it's
it's.
The
only
thing
that
I
want.
I
want
this
course
about
this.
Okay,
yeah!
It's
it's
closer!
The
issue
for
me.
B
A
Then,
let's
see
the
ones
that
I
had
added
still
we
had
so
this
one
was
the
move,
moving
the
destruction
to
the
move
and
we
did
discuss
this
last
week
and
there
has
not
been
any
update
from
the
original
poster
or
anybody
any
interested
parties.
A
So
I
suppose
we'll
just
leave
this
open
until
they
come
back
to
us.
No
okay,
then,
let's
see
the
other
one.
Let's
see.
A
Yeah,
but
I
guess
because
we
had
released
a
new
version
of
node
add-on
api,
so
we're
seeing
if
the
new
version
provides
a
fix
for
this
person's
issue,
and
I
guess
we're
waiting
to
hear
back
on
that.
A
A
I
think
this
would
probably
be
one
that
would
be
left
best
for
discussion
when,
when
the
whole
team
is
is
back
unless
lucas
or
anyone
else
or
or
nick
or
anyone
else
has
anything
else
to
say
about
this
issue.
Yeah.
A
Okay,
so
we'll
move
on
then.
A
D
Sorry,
I
just
answered
this
really
a
minute
ago
and
I
probably
didn't
understand
the
question,
but
I
guess
yes
hermes
and
react
natives.
They
do
have
a
way
to
have
a
kind
of
reference
to
kind
of
simple
values:
primitive
values,
but
they
mostly
do
it
in
external
apis
for
strings
and
symbols.
If
you
like
and
other
kind
of
simple
values-
and
I
put
all
these
different
preferences
to
the
source
code
of
hermes,
api
implementation-
they're,
mostly
like
numbers,
bulls
and
and
see
this-
is
how
they
they
implemented.
D
This
external
references,
they
provided
some
kind
of
callback
and
this
callback
tells
garbage
collector
what
current
routes
right.
This
is
the
way
how
this
permanently
kind
of
references
versus
local
references,
so
pretty
much
anything
we've
put
in
this
special
kind
of
double
linked
list,
it's
kind
of
very
similar
what
we
do
in
an
apis
for
v8.
We
have
double
linked
list
of
all
experiment,
kind
of
references,
so
the
same
here
we're
using
they're
using
a
std
list
which
is
like
in
standard
c,
plus
plus
pretty
much
double
linked
list
structure.
D
So
anything
inside
of
this
structure
say
like
so
just
saying
what
our
kind.
D
To
the
garbage
practice
we're
making
the
permanent
references
and
the
second
link,
I
put
it's-
how
we
convert
between
this
publicly
exposed
full
gsi
values
versus
kind
of
whatever
we
keep
internally,
and,
as
you
see
this,
this
function,
I
put
link
to
it's
like
a
hermes
valley
from
from
value
from
from
publicly
exposed
failure,
and
you
see
like
a
publicly
exposed
value,
does
not
contain
incorrect
implementation,
undefined
now
boolean
or
number
they
all
get
like
you
see
here,
recreate
it.
D
I
don't
know
if
it's
an
internal
kind
of
limitation
or
it's
mostly,
maybe
just
some
kind
of
optimization.
I
would
expect.
D
But
I
think
it's
I
think
it's
still
possible
to
expose
like
primitive
values
like
numbers.
Just
I
really
want
to
play
with
this
code
first,
because
I
couldn't
get
a
kind
of
different
answer
from
just
looking
through
his
code.
A
Right:
okay,
okay,
so
is
there
anything
that
you
need
from
from
us
to
help
you
in
your
investigations.
D
Right
so
think
I
I
just
want
to
understand
the
context
with
this
question.
It's
is
it
it's
pretty
much.
We
want
to
have
exception
to
be
kind
of
some
primitive
value
right
like,
for
example,
people
can
say,
throw
five
right.
D
Yeah,
definitely
kind
of
fool
bar
would
work,
because
we,
I
can
confirm
today
the
strings
and
symbols
they
internally.
They
three
just
like
objects
perfectly
in
hermes
and
usgs
api.
So
this
this
contract
would
work.
I
guess
question
will
be
if
somebody
says
pro
five
like
throw
in
numbers.
A
C
Well,
we
previously
discussed
about
this
that
if
some
of
these
engines
doesn't
support
food
like
say
primitive
value,
like
numbers
and
either
maybe
inline
value,
then
the
minimum
requirement
for
us
to
resolve
the
question
a
result
properly
that
we
expanded
the
question
to
allow
referencing
symbols
in
our
api.
So
that
would
allow
us
to
solve
the
problem.
C
D
Yeah,
I
definitely
can
confirm
strings
and
symbols.
It's
yeah,
but
and
internally
numbers
pretty
much
internal
inside
of
hermes
values
they
pretty
much
three,
the
same
numbers
and
all
the
rest,
but
for
internal
representation.
I
believe
they're
using
it's
a
double
non
encoding,
if
you
like
it
could
be,
it
could
be
a
reason
why
they
may
be
not
exposing
them
anyway.
D
I
probably
need
to
kind
of
play
with
it
a
little
bit
more
if
number,
if
we
want
to
keep
referencing
numbers,
but
I
think,
even
if
it's
with
current,
I
think,
like
boolean
numbers
should
not
be
a
big
deal,
because
we
can
always
add
additional
field
in
implementation,
so
we
can
make
it
look
like
we're
exposing
this
permanent
reference,
while
inside
we
just
keep
primitive
value,
so
it
can
be
effectively
an
api
implementation
detail
on
those
thermos.
If
you
like,
so
even
hermes,
does
not
support
it.
D
Right
but
thankfully
speaking
v8
supports
it
right
and
I
guess
many
other
javascript
engines
supports
referencing
symbols
right,
yeah,.
A
Right
for
my
initial
investigation
that
I
found,
I
did
see
that
so
we
were
just
kind
of
reaching
out
to
see
what
other
ones
do.
D
A
A
D
Yeah,
I
I
believe
definitely
we
can.
If,
if
hermes
react,
may
difference
was
only
and
last
the
line
is
stable.
I
think
it's
also
from
this
perspective.
Okay,.
D
And
another,
my
comment
here
was
about
like
a
shared
ptr
vtr,
it's
pretty
much.
I
found
that
the
current
nap
implementation
of
references,
like
that's
very
kind
of
unintuitive,
because
thankfully,
today
I
not
only
have
to
kind
of
manipulate
the
reference
counter,
but
also
need
to
understand.
When
I
need
to
destroy
this
object,
it
would
be
really
nice
to
have
kind
of
more
traditional
share.
Ptr
vpr
behavior
that
you
I'm
as
a
user.
D
I
only
care
about
ref
counting,
because
I
don't
know
like
m-
is
the
last
one
or
not
like
much
easier,
just
simply
say
or
increment
decrement
and
actually,
depending
on
the
ref
counter.
D
Permanent
reference
will
be
destroyed
or
not
automatically,
and
the
same
will
have,
for
example,
for
weak
ptrs,
because
current
augmentation
has
effectively
does
not
allow
you
to
support
a
reference
counter
of
how
many
weak
references
you
have.
Actually,
it's,
I
think,
a
merging
reference
counter
with
a
decreased
country
in
one
reference
as
it
went
today
in
api,
it
becomes
kind
of
difficult
to
use,
and
it's
not
more
traditional,
like
separating
these
two
concepts
shared
with
your
stick,
which
are
behaving
them
more
on
this
expected
stuff
would
be
really
cool.
D
It's
it's
just
gonna
a
proposal
to
add
additional
api.
We
obviously
can't
change
existing
one,
but
you
can
probably
add
better
references
if
you
like.
A
Right,
I
think,
maybe
if
we
could
figure
out
a
like
an
api
or
a
design
that
you
think
would
look,
would
work
well
in
like
a
use
case
or
whatnot,
and
then
we
can
see
look
at
implementing
that.
Let's
say
because
I
guess
it
it'd
be
good
to
see
your
exact
use
cases
that
you
want
to
that.
You
have
with
shared
pointer
and
weak
pointer,
to
see
how
we
can
migrate
or
use
that
in
node
api
terms.
If
that
makes.
D
Sense,
yes
I'll
I'll
play
with
it
in
next
say
few
weeks
and
hopefully
provide
more
kind
of
detailed
proposal.
If
you
like.
A
So
then
issues
ported
there
has
not
been
any,
but
let
me
always
check
this
out
and
let's
see
what's
happening.
A
Okay,
that's
good
to
know
all
right
well,
we'll
just
keep
on
keep
on
moving
and
keep
on
trucking
all
right,
tested
methods.
Jack
is
working
on
the
tests,
so
I
think
we
can
bypass
that.
But
let's
see
if
he
has
anything
that
is
waiting
for
us,
so
we
can
just
know
he
does
not.
A
A
B
A
Okay,
then
enable
debug
testing.
Let's
see,
I
don't
believe
this
is
what
michael's
working
on
he's
not
here.
So
I
guess
we
won't
really
have
an
update
unless
anything's
here,
but
don't
see
anything.
B
Yeah,
sorry,
I
don't
have
the
time
in
last
two
days
before
that
the
ci
was
blocked
for
the
security
release
yeah
in
this
weekend.
I
try
to
make
this
a
new
release.
A
A
A
No
okay,
then
we
can
see
sort
of
what's
new
here
this
first
one
I've
been
working
with
this
poster
here
they
want
to
use
enoms
in
their
code,
and
I
had
just
given
examples
using
externals
waiting
to
hear
back
from
them.
If
they
think
that's
a
good
idea.
I'd
also
mentioned
you
can
use
some
sort
of
object,
wrap
if
you
want,
but
we'll
see
what
they
say.
B
A
Basic,
it's
like
they
want
to
make
a
call
in
some
sort
of
native
method.
Here
you
see
it
doesn't
have
any
environment
or
whatnot.
They
want
to
end
up
making
some
call
into
the
node
thread
and
getting
its
response,
and
that
function
is
a
is
asynchronous,
so
it
returns
a
promise.
A
A
Then
this
one
here
I
also
took
a
peek
at
this-
is
talking
about
unit
tests
and
whatnot,
and
I'm
really
not
sure
how
to
answer
this
one,
because
I
don't
really
use
c
plus
like
that.
In
order
to.
B
A
Any
frameworks
or
libraries
that
you
can
construct
fake
objects
or
proxy
objects,
or
anything
like
that.
Does
anybody
have
any
idea
about
this.
A
B
Bit
on
nick
yes,
but
I
cannot
able
to
reproduce
the
issue.
I
tried
to
yeah,
create
a
repo
and
publish
the
content
on
fly
and
only
fly.
I
enabled
the
yeah
next
js
plugin
that
yeah.
B
Essentially
produce
the
problem,
but
it
it
compiled
and
worked
well.
So
I
don't
know
what
is
the
problem
with
the
the
project.
E
B
The
native
tribe,
because
I
found
the
same
issue
right
on
the
nativ5
next
and
yeah.
Well,
essentially,
the
problem
is
that
is
on
sharp,
that
is
a
native
add-on
to
for
image,
processing
and
yeah.
It
say
that.
B
Yeah
don't
find
the
binding.js,
and
I
remember
that
this
was
an
issue
if
you
have
a
folder
with
a
space,
and
so
this
is
why
we
unloaded
done
api
added
include
underscore
dear
instead
of
include
in
our
index.js
and.
B
I
am
right
yeah,
but
now
I
am
so.
I
asked
to
the
reporter
this
and
yeah.
He
said
that
the
name
of
the
project,
the
folder
that
contained
the
project,
okay,.
E
B
Yeah,
it's
another
done
api
that
contains
the
the
the
new
things
and
sharpies
these
so
because
this
change
was
proposed
by
the
sharp
maintainer.
So
I
I
I
I
don't
know
how
do
I
so
is
sharp
itself.
A
B
Using
yeah,
I
use
another
done
api
and
I
think
that.
B
Yeah
we
we,
we
can
go
on
the
race,
so
yeah.
If
you
go
on
the
github
release,
our
yes.
B
So
yeah
trying
to.
A
Is
this
not
hold
on
hold
on?
I
go
here.
B
Oh,
we,
okay,
you,
you
can
go
on
the
on
the
yeah
on
the
yeah,
go
on
the
changelog
dot,
md.
B
A
I
see
okay,
all
right
so.
B
This
is
the
only
thing
that
yeah.
F
B
Let's
introduce
this
this,
this
problem.
B
Is
but
the
problem
is
that
he
is
in
a
production,
is
when
he
deployed
the
project,
so
I
I
cannot
see
how
he
configured
all
the
things
right.
Okay,
I
just
followed
the
tutorial
and
that
night,
if
I
give
to
developers
and
all
work,
so
maybe
if
he
customized
something,
maybe
yeah,
maybe
yeah,
he
have
he
yeah.
If
you
customize
something
you
could
have
this
kind
of
problem.
A
Okay,
well,
I
guess
we
can
just
wait
to
see
if
he
messages
anything
back.
Let's
just
go
from
there.
Let's
see.
F
A
Let's
see
if
we
can
just
take
a
quick
peek
and
to
see
as
to
why,
I
think
that's
the
only
implementation
piece
and
that's
all
tests
yeah.
So
they
are
saying
one
more
check
check.
A
A
A
B
You
can
link
the
pr
to
the
issue
so
yeah.
It's
like
a
reminder.
A
A
Okay,
so
we
could
take
a
look
at
that.
A
Okay-
and
I
think
that
is
it
because
that's
the
one
that
deepak
is
working
on-
that
we
added
all
right,
then,
let's
see,
if
there's
any
on
core.
A
Michael
would
want
to
take
a
look,
but
he
is
off
this
week.
If
anybody
else
has
some
time
to
look
at
this,
that
would
be
great.
It's
just
a
documentation.
Okay,
then
I
think
that's
it.
Does
anyone
have
any
pull
requests?
I
don't
think
we
we
have
any.
C
C
It's
a
back
port
appear,
so
we
have.
We
need
to
replace
to
the
new
the
latest
staging
branch
and
then
we
can
get
it
to
be
merged
to
the
back
party
branch.
Okay,.
A
All
right,
then:
okay,
that's
the
list
of
issues.
Now,
michael
added
this
one
new
this
week,
the
serial
port
asked
if
any
of
the
node
team
would
be
able
to
take
a
look
at
this
pr.
B
A
E
B
Port
of
not
cr
port
using
a.
A
F
A
A
All
right,
then,
that
is
it
for
the
milestones
all
right.
Anybody
else
have
anything
else
that
they
would
like
to
discuss
before
we
close
for
the
evening.