►
From YouTube: Node.js N-API Team meeting - September 27 2018
Description
A
A
And
we
have
two
guests
who
are
part
of
that
discussion
and
sort
of
will
kick
it
off
there?
I'm
sorry,
I,
don't
know,
I,
think
our
guests
can
only
type
so
I,
don't
know
Gabriel.
If
you
want
to
provide
some
context,
you
want
me
to
provide
some
context.
I'm
good,
either
way.
B
Sure
so,
basically,
basically
yazhong
came
forward
with
with
a
new
implementation
of
an
API
on
top
of
a
fork
of
Io
tjs.
If
that's
my
correct
understanding
and
the
issue
is
that
we
wish
to
establish
a
common
testing
infrastructure
for
the
two
implementations
of
an
API,
and
we
should
discuss
what
what
would
be
the
best
way
going
forward
for
that.
B
B
Yeah
yeah
yeah
no
GSR
snappy
tests
yeah.
That
would
be
the
way
to
go,
but
there
are
some
issues
with
how
we
should
maintain
that
package
and
the
repo,
because
our
tests
are
fairly
deeply
integrated
with
the
node.js
build
system.
So
so
then,
that's
another
part
of
the
discussion
that
we
need
to
have
right.
B
A
A
B
Right,
okay,
I
I'm,
not
sure
I'm,
not
sure
if
the
build
system
is
even
the
same,
because
I
believe
at
least
Jerry
script
uses
see
make
rather
than
rather
than
so
so
I'm
not
sure
what
else
will
be
needed.
So
so
you
was
young.
If
you
can,
if
you
can
tell
us
what
kind
of
build
system
is
being
used
by
shadow
node
is
it
is
it
see
make?
And
if
so,
how
do
you?
How
do
you
consume
NPM
packages
containing
native
modules?
That's
what
we
need
from
you.
B
B
B
Okay,
so
this
makes
it
very
similar
to
to
what
I
did
in
Jerry
script,
which
is
to
create
the
script
that
creates
a
C,
make
target
another
question
for
4
years.
Young
does
does
IOT
Jas
and
the
shadow
node
fork.
Does
it
ultimately
create
create
an
executable
that
contains
all
the
native
modules
statically
linked
or
or
is
it
able
to
do
dynamic
linking
at
runtime?
B
Is
it
able
to
load
modules
from
the
file
system
at
the
runtime,
because
Jerry
script
is
static,
is
fully
statically
linked
and
the
the
main
you
have
to
write
the
main
and
then
the
and
and
then
it
loads
static
libraries
which
for
which
you
can
add
library,
constructors,
and
so
it's
all
one
binary,
but
is
shadow
node
able
to
load
binaries
at
runtime?
Does
it
use
DL,
open.
B
B
I'm
gonna
check,
meanwhile
sure,
if
there
is,
if
on
the
shadow,
node
repo,
there's
okay,
so
so
the
question
again,
is
it?
Is
it
a
good
idea
if
we
add
a
script
that
after
which,
which,
after
extracting
the
the
test
suite
creates
see,
make
files
for
generating
dynamic
shared
objects?
Is
that
is
that
a
good
good
idea
to
add.
A
E
D
B
B
Yeah,
so
so
yeah
we
we
may
need
to.
We
may
need
to
stop
relying
on
things
like
comment.
R.J.
essences
like
that,
so
so
what
are
the
changes
are
required
besides,
this
is
a
question
to
you,
through
your
key
and
and
your
team.
What
other
changes
are
required
besides
creating
the
repo
that
contains
owning
the
test,
suite.
B
A
B
B
B
E
B
A
B
Can
move
forward
with
this
and
then
and
then
the
good
news
is
that
I'll
have
a
repo,
we'll
have
a
repo
in
which
to
discuss
issues
pertaining
to
to
this
common
infrastructure
and
all
that
so
so
that
that
should
give
us
more
than
just
a
repo.
It
gives
us
a
forum
in
which
to
you
go
back
and
forth
between
the
core,
repo
and
and
and
shadow
node
yeah.
G
G
The
the
the
the
person
who
reviewed
my
original
pull
request
has
requested.
Oh
there
we
go,
you
see
it
there.
Well,
no
on
the
mate.
It
doesn't
matter
on
the
main
page
anyway.
The
guy
who
reviewed
my
PR
has
requested
the
maintainer
to
to
take
a
look
at
it.
So
there's
it's
moving
forward,
just
very
slowly.
Okay,
so.
A
G
G
E
A
A
B
F
B
A
E
D
B
A
E
A
It's
a
good
idea:
do
you
by
chance
have
any
time
to
look
at
that
list?
I
can
probably
find
some
time.
Okay,
cuz,
yeah,
I.
Think
that
would
be
good
like
if
there's
some
good
candidates
in
there
to
say,
hey,
here's
a
case
cuz.
What
would
be
even
even
better,
you
know
sort
of
messages.
This
happened.
There
was
some
breakage
somebody
moved,
napi
and
and
now
they're
good
for
the
future.
A
F
A
F
G
A
E
E
A
A
D
B
D
B
So,
okay,
so
no
I
think
I
changed
that
so
that
it
it
does
like
like
cut
a
file,
so
yeah
yeah,
so
I
went
from
from
from
what
was
it
before
type
I
forget
what
the
original
was,
but
but
right
now
it's
okay.
So
it
creates
a
dot,
a
file
on
on
UNIX
and
a
dot
Lib
file
on
Windows.
So
in
either
case
does
it
creates
a
dot
note
file.
So
so
then,
so
then
the
checker
script
should
no
longer
need
to
filter
once
once
this
is
so.
This.
D
B
What
this
does
is
so
for
for
cases
where,
where
no
dad
on
API
finds
a
version
of
an
API
inside
nodejs
that
it
can
use,
then
the
then
this
dependency
targets,
this
jiff
dependency
target.
That
would
normally
cause
the
version
of
an
api
shipped
with
with
no
that
on
API
to
be
compiled
as
a
static
library
will
cause
nothing
to
happen,
but
because
of
the
way
generates
the
make
file,
it
will
still
create
a
target
which
results
in
an
empty
library
and-
and
so
basically
you
need
to
oh
wait.
I'm
wait
a
minute.
B
Yeah:
yes,
yes,
yes,
okay!
We
need
to
create
a
file
that
is
empty,
like
like
a
zero
bytes
C
file
and
give
that
as
the
source
so
that
when
it
creates
the
static
library,
it
has
a
source
file
out
of
which
to
create
it
because
otherwise
on
Mac,
it
just
fails
because
the
the
Mac
link
our
requires
at
least
one
input
file,
and
so
so
that
that
isn't
there.
Okay,
yes,
so
I
I
do
need
to
change
this.
B
This
should
be
very,
very
quick,
so
so,
but
yeah
that's
what
we
need
and
then
we
have
that
file
and
then
it'll
it'll
create
the
it
will
create
a
dot,
a
file
and
then
the
dot
a
file
has
the
wrong
extension.
It
doesn't
have
a
dot
node
extension,
and
so
we,
it
should
not
be
picked
up
by
the
by
the
checker
script.
Okay,
so
you're.
A
Okay,
so
we'll
say
that
one
I
figure
we
can
it
sounds
like
Roman.
Dev
is
gonna
push
on
that
this
weekend,
so
we'll
wait
until
next
week.
What
sounds
like
it's
coming,
which
is
good
and
then
this
one
it's
a
bit
big,
so
Gabriel
and
I,
and
whoever
else
comes
once
wants
to
stick
around-
are
gonna
go
through
it
after
the
this
beating,
okay,
so
I
think
that
sounds
like
we
should
be
getting
close
to
being
able
to
do
that
next
week.
A
H
A
Good
okay,
this
one
talked
about
this
one
I
think
we
touched
on
those
topics
for
NEP
I
collaborators
in
that
I
think
we've
talked
about
and
we're
we're
good,
creating
the
matrix
of
tested
methods.
Just
the
only
thing
I'll
mention
there
is
Andrew
was
working
on
some
code
coverage
generation,
so
I
pasted
it
in
this
PDF
which
I
guess
you're
not
gonna,
be
able
to
see.
But
let
me
change
the
sharing
of
that.
F
F
A
A
Like
because
there
are
there
only
inline
headers,
you
know
the
I'm,
not
sure
this
coverage
number
is
correct,
although
in
96
I
guess
it's
not
impossible,
but
you
know
the
places
that
don't
seem
to
be
covered.
I
did
some
sniff
test
thing
and
it
did
seem
like
they
were
actually
not
tested.
So
anyway,
I
did
I
didn't
want
to
take
too
much
time.
Just
want
to
show
that
so
that's
there
and
hopefully
we'll
get
to
the
point
where
you
can.
You
know
at
least
on
Linux.
A
You
can
generate
a
similar
coverage
report
just
by
running
one
of
the
targets
saying
it's
a
bit
tricky
like,
though
it
what's
there
now
would
do
it
all
the
time
which
I
think
might
get.
You
know,
it'd
be
like
a
50%,
more
testing,
which
is
maybe
not
great,
but
if
you
do
want
to
run
it,
it's
I
can
point
you
at
the
branch
that
you
could
do
it
from.
A
B
B
Okay,
I
haven't
had
time
to
to
move
forward
with,
with
the
plan
of
of
adding
a
like
a
similar
blurb
to
to
a
bi-stable
know
that
I
haven't
really
had
time
to
review
the
readme
there,
because
I
kind
of
I
suspect
I
need
to
prepare
the
readme
for
this
person's
contribution
to
arrive
there
and
I
haven't.
Had
it
do
that
yep.
A
A
Yeah,
no
problem,
okay,
so
no
update,
just
one
was
checked
through
discuss,
okay,
Humira
corner
session.
I
think
we
talked
about
and
we
were
good
note
coffee,
you
APN
api
workshops.
So
I
know
we
talked
about
this
in
one
of
the
meetings
Jim
suggested
we
added,
which
makes
so
maybe
we
should
spend
a
few
minutes
just
figuring
out
what
we
need
to
do
to
start
getting
prepared
for
that
right.
G
A
G
C
C
A
I
think
it
would
just
be
something
you
know
whether
through
you
and
when
it
starts
it
asks
you
which,
which
which
use
case,
do
you
want
to
follow
right
like
it
could
be
simple
or
object,
wrap
or
some
names
like
that,
and
then,
if
you,
you
know,
if
you
select
object,
wrap
it'll
do
what
it
does
today.
If
you
select
simple
it'll
generate
some
stuff,
but
it'll
be
basically
just
you
know,
AC
method
that
is
exported
on
an
object.
That
object
is
then
called
from
the
JavaScript
test
side.
I.
C
I'm
trying
to
get
it
into
the
chat,
apparently
copy
and
paste
is
not
there.
We
go
so
obviously
like
I
think
that
is
a
is
a
very
high
level.
Capturing
of
what
you're
looking
for
I
mean
honestly.
If
it
were
a
module
that
just
returned
hello
world,
that's
probably
wouldn't
actually
be
a
bad
like
that's.
That's
ended
with
the
interpretation
of
what
I
got
like
if
it
just
had
a
single
function
that
returned
the
string,
hello
world
and
we
tested
for
it
is
that
on
the
level
yeah.
D
G
D
C
B
B
B
A
G
G
G
A
A
G
F
B
B
A
B
E
B
Need
to
basically
look
at
at
files
that
that
are
part
of
an
API,
so
I
mean
anybody.
Who's
touched
like
SRC,
node,
API,
dot,
CC
or
dot
H
or
dark
API
napi
dot.
Md.
If
you
look
at
those
files
alone,
you
should
you
should
get
a
pretty
good
idea
of
who's
contributed,
so
I'll
go.
Do
that
now
for
for
the
main
repo
and
see
see
if
I
don't
get
anything
that
blows,
it's
gonna
be
a
long
list
of
names.
B
G
G
G
B
Yeah
I
just
pasted
another
command
for
for
the
node
main
repo.
It's
it's
a
rather
large
list,
because
I
mean
a
lot
of
the
contributors
have
or
a
lot
of
the
collaborators
have
also
contributed
to
to
an
API
since
then,
so
it
gets
yeah.
It
gets
an
shal
yeah.
A
B
A
G
A
A
half
even
yes
like
this
one
is
kind
of
broken
off
broken
out
in
that
there
is
a
an
hour
and
a
half,
then
there's
a
break
and
then
another
hour
and
a
half
right.
A
E
A
D
F
F
B
Anybody's
interested
in
I
mean
okay,
we
can
just
throw
it
out
there
like,
if
anybody's
interested
in
looking
at
thread,
safe
functions
because
it
I
did
get
I
did
get
a
pull
request
for
my
for
my
round
trip
example
and
since
I
put
it
online
and
so
I
sort
of
added
the
added
the
landed,
the
PR
inside
my
own,
my
own
fork
and
then
I
finally
get
dating
it
it'll
be
there.
So
there
was
at
least
one
person
interested.
It
was
a
it
was.
It
was
a
minor,
but
but
but
very
telling
change.
B
So
basically
they
they
they
replaced
the
they
replaced,
they
removed
the
binding
which,
which
would
retrieve
a
value
and
they
replaced
it
with
like
a
getter,
and
so
so
that
was
basically
their
attempt
to
to
ramp
up
with
an
API.
But
at
the
same
time
it
made
a
very,
very
important
and
and
sort
of
very
conceptually
sound
change
to
to
the
example
and
so
okay.
So
if,
if
if
either
that
person
or
persons
like
that
person
show
up,
then
I
would
be
happy
to.
B
A
E
E
B
B
F
D
A
A
F
A
A
H
H
H
H
A
A
B
B
Yeah,
yeah,
okay,
so
hours
hours
would
be
a
lot.
Less
would
be
a
lot
less
efficient
than
that
because
we
couldn't
wrap
v8v
AIT's
JSON
object,
because
we
would
have
to
go
through
an
API
to
do
that,
but
yeah
with
property
lookup
as
a
backup.
It
should
be
alright,
but
then
we
need
to
check.
We
need
to
check
what
kinds
of
modules
have
been
using
this
man,
because
you
know
they
may
expect
a
certain
kind
of
performance
which
they've
been
getting
with
nan.