►
From YouTube: 2022-05-27-Node.js Node-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
D
D
A
We
could
have
like
another
ci
job
that
that
basically
ran
and
even
like
I
know
I
think,
like
you
know,
there
was
work
to
to
push
the
results
to
something
like
coverage.io
or
one
of.
A
E
Yes,
I
I
didn't
make
progress
this
week
on
it,
but
yeah
the
plan
is
actually
move.
Is
I
have
this
proxy
example?
Is
a
part
of
node.js
unit
test
the
planners
actually
move
to
node
api
examples
instead,
yeah
I'll
do
it.
Every
second
sounds
good.
Okay,.
B
A
B
A
The
stale
ones
that
we
needed
to
discuss
looking
at
modules
that
were
ported,
I
don't
see
anything
new
there.
We
can
always
look
up
npm.
A
A
So
I
can
open
that
up,
but
anyone's
in
particular
that
people
want
to
have
us.
Take
a
look
at
to
start
out
with.
E
Yeah,
we
discussed
last
time
one
of
these
issues.
It
was
a
question
mostly
how
to
use
typed
array-
and
I
have
submitted
pr
out
today
morning
about
as
an
example
like
this
second
one
in
this
list.
Sorry,
this
one:
okay,
oh
no,.
E
E
E
So
if
you
scroll
to
the
bottom,
I
had
to
edit
this
pr
how
to
demo
how
to
read
a
unit
8
array
and
how
to
create
it.
E
Just
as
a
demo
a
cup
it's
this,
this
one
is
just
about
bytes,
but
I
can
add
also
about
like
doubles
or
like
in
32
as
well.
E
Another
one
about
this
iterator
kevin
submitted
also
example
for
this
asynchronously
trader
and
we
also
swan
team
two
yeah.
I
think
the
next
one
number
four
in
this
list
for.
A
A
A
C
B
F
B
Yes,
I'm
tempted
to
go
and
just
say
this
is
stock.
Note
api.
F
So
she
need
to
remove
a
native
action
from
from
the
docks
and
that's
it.
G
A
F
Yeah,
because.
F
For
a
form,
someone
added
the
the
nappy
version
on
yeah
yeah-
that
is
not
part
of
any
right
version,
so
yeah,
okay,
so.
B
So
if
you
want
to
just
just
you
give
me
some
segments
yeah.
B
G
There
is
one
comment
that
I
haven't
updated:
another
one
gabriel
said
it
and
it's
probably
a
style
change.
We
just
move
piece
of
code
up
and
or
down
it's
just
in
it,
but
I
found
that
since
we
are
exposing
the.
G
A
C
E
Okay,
it's
number
three
like
it's
a
ref
type
as
yeah,
which
I
updated
it
yesterday
so
think
it
should
be
good
to
go.
But
I
would
like
you
guys
to
review
the
names,
because
I'm
right.
A
A
G
E
G
G
Sorry
yeah,
I
just
found
the
name
in
your
enumeration
name
in
various,
is
very
similar,
so
I
just
had
a
hard
time
implementing
the
meaning
of
the
name.
So
I
probably
I
will
comment
in
the
issue,
but
it's
not
a
big
deal,
since
my
name
is.
G
A
A
E
It
would
be
nice
if,
because
I
I
feel
like
it's
pretty
much,
I
have
documentation.
I
have
tests,
I
have
pretty
much.
I
probably
just
need
to
update
a
little
description
here.
I
see
a
little
bit
updated,
but
the
rest,
I
feel
like
it's
good,
to
kind
of
it's
ready
to
review
and
right
submitted
if
you,
if
it's
okay.
G
So
that
is
right,
number
four
another
another
naming
issue
I
found
in
the
piano
from
vladimir
in
another
pr
is
that
it's
split
analyzes
into
two
different
types.
G
Yeah
right,
they
are
named
in
a
way.
We
let's
say
not:
api
rock
and
the
node
api
click
create
external,
but
we
have
already
have
this
series
or
appear
in
name
like
and
and
not
be
rather
not
equipped,
it's
kind
of
java.
I
find
that
they
are
very
similar
and
I
I
don't
have
we.
I
feel
we
don't
have
any
questions
for
such
naming
and
adjustment
that
it
might
be
a
hard
time
for
people
new
comments
to
the
note
api.
G
They
might
have
to
distinguish
why
these
two
functions
are
named
very
similar
just
because
just
for
they
have
different
prefixes,
but
they
act
differently.
E
Right,
I
remember
we
had
the
meeting
about
like
probably
about
five
six
weeks
ago
and
I
think
it's
well.
We
discussed
about
this
name
and
conventions.
I
believe
in
this
meeting
as
well,
and
this
is
what
he
suggested,
because
we
extending
this
apis
with
new
functionality
and
proposal
was
like,
let's
just
because
we
want
to
have
all
new
apis
to
have
his
node
underscore
api,
prefix
and
suggestion
was
actually
just
have
exactly
the
same
names
as
before.
Just
different
metrics.
G
I
I
was
thinking
that
deprecating,
the
previous
one
might
be
very,
might
be
good
to
the
answer.
I
I
just
forgot
about
depicting
the
previous
one.
G
G
A
C
C
E
A
A
A
A
Right
yeah,
maybe
we
haven't
deprecated
as
much
here,
but
there
is
a
standard
deprecation.
A
A
E
A
A
Well,
there's
yeah
and
that's
depending
on
our
on
our
like:
we
can
do
docked
applications
or
we
can
actually
have
them
so
that
they
throw
warnings.
A
I
might
be
more
tempted
since
we're
never
going
to
remove
them
just
to
leave
it
as
a
docked
application.
Okay,
so
let
me
see,
here's
url
is
one
url.api
url.
So
let
me
take
a
look
at
there.
E
F
Michael,
I
posted
oh,
you
got
a
like.
Maybe
it.
F
Like
experimental
api,
so
do
you
want
to
deprecate
now
or
when
we
added
these
new
api
to
stable
node
api
version
so.
A
F
Yeah
we
can
encourage
in
the
documentation
to
use
this
a
new
experimental
api
yeah
versus
the
equivalent
that
are
now
considered
stable.
So
this
is
my
point
and
then,
when
we
promote
the
new
function,
luck
stable
api.
We
can
deprecate
the
old
one.
A
E
Okay,
I'll
do
the
same
in
this
api.
Ref
changes
pretty
much.
I
think
legend
car's
comment
was
also
about
with
pr,
because
I
I
do
very
similar
stuff
there,
like
I
have
this
node
api,
create
reference
instead
of
nap,
a
great
difference.
E
A
C
A
If
not
any
other
topics,
we
should
talk
about
before
we
close
out
for
this
week,.
E
I
have
just
like,
as
usual,
number
of
different
questions
about
possible
new
apis
to
the
node
api
sure
you
know
like
in
some
javascript
engines,
like
the
name
we
set
in
property
by
name
or
something
people
using
some.
Some
some
people
refer
like
a
property
id
or
a
property
name
and
and
property
name
can
be
either
symbol
or
it
can
be
string.
But
even
it's
a
string.
E
E
Well,
as
a
name
I'm
referring
to
what
the
eta
uses
in
its
api,
because
name
can
be
either
string
or,
for
example,
if
you
set
in
property,
like
I
think,
let's
say
in
normal
javascript,
we
can
probably
look
on
javascript
specification.
Yes,
yeah.
E
F
That's
not
michael,
you
could
use
the
search
on
top
on
your
left,
top
left.
G
E
It's
what
I
probably
kind
of
what
I'm
looking
for
to
function.
E
E
A
G
G
For
what
I
know.
Let's
say
I
I
need
to
check
it,
but
they
are
probably
not
not
having
any
strength
and
like
javascript.
G
But
the
problem
is
that
we
are
exposing
the
implemented
implementation
details
of
the
oa
javascript
engine,
which
the
concept
is
not
exposing
the
icon
script
and
that
probably
might
not
be
good,
but
I
don't
know
other
people
think
a
lot
about
it.
It's
we've
been
talking
about
the
idea
in
the
previous
meeting
that
we
would
be
hesitant
by
adding
new
concepts
that
are
not
available
in
the
admin
security
to
the
api.
A
G
I
see
I
I
can
see
the
use
case
for
the
feature
it's
very
useful
and
it's
very
performant,
but
I
mean
if
people
are
very
care
about
the
implementation
implementation
details
of
the
engine,
they
should
go
forward
with
the
engineering
api
and
another
api
should
keep
most
compatibility
compatibility
between
the
engines
so
that
the
other
implementations
could
also
embrace
the
it
could
also
provide
another
implementation.
We
got
very
very
hard
work
to
adopting
the
features
they
are
not
providing.
G
Yeah,
especially
when
especially
the
problem
is,
that
va
didn't
guarantee
their
native
api
api
stable,
so
they
can
duplicate
features
that
previous
provide,
and
so
we
have.
If
we
depend
on
that
features,
we
may
need
to
change
our
loader
api
if
we
are
depending
on
it.
So
that's
a
problem
just
for
not
just
agreeable.
E
G
Yeah,
I
don't
think
there
is
a
very
hard
bar
between
the
item.
If
we
should
add
an
api
and
gabriel
have
devoted
a
very
hard
work
on
investigating
if
the
api
is
compatible
between
the
outstanding
engines.
So
that's
how
it
how
we
decide
how
we
decided
if
a
api
is,
it
should
be
added
to
knowledge,
even
if
it's
not
a
part
of
economist.
G
Yeah
and
he
I
I
have
a
recall
that
he
has
a
separate
number.
He
has
a
implementation
on
putting
the
api
to
javascript
engine,
which
is
a
embedded
javascript
engine,
and
they
have
implemented
a
very
limited
set
of
features
to.
G
Provide
atmospheric
support
so
that's
very
challenging
to
implement
our
currently
have
currently
another
data
features.
If
that's,
if
that's
visible,
then
we
can
say.
E
Okay,
so
think
it's,
it
should
be
okay
to
be
able
to
add
new
api.
If
it's
implementable
on
existing
javascript
engines
is
correct,.
A
A
B
E
A
In
terms
of
adding
a
new
api,
so
it
has
to
like
the
shaped
spirit.
It
has
to
be
agnostic
to
the
underlying
javascript
vm.
A
All
right,
so
this
talks
about
the
experimental
I'm
just
trying
to
see
if
it
sort
of
covers
the
so
it's
kind
of
like
the
you
know
it.
It
must
be
necessary,
so
we
kind
of
want
you
know.
Kind
of
what
we
want
to
provide
is
not
like
a
huge
surface
area.
We
want
to
keep
the
surface
area
down
to
what
you
need
be
able
to
be
supportable
on
on
all
vms.
A
So
that's
where
the
kind
of
like,
if
it's
in
the
javascript
spec,
we
have
better
confidence
that
it's
going
to
be
supported
everywhere
right
because
you
have
to,
and
then
it
gets
into
that
fuzzy
like
what's
necessary
versus
unnecessary.
A
You
know
if
it's
a
you
know
it
it
it's,
and
so
there's
probably
some
things
we
have
included
which
have
been
like
for
performance.
This
really
really
helps
a
lot
right,
so
we'll
consider
that
versus
a
well.
This
is
just
a
nice
to
have
convenience
function
that
cuts
down
a
bit
of
code
that
one
we'd
probably
be
like.
Well,
you
know
that's
more
for
node
api
node
add-on
api,
where,
in
that
wrapper
we
want
to
do
the
things
that
will
sort
of
make
it
easier
for
you
easier
to
do
stuff
versus
in
the
one.
A
Does
that
make
sense?
Yes,
it
makes
sense.
Yes,
yes,
so
like
in
this
case,
you
know,
is
it
you
know
I
think,
to
make
to
advocate
for
the
you
know
what
you're
talking
about.
I
I'd
why
you
know?
Is
there
a
used
case
where
it
makes
such
a
big
difference
that
you
know
it
makes
sense
to
consider
it
or
is
it
like
it'd
be
nice
to
have
it,
but
if
not
things
are
not
really
broken.
Right
is
kind
of
the
consideration.
E
No
symbols
and
strings
are
different
right.
Like
so
think,
it's
you,
you
can't
replace
symbol.
You
can't
replace
string
with
symbol.
E
But
for
javascript
is
a
string,
but
we
string
in
some
cases
like,
for
example,
some
other
javascript
engines
say
in
chakra
or
like
in
hermes.
E
Whenever
they
accessing
properties,
they
want
to
have
a
unique
string
effectively,
and
so
this
unique
string
is
something
which,
in
the
end,
because
they
know
that's
unique,
especially
special
fragments
you
need.
So
in
this
case
they
don't
need
to
compare
the
level
setting
property
or
getting
properties.
They
don't
need
to
compare
all
this
by
string
content.
They
can
just
simply
compare
string
pointer,
point
or
effectively
matches
right.
E
Yes,
yes,
we
somehow
need
to
kind
of
in
native
code.
We
need
somehow
to
reference
this
unique
concept.
A
A
G
A
Like
if
you
wrote
co-
so
I
you
know,
I'm
just
like
if
in
that
creep
string,
if
there
was
a
flag
that
says
you
know
unique
and
that
flag
meant
this
can
be
unique,
but
it
doesn't
have
to
be,
and
you
know,
then
the
engine
did
something
like
it
could
say.
Okay!
Well,
I
know
this.
You
know
from
the
programmer's
perspective,
this
is
unique
string.
If
I
can
create
a
new,
unique
string
I'll
do
that,
otherwise,
I'm
just
going
to
create
a
regular
spring.
A
On
you
know,
it
is,
is
it's
kind
of
I
guess
where
I'm
going
is
like
a
hint
that
gives
the
engine
more
info
is.
Is
okay
in
my
mind,
because
that's
something
that
says:
okay,
you
can
do
an
optimization,
but
we're
not
forcing
an
optimization
right,
but
we
don't
want
to
provide
something
like
that
that
then
potentially
breaks
you
know
let
people
write
code
that
won't
work
right,
because
it
depends
on
the
hint
versus
not.
E
All
right,
so
it's
saying
if,
if
some
code
will
depend
on
that,
we
have
this
unique
or,
like
legend
cast
just
mentions
people
using
internalized
strings.
I
think,
for
example,
which
with
much
string,
we
can
use
just
kind
of
by
using
address
of
the
string
to
compare
it
with
others.
E
And
if
people
can
start
depend
on
that,
it's
whatever
it's
returning
to
be
supposed
to
be
like
unique
address
like
for
example,
in
this
case,
for
example,
returned
an
api
value
could
be
used
as
an
entry
inside
of
a
hash
table
right.
So,
instead
of
having
string
inside
of
your
hash
table,
you
can
use
just
address
of
your
an
api
value,
potentially.
A
Yeah
I
wasn't
thinking
like
I
was
thinking
more,
that
it
would
be
it's.
It
would
still
be
like
the
the
end
user
code
would
still
be
completely
transparent.
It
just
says
I
want
a
string,
it
gives
a
hint
that
says:
hey
I'm.
This
is
going
to
be.
From
my
perspective,
I
won't
create
another
string
with
the
same
name.
Is
that
what
you're
saying.
E
A
Right,
I
guess
I'm
just
trying
to
understand
like
what's
the
is
there
a
hint
the
end
user
could
give
that
would
let
the
engine
optimize
but
wouldn't
be
a
dependency?
It's
like
you
know,
just
give
me
so
it'd
still
be
like
give
me
an
a
nappy
value
for
a
string
and
that
string
may
or
may
not
be
internalized.
The
code
doesn't
need
to
know,
but
it
could
give
a
hint
that
sort
of
says
like
you
can
make
this.
A
E
Yes,
it's
more
like
yeah,
probably
it's
not
term
unique,
with
a
small
like
term
internalized.
I
think
we're
saying
that
whenever
you're
creating
this
string,
please
look
on
a
special
kind
of
string
table
and
find
string
the
same
content
and
use
it.
D
E
Use
it
for
always
say
built-in
object,
properties,
built-in
object,
name
so
think
we
don't
duplicate
all
these
different
strings
all
over
the
place,
but
we
rather
have
a
special
string
table
for
all
this
unique.
I
probably
again
I'm
using
this
unique
term,
but
in
fact
it's
like
internalized
string.
E
No,
it's
okay.
I
just
kind
of
realize
that
I
probably
I
can
implement
what
I
want
outside
of
know
the
api.
As
long
as
we
have
this
kind
of
new
reference
type,
so
we
can
wrap
up
any
any
type
of
object.
So
if
I
can
build
a
reference
to
a
string,
I
could
probably
achieve
it
outside
of
node
api.
E
E
E
A
If
not
thanks
for
everybody's
time
and
we'll
talk
to
everybody
later
on.