►
From YouTube: Node.js N-API Team meeting July 5th, 2018
Description
A
A
A
It
includes
the
taking
any
P
outta
out
of
experimental,
which
is
important
and
I
also
suggested
at
another
few
back
ports
I
think
at
least
one
of
them
was
yours:
Gabriel
fixing
a
to
get
a
problem
as
well
as
one
that
I
fixed
in
terms
of
a
memory
leak.
So
if
there's
any
other
key
things,
you
think
need
to
be
back
ported
to
version
eight.
If
you
take
a
look
and
find
that
issue
and
comment
in
there
as
well.
B
You
know
the
API
surface
will
be
different
between
this,
with
between
the
supported
versions,
even
within
the
experimental
landscape
right,
because
if
we
land
something
is
experimental
on
ten
point,
O
or
ten
point
X,
then
then
it
is
not
available
at
all,
experimental
or
otherwise
in
earlier
versions.
Right,
so
so
there
is
still
a
so
there's
a
distinction
between
what
version
of
an
API,
including
experimental,
and
what
version
of
nodejs
has
that
version
of
an
API,
including
experimental,
so
I.
B
A
A
A
A
B
Actually
come
to
think
of
it
yeah
this
is.
This
is
one
of
the
implications
of
increasing
the
version
I
mean
if
we,
if
we
release
something
under
under
some
new
and
API
version
other
than
experimental,
then
then
I
suspect
we
should.
We
should
always
keep
an
eye
on
whether
we
want
to
back
port
this,
because
there
may
very
well
be
a
strong
desire
to
have
this
new
newfangled
and
API
version
available.
On
all
available
note
version
yeah,
okay,.
A
C
B
A
You
know
it's
just
gonna
happen,
but
yeah
I
think
when
we
whenever
I
think,
that's
that's.
Why
it'll
be
good?
Do
you
know
since
if
thinks,
if,
basically
things
get
promoted
from
experimental
into
an
app,
you
version
release.
That's
the
perfect
time
to
think
about
okay,
and
where
does
it
make
sense
to
back
port
that
particular
content
right.
B
And
which,
which
ones
to
put
into
the
degree
to
the
release
as
a
function
of
whether
they
can
be
back
ported
and
and
how
much
way
to
do
we
place
on
on
this
damn
and
so
forth?
Okay,
all
right!
Okay!
Well,
we'll
be
there
at
some
point.
Yeah
we've
already
got
some
accumulation
in
experimental
now,
yeah.
A
We
have
some
an
experimental
and
we
have
a
couple.
We've
still
got
to
figure
out
whether
we
should
move
into
experimental
in
yes
or
not,
because
we're
kind
of
it
we're
we're
a
little
bit.
I
wouldn't
say
broken,
but
it's
an
we're
in
a
position.
We'd
prefer
not
to
be
where
there's
a
couple
that
are
not
in
an
app.
You
didn't
get
a
proper
nappy.
B
A
So
that's
kind
of
our
growing
pains,
but
we
will
yeah.
We
will
see
I
mean
I
guess.
The
the
risk
today
is
is
that
if
we
do
that
the
way
it
is
now
you
could
build
against
a
later
version,
then
that
wouldn't
actually
run
against
an
earlier
version,
because
you're
using
those
particular
functions,
yeah.
B
A
B
A
B
B
A
B
B
A
B
B
B
B
A
What
you
already
the
you
know,
the
only
changes
really
are
gonna,
be
that
it's
actually
marked
as
non
experimental.
Yeah,
that's
good,
and
then
it's
we've
got
a
couple
bug
fixes
that
can
go
in
excellent.
Otherwise,
it's
like
it's
the
same.
It
doesn't
really
change
anything
for
people
other
than
it's
officially
non
experimental,
which
is
what
we're
gonna
then
say.
You
know
trumpet
good
stuff.
A
Okay.
The
next
item
was
creating
workshop
for
notes,
somewhat
I.
Think
we'll
just
leave
that
to
the
end,
because
I
think
we
plan
to
stick
around
and
work
on
that
anyway.
So
probably
worth
doing
that
document
guidance
on
adding
API
is
2n.
Api
sohe
Tesh
had
put
together
a
list
and
he
was
gonna
get
somebody
he
was
away.
So
he
was
gonna,
get
somebody
else
to
open
a
PR.
I
haven't
seen
it
yet.
Does
anybody
else.
B
Week
we
we
kind
of
we
kind
of
agreed
that
it
would
be
a
PR
and
we
were
kind
of
debating
where
it
should
go
and
I
believe
if
I
remember
correctly,
our
our
sort
of
consensus,
whether
that's
going
to
guides
like
there's
dark
guides,
and
then
that
would
be
a
good
place
for
it
and
give
us
give
us
something
we
can
refer
to
whenever.
Whenever
somebody
opens
a
issue
or
a
PR.
That
yeah.
C
A
C
A
A
So
he'd
suggest
putting
them
into
guy
right.
So,
basically
yeah.
Maybe
you
were
on
that
email.
So
it's
the
doc
just
be
a
doc
and
guides
contributing
and
then
link
it
off
to
contributing
or
collaborator
guides.
Yeah
yep,
so
I
haven't
seen
that
PR
go
through
yet,
though
I
don't
know.
If
anybody
else
has
seen
it.
If
he
touch
doesn't
have
time
for
it,
I
can
I
can
do
the
PR
yeah
I
was
gonna
volunteer
to,
but
he
said
he
would
get
somebody
else
to
do
it.
Oh
okay,
so
he
said
Jimmy
will
open
it.
A
A
D
A
E
A
E
A
E
A
Sounds
good
cuz,
yeah
I
would
be
good
to
give
that
to
him
as
well.
Cuz
I
think
it
should
be
clear
what
the
suggestion
is
for
the
the
other
two
and
then
but
yeah.
Maybe
if
you,
if
we
can
go
over
on
Monday
and
even
give
them
the
updated
PR
that'd
be
great.
Okay
sounds
good
I'm
just
for
everybody
else,
the
end
30
to
check
you
know
we
did
look
at
the
v8
code
and
it
didn't
look
like
it
was
doing.
A
Think
special
like
it
wasn't
retaining
any
state
that
let
it
tell
that
it
was
an
in
32.
It
was
just
doing
a
check
on
the
you
know
doing
some
math,
oh,
so
we
figured
we
can
do
that
math
just
as
well
yeah.
So
that's
the
way
that
Aneesh
has
been
pushing
it
forward,
investigate
use
of
pre
build
within
API.
Yes,.
C
C
C
D
A
A
B
A
B
A
B
B
B
Does
that
that
we
should
integrate
the
solution
into
an
API,
because
he
was
suggesting
that
maybe,
whenever
we
get
a
buffer
for
an
external
buffer
for
which
we
know
the
size,
we
should
inform
v8
that
that
you
know
so
much
more
memory
has
been
added,
and
so
perhaps
it
should
GC
more
often
because
if
we
do
it,
but
then
module
owners
who
are
aware
of
this
marine
reporting
also
do
it
and
then
our
we're
giving
v8
a
more
pessimistic
picture
than
yes.
So.
A
I
think
we
should
look
at
that.
There
are
places
in
the
VMware.
That's
automatically
done.
Oh
really,
yeah
I
thought
already
when
you
like,
say
you
Zeeland.
So,
for
example,
when
zeal
abuses,
memory
internally
yeah,
it
will
automatically
adjust
the
memory
to
try
and
help.
Tell
that
you
see
what's
going
on.
Okay,.
B
Right
right,
but
from
the
point
of
view
of
the
VM
Zed
Lib
is
just
another
add-on
right,
and
so
so
in
that
sense
it
is
the
add-ons
responsibility
to
make
these
announcements
right.
So
so
then,
so
then
you
know
if
we're
dealing
with
somebody
else
is
like
a
third-party
add-on.
There
I
think
it
should
be
this
way,
because
if
we,
if
we
start
internalizing
this
into
an
API,
then
it
is
as
if
the
VM
itself
did
it
automatically
right.
But
if
you
use
v8
and
it
doesn't,
do
it
automatically
right.
B
B
D
B
B
A
B
B
A
B
You
mean
the
note
add-on
API
code.
Yes,
so
oh
there
are
many,
but
there
are
actually
places
where,
where
I'm
not
actually
sure
how
we
will
ever
do
that,
like
we
keep
allocate
some
some
function,
call
back
stuff
that
we
simply
to
do
free,
but
we
didn't
actually
do
that
so
yeah,
that's
not
so
good.
No,
it's
not,
but
for
now
I
think
we
are
safe
because
v8
itself
doesn't
doesn't
garbage,
collect
anything
that
has
a
native
back-end.
So
so
we
wouldn't
actually
ever
be
called
upon
to
free
that.
A
A
B
D
B
C
C
B
A
C
A
A
A
B
B
A
B
A
A
A
So
yeah
so
yeah,
so
yeah,
okay,
so
yeah.
If
you
can
comment
in
there,
okay,
though,
that's
good,
so
it
sounds
like
there's
nothing
really
to
investigate.
We
understand
the
issue.
We
just
need
to
document
I'll,
take
the
option
to
add
some
documentation
around
them,
but
if
you
can
just
comment
sort
of.
A
Okay,
that's
good
good
week
glad
we
had
that
discussion
because
we
can
solve
it
answer
the
thing
and
clarify
what's
going
on
without
spending
too
much
time:
okay,
I'm,
sorry
I'm
trying
to
get
back
to
where
was
it
milestone
there
we
go
documentation
push
so
we
have
landed
a
few
more
things.
So,
let's
take
a
look.
I
think
we
want
to
spend
some
time
looking
at
that
today
too.
So,
if
we
look
here.