►
From YouTube: Node.js N-API Team meeting - Sep 4 2018
Description
A
B
A
A
Okay,
so
this
is
an
issue
we
discussed
last
week
about
investigating
how
NEP
I
might
have
helped
avoid
some
of
the
breakages
that
were
reported
in
to
274,
as
we
attempted
to
upgrade
to
node
attempted
to
upgrade
to
version
7
nitesh
posted
in
a
nice
summary
that
came
from
jail,
grace
in
terms
of
the
modules
that
were
impacted
and
it
does
sound
like
a
number
of
them.
We
have
either
started
or
I
thought
about
doing
ports.
A
C
A
A
Sqlite
port,
so
I
did
meet
with
her
with
Anisha
this
week.
Unfortunately,
it
actually
seems
to
be
a
bit
more
complicated,
so
she
hadn't
made
any
progress
in
figuring
out
the
actual
hang.
But
when
we
were
looking
through
the
code,
the
one
thing
I
noticed
is:
it
was
actually
still
using
libuv
directly
to
do
a
bunch
of
its
asynchronous
work.
So
we
really
have
some
more
work
there
before
I
think
we'd
call
it
an
API
port.
A
So
what
we
agreed
was
she
should
go
back
and
look
at
pulling
out
the
the
use
of
libuv
and
replacing
it
with
what
we
have
in
no
data
on
API
and
potentially
even
some
direct
calls
into
an
API,
and
then
you
know
we'll
see
at
that
point.
If
it's
related,
it's
it's
I,
wouldn't
be
terribly
surprised
if
it
was
related.
In
terms
of
you
know,
we
have
done
things
like
not
be
fatal,
exception
and
stuff,
because
you
have
to
do
some
special
things
for
AC.
A
You
know
when
exceptions
happens,
asynchronously,
and
so
the
problems
we
were
seeing
may
be
tied
in
with
the
fact
that
we
were
still
using
the
PV
directly
in
those
few
places.
So
that's
where
we're
at
on
that
one
I'm
burning
down
the
list
of
issues
raised
by
module
owners,
I,
don't
I'm,
not
aware
of
any
I,
don't
know
if
anybody
else
has
looked
and
seen
anything
new
recently
that
we
should
discuss
no.
A
A
Is
there
we'll
come
back
to
that
afterwards
as
a
sort
of
a
high-level
list
of
what
we
should
do
in
this
milestone,
but
we
don't
necessary:
have
issues
open
for
creating
the
matrix
of
tested
methods,
so
I,
don't
think,
there's
anything
necessarily
new
specific
in
that
ap
in
that
issue,
except
that
we
are
starting
to
see
a
few
contributions
to
to
add
to
the
coverage,
which
is
great,
so
I
think
we're
making
progress
on
that
front
anything
else.
People
want
to
comment
on
that.
One.
B
B
A
A
B
B
A
B
A
C
C
D
C
C
A
A
C
A
A
B
A
A
What
we've
done
for
other
reposes
actually
followed
a
process
where
we've
said
you
know
we're
gonna,
post
a
post,
an
issue
and
app
mentioned
everybody
in
that
issue.
That
says:
hey.
You
know
we're
doing
a
membership
review
just
ping
here.
If
you
know
you
still
plan
to
be
active,
alright
and
if
somebody
says
hey,
yeah
I
still
plan
to
participate,
then
they
stay.
A
If,
after
two
weeks
we
haven't
heard,
we
then
remind
people
and
there's
another
two
weeks,
and
so
basically
you
know
if
there's
somebody
who
doesn't
even
respond
after
four
weeks,
then
we'll
move
them
to
emeritus
and
if,
for
example,
they
came
back
within
the
next
month,
it's
still
like,
oh
yeah,
sure
you're
back
in
right.
Right.
A
That'd
be
great,
cuz,
I.
Think
it's
just
a
nice
independent
neutral
way
of
you
know,
saying:
hey
who's
still
involved
and
if
you're
not,
then
then
we've
moved
the
people
to
emeritus
is
still
like.
You
know
the
thank
you
for
having
participated,
but
right
it
gives
a
more
accurate
view
of
who's.
You
know,
participating
day
to
day,
okay.
A
C
A
That
that's,
like
could
basically
say.
Well,
you
know
now
that
any
P
I
is
in
core.
You
know
it's
just
there's
been
lots
of
contributors,
you
know
making
changes
across
the
board.
We
won't
list
them,
but
also
you
know
and
know
that
on
API
here
are
here
are
some
contributors
that
we
see
going
and
and
okay
there.
That
means.
C
A
D
We
haven't
made
any
progress
on
that.
Yet
I
can
take
a
look
and
see
if
I
can
take
a
stab
at
it
over
the
weekend
and
see
if
I
can
get
something
done.
The
like
I
was
I
did
make
a
pass
at
just
getting
dependencies
cleaned
up
on
it.
It
was
a
little
bit
like
broken
I
still
using
the
old
node
security
package
or
whatever
it
is,
which
apparently
has
been
deprecated
NSP
yeah,
okay.
They
apparently
got
rid
of
it
in
favor
of
just
note.
Our
npm
audit
yeah.
D
C
D
D
A
A
A
Since
then,
it
has
a
bit
more
of
the
back
with
like
code
sample
shape
to
the
API
I
added,
a
very
simple
demo,
which
just
it
uses
the
demo
that
we
used
before,
but
it's
pre-recorded
and
is
about
a
minute
where
it
just
starts
up
with
and
without
any
PI,
showing
that
well
look
with
with
an
API.
You
can
nvm
up
to
version
10
if
you're
upgrading
from
Aden
it
just
works.
Oh,
but
if
you
do
the
same
thing
with
a
non
API
version,
it
just
falls
over
telling
you.
A
You
know
you
have
a
version
mismatch
so
and
then
a
little
bit
of
reordering
stuff
but
I,
don't
think
there'll
be
any
real
surprises,
not
the
birds
of
a
feather.
We
talked
about
the
breakout
session.
We
talked
about
bit
badges
Brooke
shop,
yeah,
the
node,
add
on
examples.
So
I
know.
Actually
that's
a
good
one.
Gabriel
you've
basically
done
that
yeah
I.
C
B
C
B
The
actual
reference
so
yeah
I
need
I
need
the
reviews
for
that
one
for
those
three
PRS
I
guess
and
then,
and
then
we
can
go
with
those
and
actually
I
was
thinking
for
the.
Let
me
remember
yes
for
the
last
one
for
for
this
multiple
loading
one,
we
could
actually
add
links
to
those
examples
to
the
to
the
reference,
because
the
the
documentation
for
both
of
these
macros
they
they
do
mention
that
that
they
are
there,
so
that
modules
might
be
context
aware,
and
so
so
this
context
awareness
is
also
shown
by
this
example.
B
So
we
could
link
back
to
the
example,
though
I'm
not
sure
what
what
the
what
the
policy
has
been
of
late.
Since
we
had
archived
the
examples,
then
I
suppose
the
links
from
the
API
reference
have
disappeared
in
favor
of
just
embedding
the
examples
literally
into
the
reference,
but
now
that,
now
that
the
repo
is
back,
we
could
start
linking
to
it
or
not.
I,
don't
know
what
what
the
general
feeling
will
be
about
that
yeah.
A
A
C
B
A
A
B
A
B
D
A
B
A
B
B
A
B
A
B
B
A
B
A
A
A
B
A
A
B
Before
8.6
yep,
so,
but
as
those
start,
edging
closer
to
you
know,
being
unmaintained
will
node
add-on
api,
eventually
transition
into
not
no
longer
providing
like
like
a
static
version
of
an
api.
I
would
say:
yes,
you
know
I
was
thinking
like
we
could.
We
could,
on
the
other
hand,
I'm
not
sure
if
this
is
feasible,
but
we
could,
on
the
other
hand,
maintain
this
this.
You
know
we
do
everything,
tell
us
that
you
don't
have
in
perpetuity.
B
C
B
A
B
B
A
And
so
yes,
I
think
there
we
just
our
action,
was
to
as
well
look
through
some
of
the
old
issue,
see
if
we
can
kind
of
prune
those
yeah
and
then
finally,
the
last
bit
was
expanding.
The
test
suite,
which
I
think
we
already
talked
about
so
I,
think
we're
we're
doing
pretty
well
on
the
content
we
had
for
the
milestone
any
other
issues.
People
want
to
talk
about.