►
From YouTube: 2020-10-09-Node.js N-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
A
A
A
B
Do
you
think
go
ahead?
I
had
some
questions
because
in
this
section
about
new
features
and
functionalities,
it's
like
to
mama
in
my
mind,
is
pretty
technical
and
I
don't
want
it
to
sound
too
tutorialy.
B
A
I
yeah,
I
think
I
do
I
think
like
in
my
mind.
It's
not
you
know.
We
don't
want
to
get
into
necessarily
code
samples
or
anything
like
that.
It's
more
like
to
highlight
here
the
new
things
you
can
do
or
do
more
easily
that
you
couldn't
before
and
then
maybe
a
link
off
to
the
actual
examples
in
the
examples,
repo
or
somewhere
else,
if
there's
docs.
A
B
Okay,
yeah,
that
makes
that
makes
sense.
Okay
and
then
that
second
comment
that
I
had
I
yeah
it
makes
sense
to
show
like
call
out
the
projects
that
use
these,
I'm
just
having
trouble
finding
them
on
github.
I
can
just
I'll
continue
looking
it's
just
that,
like
my
method
of
searching
for
them
is
by
searching
for
the
methods
like
an
api.
C
B
B
Are
so
I
just
need
to
take
some
time
I
guess
to
like
re
research,
these
projects
to
see
if
they
are
big
enough
to
be
listed
as
because
I
think,
on
the
very
bottom
of
this
document
we
had
listed
some
other
projects
right
sure
yeah,
so
trying
to
find
like
those
are
big
names
right.
So
I'm
trying
to
get
some
bigger
name
ones,
and
you
know
like
thread
say:
functionality
is
a
big
feature,
so
it
just
have
to
take
a
while
to
find
one.
B
Absolutely
okay,
yeah
and
then
that's
pretty
much
all
the
questions
that
I
had
and
then
I've
just
been
working
on
the
other
sections
and
just
continuing
to
flush
them
out.
A
Okay,
that's
that's
good
any
questions
from
other
people
in
terms
of
moving
forward
sections
that
are
like
people
think
are
done
or
what's
just
sort
of
figuring
out
what,
if
anything,
we
should
talk
about
this
week
on
this
front.
D
I
see
how
kevin
has
used
the
links
on
the
github
doc,
and
so
this
this
week
I
will.
I
I
put
the
I
put
the
links
in
line,
and
so
this
week,
I'll
I'll
adopt
the
method
that
kevin's
used
for
setting
up
the
linking
which.
A
D
E
D
Cmake,
if
you
go
to
cmake
yeah,
see
see
how
I
put
the
the
url
in
parentheses,
behind
it.
I'll
put
that
into
the
note
I'll
put
do
the
linking
correctly
like
michael,
like,
like
kevin,
has
done.
A
F
A
A
D
A
A
A
I
think
I
saw
that
kevin
you're
going
to
going
back
and
forth
a
little
bit
with
gabriel
in
terms
of
review
and
updates.
B
Yes,
the
so
we
had
talked
last
week
about
because
he
had
some
confusion
of
the
ref
and
unref,
and
we
we
resolved
that.
So
then,
all
of
the
majority
of
the
updates
are
documentation
and
formatting,
I'm
finishing
that
up
today.
Okay-
and
I
think
that
should
be
good
to
go.
A
Okay,
so
that's
good
and
you
know
I
think
we're
then
would
be
on
track
to
put
out
release
three
one,
which
would
be
good.
Sorry,
I'm
going
back
to
issues
here.
We
go
otherwise,
unless
anybody
has
anything
to
call
out
on
that.
Let's
just
look
at
the
pr's.
Sorry
go.
E
C
Yeah,
the
pr
introduced
a
state
sci
checks
on
the
incremental
the
change
lines
of
the
source
code,
so
it
will
only
tend
to
check
the
tangent
lines,
but
not
the
other
part
of
the
file.
Since
we
are,
we
have
mostly
the
two
files.
We
don't
have
to
format
the
whole
files
immediately,
so
only
they
change
your
nice.
A
A
A
A
B
B
Or
is
in
their
so
the
comment
that
he
actually
made
was
a
for
a
snippet
in
my
re
in
the
readme
markdown,
and
I
guess
because
I
did
I
maybe
I
don't
have
auto
format
on
save
or
something
for
those.
Maybe
I
do
on
the
javascript
files.
Who
knows
so
then
he
made
a
comment
about
the
formatting,
for
that
example,
and
then
it
just
made
me
think
of
okay.
Well,
do
we
have
any
you
know
just
like
eslint
rules
or
is
eslint
formatting
yeah.
A
B
A
Okay,
yeah,
I
didn't
so
so
on
this
one
in
particular,
I
guess
I
what
I
what
I
was
wondering
about
was
like
you'd
mentioned,
that
there
was
like
30
cave
lines,
but
this,
but
this
is
basically
incremental.
So
it's
not
actually
going
to
have
a
huge
change.
It's
just
going
to
make
mean
that
we
slowly
move
in
the
right
direction
right
yeah.
Does
anybody
have
any
concerns
in
that
context,.
F
Yes,
it's
something
that
developer
need
to
to
follow
right,
it's
a
standard
that,
but
what
happened?
If
I
don't
follow
these,
this
is
the
standard
and
I
made
up
a
request.
F
So
we
have
an
automatic
check
on
the
power
request.
Yep.
A
C
A
You're
sort
of
breaking
come
here
yeah.
I
know
we
didn't
hear
you
the
last
minute
or
so.
C
B
B
B
Yeah
like
because
base,
because
instead
of
running
you
know
npm
run
test,
it
would
do
like
npm
run
lint,
and
if
that
one
fails,
then
the
build
would
fail,
but
it
would
be
separate
from
the
build
that's
running
npm
test,
which
is
running
on
all
the
different
environments
that
we
have.
You
know
linux
mac,
whatever
the
the
one
that's
running,
npm
run
lint
only
has
to
run
on
one,
but.
A
B
B
Which
point
I
think
that
is,
I
think,
that's
standard.
I
mean
that's
how
my
my
company
does
it.
We
also
have
a
pre-commit
hook
that
like,
if
you
try
to
commit
it,
runs
the
linter
right
as
a
pre-commit
hook.
We
can
probably
investigate
in
adding
that
too,
because
it's
just
to
get
an
npm
package
pre-commit.
A
B
But
I
mean
I,
it
makes
sense
to
me
how
it
is
right
now,
with
the
addition
of
possibly
adding
the
pre-commit
hook.
That
would
run
npm
run.
B
A
A
Of
those
two
would
mean
we
would
we
would
we
should
catch
it
in
the
the
like
in
our
in
our
pr's,
and
developers
should
see
it
when
they're
working
locally.
C
Headed
about
adding
a
brick
meet
hook
to
the
of
the
linters,
since
all
the
git
clan
format
and
make
test
make
linked
in
the
in
the
no
core
will
prompt
up
in
to
not
to
in
the
command
line,
to
saying
that,
if
you
have
files
not
staged
yet
it
will
prompt
up
the
line
to
indicate
you
have
to
state
first
and
then
you
can
run
the
linkers.
It
will
ensure
that
your
code
will
not
be
overwritten
by
the
interest.
A
B
B
D
E
C
Be
disabled
locally
or
we
have
to
install
it,
install
it
with.
B
C
B
Right
so
it
would
be
beneficial
because
it
would
stop
pr's
from
being
created.
That
we
know
would
fail
because
the
ci
would
fail,
so
it
would
stop
a
developer
from
creating
a
pr
that
is
bound
to
be
rejected,
and
then,
with
the
pre-commit
hook,
you
can
still
force
the
commit
to
succeed,
even
if
the
command
fails.
B
So
it's
so
you
still
have
the
flexibility
of
still
making
the
commit
and
still
pushing
it.
If
you
want
to
it's
just
and
the
way
that
you
configure
it
is
it's
just
like
a
package
that
you
install
and
then
you
add,
like
the
command
in
your
package,
json
for
what
you
want
it
to
run
before
committing.
B
So
it's
it's
pretty
simple
and
I
think
it
would
be
be
good
because
then
we
could
add
the
linter
command
and
then,
if
we
add
figure
out
what
we
want
for
our
javascript
linter2,
we
can
add
both
of
them
and
then
everything
would
be
formatted.
B
B
E
F
I
just
I
I
wouldn't
say
that
yeah
I
I
prefer
a
permissive
approach,
so
yeah.
We
should
give
a
suggestion,
but
we
should
not
stop
to
to
commit
or
create
upper
records
because
at
the
end
we
always
have
the
the
ci
that
add
us,
like
maintainers,
to
yeah,
to
see
that
there
is
a
on
errors
on
on
so
on
the
code.
So.
B
B
Things
two
things
first
would
be
when
you
do
the
commit
and
if
the
linter
fails,
the
git
will
say
the
command
failed.
If
you
want
to
run
it,
anyways
run
this
command,
and
then
you
just
copy
and
paste
the
one.
That's
like
it's
a
switch
that
says
no
verify
so
it
just
skips
the
commit
clicks,
yeah,
okay
and
then.
Secondly,
when
you
said
that
we
still
have
the
ci
that
would
run
it.
B
Yes,
the
ci
would
run
it,
but
since
it's
running
the
exact
same
tests,
it
would
fail,
you
know,
so
it
would
just
be
like
it
does.
It
doesn't
really
make
sense
to
push
a
commit
that
you
know
the
ci
would
would
fail
if
that
makes
sense,
but
you
still
have
the
power
to
do
it.
If
you
want.
B
Okay,
yeah
so
I'll
push.
I
I'll
make
some
comments
on
this
and
I
can
even
make
a
branch
out
of
this
with
the
pre-commit
hook
added,
and
then
you
guys
can
like
check
out
that
branch
and
see
how
it
behaves.
A
E
A
A
F
A
F
F
E
F
Innumerable
is
yeah,
it
is.
F
F
A
F
I
think
that
it
it's
it
works
without
not
be
underscore
not
be
innumerable.
So
all
right,
yeah,
it's
not
necessary.
E
F
And
later
I
I
I
can
comment
to
be
sure.
A
A
If
you
remember
that,
yes,
that
discussion,
I'm
just
wondering
like
in
an
example,
would
it
be
better
to
show
a
default
that
actually
gets
you
something
that's
closer
to
javascript
versus
like
no
like
no
access.
F
F
But
in
example,
or
in
in
our
code.
A
F
A
F
Yes,
yeah
yeah
people
just
copy
and
past
the
the
example
yeah,
and
so
maybe
we
can
start
into
documentation,
yeah
and
then
in
the
and
I
don't
know
maybe
in
the
next
major
version.
We
can
do
this
in
in
the
code.
So
maybe.
F
A
F
Yeah
for
sure
we
will
break
yeah,
so
yeah.
A
F
It's
a
choice
to
be
more
near
to
the
javascript
standard
or
maybe
lived
things
like
they
have
to
die.
A
F
F
These,
but
I
didn't
have
the
the
time
to
take
a
look.
A
B
A
E
A
A
C
Yeah
some
a
few
people
have
commented
on
the
pr,
so
I
will
update,
according
to
the
reviews,
perfect.
A
Okay,
so
otherwise,
I
don't
see
anything
to
jump
into
there.
Let's
look
at
pull
requests.
A
A
A
So
I
guess
that's
it
from
the
issues.
Is
there
anything
else
that
we
think
we
should
talk
about
this
week?.
A
No
okay!
Well,
thank
you
for
everybody
who
took
the
time
to
join
and
we
will
see
you
in
github
and
next
week.
Actually,
I
won't
be
here
next
week.
It's
it's
a
a
day
off
for
me,
so
I've
I
in
email,
asked
gabriel
to
to
chair,
hopefully
he'll,
be
able
to
do
that.
If
not
all
I'll
reach
out
to
one
of
you
other
one
of
the
other
team
members
to
see
if
they
can
do
that.
B
A
He
responded,
he
said
he
can
do
it,
okay,
great
so
yeah.
So
I
won't
see
you
the
next
week,
but
I'll
see
you
in
github
and
two
weeks
from
now.
Okay,
thanks
talk
to
everybody
later
bye-bye.