►
From YouTube: Node.js N-API Team Meeting 2020-08-04
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
Hello,
everybody
welcome
to
the
august
3rd
2020
meeting
of
the
node.js
and
api
team,
we're
going
to
go
through
our
agenda,
but
if
anybody
has
any
announcements
first
then
please
share
them
going
once
going
twice
three
times
all
right.
So
then
let
me
open
the
agenda
and
share.
I.
B
A
A
B
B
So
on
the
lower
right,
there's
environments,
if
you
scroll
back
up
to
the
top
gabriel
okay
in
the
right,
sidebar.
C
B
B
A
B
So
the
the
final,
the
the
final
thing
for
me
to
consider
us
to
close
this
particular
issue
is
where
we
want
to
publicize
this
site.
So,
for
example,
on
the
readme
for
the
examples
repo,
we
should
put
a
link.
We,
we
should
put
a
note
and
a
link
out
out
here
and
I'm
not
sure
if
we
want
to
do
it
for
the
main
napi
documentation.
That's
part
of
core.
A
B
B
D
D
We
we
have
a
section
on
noted
on
api
dedicated
to
the
example,
and
maybe
you
can
see
if
yeah
to
add
a
section
for
these
tutorials.
Yes,
yeah
exactly
you
know
the
done
api.
It's
it's!
It's
nice
to
to
have
these
these
reference.
B
Yeah,
okay,
so
I
can
definitely
do
a
pr
for
the
node
add-on
api
and
we
might.
We
might
enlist
michael's
help
approaching
the
core
and
seeing
what
we
can
do
there.
A
Issues,
so
if
you
just
go
to
like
doc
api,
an
api
md,
we
we
have,
we
have
sort
of
a
a
similar,
high
level
overview
here.
You
know
so
so
you
know
you
can
you
can
just
you
can
just
inject
it
anywhere
right,
pretty
much
just
yeah
I
mean
you,
can
you
can
probably
find
the
the
optimal
spot
where
to
inject
it,
because
like
right
here,
it
starts
out
with
with
just
completely
high
level
stuff
and
then,
but
it
goes
fairly
quickly
into
into
specifics.
You
know
this.
A
This
is
still
explanation,
but
then
these
are
already
like
instructions
right,
and
so
we
have
a
lot
of
this
stuff
here
and
then
I
guess
I
guess
you
know.
Well
I
don't
know
maybe
usage
yeah,
maybe
at
the
end
of
usage
you
you
might
want
to
just
you
might
want
to
just
add,
like
a
resources.
If
we
don't
already
have
it,
we
might
actually
have
like
a
resources
thing.
You
know
like
further
document.
A
If
we,
if
we
don't,
then
then
then
it
would
be
good
if
you
added
it
and
because
then
we
can
just
collect
links
there.
But
of
course,
of
course,
with
with
links,
there's
usually
there's
usually
one
one.
A
One
sort
of
aspect
is
that
if
we
link
to
something
external
then
then
then
you
know
we
might
be
reluctant
to
do
that
because
then,
when
that
link
gets
hit,
then
then
they
know
that
it's
coming
from
from
node.js
right,
and
so
they
can
gain
like,
like
basically
popularity
numbers
from
node.js
if
it's
an
external
link,
but
I
think
in
this
case
it's
a
github
link.
So
so.
B
A
Should
be
fine,
yeah,
but
either
way
I
I'm
not.
I'm
not
100
qualified
to
judge
the
implications
of
that
link,
which
is
why
I'm
suggesting
that
that
you
do
a
pr
against
core,
because
there
are
people
there
that
are
eminently
more
qualified
to
to
to
to
analyze
whether
that's
an
okay
link
to
have
and
and
so
forth,
but
that
this
this
would
be
the
place
to
put
it
in.
C
B
No,
I
think
I
I
think
go
for
the
pr
and
that
that
saves
like
the
two-step
process
of
having
a
discussion
and
then
doing
a
pr.
C
B
B
B
A
Yeah
for
sure
yeah
for
sure
yeah,
yeah,
yeah
yeah.
I
guess
I
guess
given
time
we
should.
We
should
go
all
over
the
over
the
the
tutorials
and
the
examples,
because
you
know
the
fact
is
that
you
know
they
will.
They
will
accumulate
bit
rot
after
a
while.
So
so
we're
just
gonna
have
to
keep
keep
things
fresh,
yeah
all
right.
This
is
great
yeah
awesome.
It
looks
good
and-
and
it's
deployed
using
like
github
mechanisms
right.
B
Yeah,
it's
really
sweet.
Whenever,
whenever
there's
a
merge
to
master,
then
a
github
action
runs
that
has
gatsby
regenerate
the
site,
which
gets
published
on
the
github
pages
branch
and
then
that
is
immediately
served
from
github
pages.
A
A
Okay,
tracking
issues
for
modules.
Aha,
there's
been
activity,
always
happy
to
see
that
unless
I
think
there's
been
activity
because
I
haven't
opened
this
with
with
with
chrome,
okay
yeah.
No,
this
was
a
ways
back.
It's
just
I
had
I
hadn't
opened
it
with.
I
normally
use
firefox
right,
but
chrome
is
better
with
this
audio
stuff.
So
so
the
things
that
are
old
in
firefox
are
new
in
chrome
for
me,
but
this
is
the
point
where
we
always
check
this.
So
let's
check
this.
A
E
A
So
we've
got
that
going:
okay,
note,
conf
eu
workshop
proposal.
B
Yes,
so
I
have
submitted
our
proposal
and
so
now
we
wait
it's
it's
not
clear.
I
I'm
not
seeing
any
documentation
as
to
when
they
expect
the
to
make
the
decision
on
these.
So
we
we
just
wait.
A
A
Okay,
let's
see
well
yeah,
we
haven't
written
much
in
here,
but
this
is
the
point
in
time
when
we
customarily
open
the
repo-
and
we
say
no,
we
don't
say
that
we
say
this
hold
add-on
api.
Why
is
it
so
busy
all
of
a
sudden.
C
A
A
A
A
Yeah,
because
I
mean
the
stack
doesn't
have
any
javascript
in
it,
so
you
can't
simply
call
a
function.
That's
that's
what
it
sounds
like.
What
do
you
guys
think?
I
think
I
think
that's
safe
whoo
event:
loop
integration!
That's
a
lot
of
fun.
A
D
Yeah,
I
I
answered
and
yeah
it's
correlated
with
the
work
that
michael,
is,
is
doing
on
documentation
in
the
core.
B
D
Yeah
we,
the
first
staple
an
api,
is
eight
two
six
zero.
A
D
D
A
A
Oh
no,
I
should
just
go
like
that.
Hopefully
we'll
see
a
pr
on
this
because
yeah
it's
it's
a
long.
It's
a
long
set
of
you
know
dot,
then
dot
then
dot,
then
dot.
Then
it
would
be
a
lot
cleaner.
If
you
just
said,
oh
wait,
wait,
wait
and
be
done
with
it.
Yeah,
it's
pretty
straightforward.
Maybe
I
should
I
don't
know.
Do
you
think?
Do
you
think
this
is?
I
should
label
this
good
good
first
issue,
or
is
this
too
complicated
for
first-time
contributors?
D
I
I
think
that
everyone
can
can
do
this.
So,
even
if
you
don't
know
c
or
c
bus
plus
yeah.
D
To
only
have
to
to
refactor
the
jobs
so
yeah
you
can
mark
as.
A
A
Okay,
all
right,
so
we've
got
that
one
windows
ci.
A
A
Please
all
right
how
to
return
a
created,
object,
wrap
object,
wrap
questions,
always
lots
of
fun
return.
Tags
inside
convo
is
okay
input
created.
C
A
A
All
right
looks
like
looks
like
michael
michael
cranked,
this
one
by
one
turn.
A
D
With
the
paths
right,
yeah,
yeah
and
yeah,
I'm
working
on,
I
guess
that
yeah
we
have
and
solve
the
problem,
but
yeah.
I
I'm
experimenting
both
on
unix
and
on
and
all
windows.
I
want
maybe
yeah.
I
I
I
won't
find
us
to
I'm
a
better
solution:
okay,
but
yeah.
D
I
I
yeah
I
mean
so
sometimes,
but
my
opinion
is
that
now
we
yeah
I
I
try
to
fix
all
as
soon
as
possible
and
yeah
I
I
I
want.
Then
I
want
to
make
a
new
release.
D
A
D
Because,
because
now
we
have
all
the
fixes
that
are
on
the
3.0.1
and
then
you
are
the
new
api
yeah.
A
D
Yeah,
I
I
think
that
it's
it's
right
time
to
to
ship
on
a
new
on
your
release.
Okay,
give
me
another
two
three
days
and
yeah,
then
I
will
open
an
issue
for
the
release.
A
D
A
Okay
yeah
this,
I
think
we
I
think
we
discussed
this.
We
yeah,
we
don't
have.
We
don't
have
contact
support
without
without
a
worker,
and
I
think
this
goes
all
the
way
into
core,
and
I
I
yeah
michael,
and
I
think
we
both
tried
to
see
how
how
we
could
do
this
vm
running
context,
thing
and
there's
just
there's
just
no
way
to
know
what
context
you're
in
especially
for
errors,
errors,
don't
even
have
the
concept
of
a
context
they
heck.
A
They
don't
even
have
an
isolate
in
v8,
so
so
there's
really
no
way
to
to
to
to
make
them
work
as
intended,
except
on
the
javascript
side.
So
yeah,
it's
it's
kind
of
a
kind
of
a
native
interface
shortcoming
of
the
engine.
I
think
that
was
our
conclusion
there.
So
this
needs
work
upstream
in
in
core
to
get
this
to
work
errors
from.
A
B
A
A
All
right,
so
there
we
go
and
then
what
was
this
again.
D
Yeah
yeah
then
sonic
reported
that
was
the
first
to
report.
This
problem,
yeah
and
michael,
worked
on
documentation
in
the
court.
A
So
then,
this
this
should
actually
fix
this
issue
right,
because
all
we
can
do
is
document
right.
He
did
reference
it
yeah
so,
and
this
has
landed.
D
A
D
D
Okay,
I
think
that's
because
yeah
you
can
copy
and
past
the
same
command
on
the
issue.
Seven,
seven,
eight.
A
A
A
D
A
D
What
is
exported
from
the
native
side
so.
A
Okay,
so
okay,
but
wait
a
minute.
I
see:
okay,
okay,
okay,
I
see
what
you
wrote
there
jim,
so
you
can
actually
do
js
doc
on
c-plus
plus.
B
Man,
I
have
to
refresh
my
memory
here,
a
tool
called
documentation.
B
So,
as
I
mentioned
earlier,
when
I
go
through
the
ex
the
tutorials
I'll
review,
the
examples-
and
I
might
I
might
try
one
and
just
see
how
it
works-
yeah
as
a
suggested
way
of
documenting
your
your
methods,
essentially
yeah.
A
So
correct
me:
if
I'm
wrong,
correct
me
if
I'm
wrong,
if
I
understood
this
issue
correctly
so
so,
basically,
if
we
do
what
this
issue
is
asking,
our
napi.h
file
will
basically
explode
with
specially
formatted
comments
which
contain
exactly
what
what
our
markdown
documentation
now
contains.
Did
I
understand
that
correctly.
B
I
I
that
was
not
my
understanding,
my
my
understanding
was
so
to
show
a
user
how
they
might
document
their
own
work
by
adding
js
dot
comments
to
their
c
c
plus
plus
code.
B
A
B
Yeah,
because
js
doc
itself,
which
is
the
foundation
of
everything,
just
expects
the
js.comments
to
be
in
javascript,
because
it's
looking
at
the
javascript.
B
A
A
Yeah
yeah
yeah,
it's
I
mean
you
know
we
are
in
kind
of
a
unique
position.
We
write,
we
write
javascript
stuff,
but
we
don't
write
it
in
javascript.
A
A
A
A
A
B
A
D
Okay,
the
integer
is
the
test
okay
into
test.
Okay,.
A
A
Js
callback
is,
I
don't
know
I
I'm
going
to
ask
for
for
for
a
minimal
example,
because
yeah.
C
A
A
Yeah
this
is
it's
pretty
incomplete,
it's
hard
to,
at
least
for
me,
it's
hard
to
hard
to
tell
where
the
issue
is
because
it
looks
like
threat.
Safe,
is
involved.
A
E
B
A
Where
was
that
sorry-
or
maybe
it's
already
linked
to
that?
Do
we
already
have
a
link
between
the
two
issues,
because
that
would
be
that
would
be
ideal.
A
A
Yeah,
okay,
okay,
so
let's,
let's
see
the
other
repo,
the
core
repo
see
what
nepi
things
are
going
on
over
there.
That
would
be,
if
I'm
not
mistaken,
the
next
issue.
So
let's
have
a
look
at
the
core.
A
Okay,
yes,
this
is
a
new
thing.
Coming
the
async
asynchronous
cleanup
hooks
anna
is
contributing
this
to
both
the
c
plus
plus
interface
and
to
an
api.
A
Okay,
yeah,
that's!
Okay!
That's
that's
a
good
point.
I
should
go
over
the
tests
to
make
them.
I'm
sorry,
I'm
sorry
say
again.
Please.
D
Oh,
I
I
I'm
asking
if.
A
Yes,
yes,
it
it
it's
going
through
the
standard
standard,
cadence
right,
it's
going
to
land
as
experimental,
the
node,
api.h
and
yeah
we're
going
to
have
to
wrap
it
in
in
in
know
that
on
api
and
it'll
still
remain
experimental,
and
I'm
not
I'm
not
sure,
I'm
not
sure
how
the
how
the
back
porting
of
it
will
work.
In
fact,
in
fact,
we
should
probably
think
about
what
we
want
in
any
api
7
right,
because
right
now
we
have
we
have
buffer
detaching
stuff.
A
We
have
that
all
the
way
back
to
10
right,
so
so
we
could
make
an
api
7
just
have
the
buffer
detaching
stuff
and
and
call
that
an
api
7
right
or
we
can
wait
for,
for.
I
landed
the
type
tagging
stuff.
Finally,
because
there
was
there
was,
there
was
some
demand
for
it,
I
think
from
from
the
neon
project
yeah,
and
so
I
I
landed
that
I
I
had
that
pr
open
for
like
over
a
year
and
okay,
since
there's
now
clear
and
present
demand
for
it.
A
I
I
landed
it,
so
that's
that
would
be
experimental,
but
that's
probably
gonna
take
a
while
to
to
trickle
back
if
it
even
gets
backported
to
10,
because
10
is
now
in
maintenance
right.
So
so
we
should
start
thinking
about
cutting
like
an
api
7
slowly
but
surely,
and
one
thought
that
I
had
and
I'm
wondering
what
what
y'all
think
of
that
is
like
if
we,
if,
if,
if
we
had
is,
is
it
too?
Is
it
too
stagnating?
A
If
we
release
a
new
version
of
an
api
at
the
same
time
that
we
drop
support
for
for
a
node.js
version
or
or
like,
if
that's
too
stagnating,
do
we
need
like
multiple
and
api
releases
per
year?
Is
the
question
right
because
we
could
just
go
with
okay?
Whenever
we
drop
a
version
of
of
of
node,
you
know
drop
support
for
a
version
of
node.
Then,
all
of
a
sudden
we
find
that
that
those
things
that
are
experimental
in
in
all
lts
all
remaining
lts
versions
of
node.
A
We
can
just
mark
them
as
stable
because
they've
been
around
for
a
whole
year
right
and
and
obviously,
if
we
change
them
and
if
there's
still
controversy
in
the
api
design
or
whatever,
we
won't
mark
them
stable.
But
but
if
they've
been
sitting
there
for
a
year
and
just
kind
of
been
used
and
okay,
maybe
a
few
bugs.
But
but
no
abi
issues.
Then
then
just
mark
them
when,
when
we
drop
where
we
drop
a
version
of
node,
so
basically
synchronize
the
the
stabilizing
of
various
apis
with
the
with
the
moving
forward
of
lts
releases.
A
B
I
was
just
going
to
say
gabriel.
The
advantage
to
that
is
we.
We
have
a
clearly
defined
cut
when
it
goes
out
of
experimental.
I
mean
we're
living
with
the
consequences
of
this
decision
with
that
old
note,
8
stuff,
and
so,
if,
if
it's
clear
enough
in
our
mind
when
it,
when
it
migrated
from
experimental
to
stable,
then
it
just
makes
long-term
support
a
lot
easier.
A
Yeah
yeah,
I
think
so
too,
right
and-
and
you
know
we
do
have
some
leeway
in
terms
of
in
terms
of
back
porting
stuff.
That's
that's
napi
related,
even
to
even
to
versions
that
are
in
maintenance.
For
the
sake
of
of
being
able
to
claim
that
this
thing
is
supported
in
all
lts
versions,
but
you
know
we
need
not
necessarily
make
use
of
that
right.
A
In
the
beginning,
it
was
useful
because
an
api
was
still
evolving
rapidly,
and
coverage
of
of
the
various
engine
and
node
functionality
was
was
still
being
added
very
quickly.
So
it
was
advantageous
that
we
had
this,
this
sort
of
extra
extra
slack
from
from
from
the
release
team
right,
but
now
that
we're
adding
apis
few
and
far
between
right,
it
may
make
sense
to
to
to
synchronize.
With
with
the
release
cadence,
you.
B
A
And
and
then
you
know
what
whatever
whatever
naturally
sort
of
trickles
back
through
the
back
ports
ends
up
being
the
release.
You
know,
so
that's
that's
what
I'm
thinking,
because
it
you
know,
we
always
have
this
problem.
A
Where
you
know,
if
you
mark
something
as
stable,
then
you
no
longer
need
nappy
experimental
right,
but
you
kind
of
still
need
it
anyway,
because
because
you
want
to
make
sure
that
you
have
it
right
and
if
you're
using
something,
if
you're
using
something
that
hasn't
been
backported
to
all
lts
releases,
then
you
still
kind
of
need
to
claim
that
you
support
version
node.
You
know,
starting
with
x
instead
of
x,
minus
two
which,
which
would
be
the
the
the
maintenance
lts.
A
A
If
you,
if
you
like
define
you
know
like
defining
defining
that
you
support
an
api
version
x,
is,
is
a
big
commitment
right,
because
you
you're
saying
I'm
not
going
to
use
any
of
the
new
stuff,
so
we
should
probably
make
it
easier.
You
know
when,
when
we
do,
when
we
do
bump
the
version
of
an
api,
then
we
should
always
bump
it
in
such
a
way
that
everything
is
backported
and
the
easy
way
to
achieve
that
is
is
when
we
drop
when
we
drop
a
like
a
release,
you
know
like
a
maintenance
release.
C
A
The
easiest
it's
the
easiest
time
to
bump
it,
because
we
can
just
check
you
know
we
have
this
okay.
Henceforth,
this
would
be
an
api
version,
n
plus
one
you
know,
but
anyway,
let's
talk
about
that
more
it's
just.
It
just
seems
to
me
that
that
you
know
an
api
is
starting
to,
like
version
seven
is
sort
of
starting
to
you
know
each
itch
the
surface.
You
know.
C
C
B
A
Okay,
what
do
you
all
think
is
that
does
that
cover
the
intention.
B
Yeah-
and
do
we
need
do
we
need
to
have
some
policy
on
the
move
from
experimental
to
stable
or
the
timing
of
that.
A
C
A
Okay,
that
cover
it:
yep,
yeah,
okay,
okay,
so
there's
that
okay-
and
this
was
because
we
were
looking
at
this
guy
and
then
back
to
here
and
close
the
tab
before
I
get
lost
in
my
own
tabs.
Okay,
so
yeah,
let's
see
okay
lucas
is
is
lucas
still
here.
Let
me
check
my
first
tab
and
I
can't
see.
A
Okay,
you're
still
here
great,
can
you
please
let
us
know,
is
there?
Is
there
anything
happening
in
the
in
the
make
call
back
and
in
asynch
hooks
context,
ambiguity,
situation.
E
I
don't
have
enough
with
it.
I
don't
have
accomplished
this
week's
problem,
I'm
planning
to
do
in
the
next
few,
especially
you
see
there
in
lunch
time.
I
came
before
so,
unfortunately,.
E
A
Yeah
no
worries
no
worries,
no
worries
and
thank
you
for
sticking
with
it.
Okay,
so
let's
see
here
this
one,
no
news
there.
This
is
long-term
discussion.
I
I
kind
of
bumped
it
a
little
bit
because
james
was
asking
and-
and
basically
just
let
me
see
if
he,
if
he
read
that
comment
and
maybe
answered
because
this
is
this-
is
like
one
of
those
things
here.
We.
A
Yeah
I
mean
an
api
stemver
major
yeah,
that's
yeah,
that's
going
to
be
a
doozy.
If
and
when
we
take
that
on,
and
we
don't
have
too
many.
I
think
we
only
have
two
issues
that
are
tagged:
an
api
somewhere
major,
so
so
yeah.
Those
are
you
know,
they're
we're
we're
chugging
along
without
them,
and
it's
not
exactly
the
end
of
the
world
that
we
don't
have
those
issues
fixed
but
yeah,
it's
good
to
keep
them
around.
A
Just
in
case
we
ever
do
redesign
things
so
back
here.
I
think
I
think
that's
pretty
much
it
so
we
only
have
a
few
minutes
left.
So
I'm
gonna
go
back
to
the
milestone.
All
right
note
sas.
I
believe
it's
status
quo.
Hopefully
they'll
have
some
time
to
resume
that
work.
This
is
also
status
quo.
Correct
me:
if
I'm
wrong
nicola.
A
Okay
and
then
reviewing
external
examples,
I
I
started
this,
but
then
I
had
to
restart
my
browser,
so
hopefully
yeah
I'm
gonna
go
and
have
a
look
at
this
and
and
see
how
far
I
can
get
that
it
seems
like
a
pretty
big
big
chunk
of
of
of
work,
because
you
know
I
mean
this
was
this
was
originally
supposed
to
be
for
the
pr,
but
since
the
pr
has
landed,
I
cannot
very
well
review
a
pr.
A
That's
already
landed,
so
I
was
thinking
of
just
filing
an
issue
just
reading
the
reading
the
files
out
of
out
of
the
actual
repo,
and
then
just
you
know
pointing
to
okay
at
this
line
in
this
file.
Maybe
it
should
be
like
this
and
not
like
that.
Those
kinds
of
it
would
be.
It
would
be
kind
of
nice.
A
Actually
if
you
could
review
a
branch
rather
than
rather
than
a
pr,
but
anyway
you
take
what
you
can
get
and
it's
probably
not
a
big
use
case
for
github,
but
anyway,
that's
what
I
was
thinking.
So
you
know
if,
if
you
all
have
any
any
more
cycles,
maybe
you
guys
can
also
add.
Add
your
comments,
but
anyway
I
think
I
think
that's
pretty
much
it
so
we
have
under
a
minute,
as
far
as
I
can
tell
so,
if,
if
anybody
has
any
issues
other
than
these,
then
please
speak
up.
A
B
A
quick
one
on
I've,
the
sqlite
three
project.
Yes,
somebody
filed
an
issue
because
it's
not
context
sensitive
and
so
I've
added
code
to
use
instance
data,
but
I'm
not
clear,
I'm
not
clear
if
it's
experimental
or
is
it
stable
at
this
point.
A
Let's
find
out
quickly,
I
believe
it's
an
api
six.
I
correct
I'm
going
to
correct
myself
if
I'm
wrong,
because
I'm
about
to
open
the
header
file.
A
B
A
Okay,
now
that
now
that's
that's
an
oversight.
So
so
you
know
if,
if
you
have
the
time,
feel
free
to
pr
that.
B
A
Awesome
awesome
all
right,
so
thank
you!
Everybody
for
attending
and
see
y'all
next
week,
if
I'm
not
mistaken,.