►
From YouTube: 2021-08-06-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
So
welcome
to
the
node.js
node
api
team
meeting
for
august
6
2021
we'll
follow
our
standard
approach
of
going
through
what
we
have
tagged
for
milestone,
11.
and
but
before
we
do,
that,
does
anybody
have
any
announcements
they'd
like
to
share.
A
A
So
here
I
think
there
is
we
had
some
discussion
in
the
past
on
this
one.
I
think,
maybe,
since
we'll
wait,
till
kevin
joins
just
to
see
where
we
stand.
If
there's
anything
more
to
discuss
on
that
one.
Let's
look
at
965.
A
Okay,
this
one
we'd
ask
the
question
to
the
to
the
poster,
but
I
wasn't
quite
clear
from
the
answer
I
didn't.
I
didn't
get
a
chance
to
watch
the
youtube
video,
but
I
from
the
answer
I
wasn't
sure
whether
they'd
reproduced
or
not.
So
I
asked
another
question
so
I
guess
we
can
wait
to
see
what
the
answer
is
there
and
then
let's
look
at
this
one,
I
think
legendary
cast.
You
were
looking
at
this,
but
I
don't
know
if
you've
had
any
time.
No
right.
A
C
React
native
hermes
allow
to
reference
any
kind
of
primitives.
This
is
what
I
understood.
A
D
That's
a
I
mean
this.
This
is
interesting
for
for
things
like
objects,
right
like
how
does
how
does
one
prevent
an
object
from
being
garbage
collected
because,
okay,
so
references
object,
string,
symbol?
Oh
I
see.
Okay,
so
there's
object,
so
there
are
always
references,
but
okay.
I
guess
I
guess.
The
question
we
should
have
asked
is
persistent
references.
D
A
D
I
mean
if,
if
you
know,
if,
if
the
engine
treats
primitive
values
well
as
primitive
values,
then
there
is
nothing
to
garbage
collect
right,
and
so
they
are.
D
D
A
But
it's
okay
so
like,
but
we
create
what
would
like.
We
have
something
that
basically
says
create
a
primitive
reference
and
give
it
to
us
back
right.
D
D
You
know
the
number
five
is
the
number
five
right
it
was,
the
number
five
will
never
be
garbage
collected,
otherwise
math
would
collapse
right.
So
you
know.
D
D
E
E
D
Yeah,
okay,
yeah
yeah
yeah,
I'm
still
reading
the
header
too,
because
everything
is
defined
in
line
so
that's
kind
of
nice
and
and
and
the
fact
that
it's
a
union,
I'm
I'm
trying
to
I'm
trying
to
read
the
header
to
see
how
how
like
a
javascript
object,
fits
into
that
okay
union,
because
I
mean
you
would
think
that
their
variable
length,
but
maybe
maybe
that's
the
thing
like
if
there's
there's
a
reference
to
a
javascript
object
that
goes
into
the
union,
which
is
great
now
but
like.
Is
that
a
persistent
reference?
A
E
D
D
Oh
boy,
look
at
that
object,
get
object,
assert
is
object,
return,
object,
runtime,
clone
object,
data
pointer,
so
so
so,
okay,
when
when,
when
this
value,
contains
an
object,
then
in
order
to
retrieve
the
object
from
the
value
you
clone
the
object
pointed
to
by
a
pointer
okay.
But
what
if
that
object,
is
garbage
collected?
How
do
you
tell
the
runtime
do
not
garbage
collect
this
object
under
any
circumstances?.
D
Okay,
that
that
would
be
another
question
I
mean
it
seems
as
though
it
seems
as
though
react
native
has
more
issues
with
with
persistent
references
to
objects
than
it
does
with
persistent
references
to
primitives.
So
it
seems
to
be
in
the
other
end
of
the
right
spectrum.
A
And
then,
if
like
they
are
just
persistent
like
five
is
persistent
or
whatever,
and
we
could
just
give
you
back
the
same
pointer
and
yeah.
That's
that's
okay,
but
we
want
to
be
able
to
effectively
call
give
me
a
give
me
a
persistent
reference
for
this
and
if
it's
just
oh
yeah,
same
thing
back
because
it
is
persistent,
that's
fine,
but
and
same
for,
like
a
deleter
persistence,
we
want
to
be
able
to
say,
let's
we're
being
asked
to
delete
this.
Oh
this
happens
to
be
persistent
already.
A
D
Something
yeah,
yeah,
yeah
and
the
type
the
type
is
is,
is
explicitly
associated
with,
with
with
the
with
the
value
in
in
in
here
like
basically
it's
it's
a
it's
a
structure
consisting
of
of
a
of
an
enum
value.
A
G
This
was
still
the
one
talking
about
remove
moving
the
the
cleanup,
the
the
release
call
to
the
actual
deconstructor,
a
deductor,
sorry,
but
I'm
still
not
sure
how
that
would
actually
work,
because
the
way
that
his
example
works
is
like
you
would
you
swap
the
two
values,
but
I
imagine
what
we
need
to
do
done.
What
we
need
to
do
is
immediately
release
one
of
the
values,
so
I'm
not
sure
if
we
can,
if
it
makes
sense
to
delay
until
cleanup
of
that
secondary
object,
I'm
not
sure.
F
G
The
first
yeah
we
call
here
and
that
template
we
call
reset,
which
is
that
napi
delete
reference
or
whatnot
right.
F
G
A
G
A
G
A
A
E
D
I
guess
the
fundamental
question
here
is
that
you
know
the
this
swapping
operation.
Do
we
consider
this
to
be
a
shallow
operation
or
a
deep
operation
right?
If
we
consider
it
to
be
a
shallow
operation,
then
we're
just
like
exchanging
members
of
this
structure
right,
but
if
we
consider
it
to
be
a
deep
operation,
then
we
want
to
actually
like
create
new
references
at
the
core
level
right
and
I
think
we've
opted
for
the
deep
operation.
So
we
can't
walk
that
back
now.
D
Though,
though,
a
swap
is
different
from
from
a
delete
in
a
way
right,
because
a
swap
means
you
know
just
exchange
whatever
is
inside
these
containers
right
and
so.
D
A
B
A
Yeah
yeah
exactly
yeah,
and
that's
just
that's
just
that's
why
I'm
trying
to
like
make
it
clear?
It's
like
we're,
not
exchanging
these
we're
getting
rid
of
one
and
overwriting
yeah
we're
overwriting
one
effectively
with
the
other,
because
I
don't
think
you
can
necessarily
set.
I
don't
think
we
even
have
do.
We
even
have
the
option
of
being
able
to
set
a
value
to
a
new
value
right
like
not
for
all
types
necessarily.
D
E
A
A
A
A
I
think
this
is
a
good
time
to
talk
about
the
matrix
of
tested
methods.
Jack.
Is
there
anything
that
you
need
the
team's
help
with
or
things
you
want
to
discuss
or.
F
F
For
a
second
sure,.
A
Yes,
yeah
might
be
easier.
E
B
F
Okay,
yeah,
I'm
not
quite
sure
what
this
these
two
method
does
like
under
docs.
It
says
it
creates
a
new
javascript
object,
but
I
want
to
look
at
the
implementation.
It's
it's
a
little
bit
different.
It's
like.
F
F
D
Yeah
yeah,
this
is
yeah
exactly.
This
is
a
this.
Is
a
javascript
thing
it
it
it
it.
It's
like
it's
like
in
javascript,
you
have
like
function,
x,
bracket
bracket,
brace,
brace,
and
then
you
say
new
x.
D
F
D
Constructs
a
new
javascript
object
right,
whose
constructor
is
a
function,
so
in
javascript
any
function
can
be
used
as
a
constructor
for
objects,
right
yeah,
and
so
you
have
a
function
reference
here
and
what
you're
saying
is,
you
know,
create
me
a
new
object
using
the
function
referenced
in
this
object
as
its
constructor.
D
A
A
E
G
Falls
for
it
yeah
it's
doing
like
I
just
did
a
search
in
github
that
search
box.
You
know
for
function
reference
new
in
this
repository,
okay,
let's.
E
C
G
F
F
G
So
I
can
imagine
if
you
have
it
so
on
the
javascript
side,
if
you
have
a
function,
that's
a
constructor
right
pass
that
function
into
your
c
yeah
into
the
add-on
and
then
do
the
new
right
and
then
it'll
return
an
object
back
to
javascript
exactly
in
javascript.
You
can
assert
that
that
object,
that
you
got
is
an
instance
of
that
classes
that
that
constructor.
F
A
F
I
think
that's
for
no,
that's
it
for
now.
Yeah
I'll,
take
a
look
at
it
more.
A
Thanks,
okay,
great
and
probably
a
good
time
also
to
check
in
with
deepak
in
terms
of
the
the
work
you're
looking
at
in
terms
of
making
it
easier
to
run
some
of
the
tests
individually
and
so
forth.
Anything
you
want
us
to
talk
about,
discuss.
H
Yes,
oh
my
god
yeah.
Let
me
show
the
walk
you
through
the
pr
that
I
have
it's
just
a
prototype.
A
So
here
yeah
we'll
let
you
share
and
do
that.
Okay.
H
Here
so
I
have
this
pr,
so
I
am
in
the
in
my
pr
branch
now
so.
H
So
I
have
added
a
you
know
in
the
package.json:
I've
added
a
npm
script
for
a
unit
and
a
pre-unit
hooked
on
with
it
right
now,
this
running
just
a
unit
and
then
running
the
pre
unit.
The
hook
is
not
working
properly,
so
I'll
be
running
the.
Let
me
just
show
running
the
you
know
pre
unit
separately
right,
so
I
can
give
a
filter
condition
like
this
any
file
name
right.
We
can
give
any.
I
guess
anything
to
be
honest,
you
have
to
sit
for
the
demo.
H
Let
me
give
you
the
one
which
I
tried
yesterday
I'll
give
the
so
name
here
is
a
punch
to
the
name
dot
cc
here.
So
what
it
effectively
means
is
that
run
the
name
all
right
run
the
name
compile
the
name.cc
file,
and
then
we
have
the
binding
generated
inside
the
unit
test
folder.
H
So
we
have
the
build
generated
inside
the
you
know,
test
folder.
Under
inside
the
release,
we
have
the
binding
dot
node,
the
output
of
the
node
rebuilt
and
okay.
Then
I'm
already
inside
the
unit
test
folder
and
I
have
a
customer
test.js.
This
is
not
how
I
am
I'm
intending
to
do
it
anyway,
but
for
now,
just
to
show
that
you
know
just
to
show
that
the
build
release
within
inside
the
unit
test
folder
works
right.
The
generated
the
compiled
binding
the
build
runs.
H
So
here
I'm
going
to
do
a
node
test
and
it
it
basically
runs
the
test
right
in
this
test
file.
I
have
copied
the
test
test
file
from
you
know
the
content
from
the
name.js.
That
is
because.
H
In
the
name.js
we
are
always
requiring
from
you
know
from
here
we
are
always
requiring
from
a
standard,
always
from
the
same.
You
know
the
build
location
if
we
are
able
to
configure
this
to
change,
to
require
from
a
different
location
right
if
you
are
if
this
is
able
to
like,
if
there
is
a
way
to
send
up
to
fix,
and
then
you
know
relative
or
relative
path,
right
path
for
the
build,
then
we
would
be
able
to.
H
You
know
prefix
with
that
and
then
do
that.
So
that's
the
reason
I
have
copied
to
it.
H
Why
do
we
need
to
compile
it
to
a
different
place?
Is
it
I
thought
it
was
a
good
idea
to
compile
to
a
different
place
like
I'm
open
for
suggestions?
Well,
I
just
you
know:
could
we
compile.
A
H
Yeah,
so
yes,
so
exactly
for
that
reason,
right
like
say
if
somebody
has
run
the
pre
unit
separately
by
mistake
or
for
some
reason,
and
then
this
binding,
if
they
run
the
npm
test,
after
that,
it
is
going
to
just
fail
for
everything
right.
So
I
thought,
because
this
is
going
to
be
a
subset,
the
the
generated
build
is
going
to
be
a
subset
of
the
original
build.
I
thought
it
could
be
generated
in
a
separate
location.
D
Another
thing
to
consider,
I
think
is,
is
is
if
you,
if
you
finish
this
off
right
and
you
have
this
polished
and
accepted
and
so
forth,
then
we
can
just
basically
redirect
the
the
test
folder
to
just
be
a
special
run
of
unit
test,
with
everything
turned
on
so
so
then
we
just
simply
run
our
unit
tests.
Your
way,
always
right
and.
A
A
It
would
basically
be
like
you
know,
no
filter
yeah
exactly,
and
so
you
know,
and
if
you
specify
a
filter,
then
it
will
narrow
down,
but
I
think,
even
in
that
case,
just
having
it
still
use
the
same
location,
the
same
binding
dot
like
the
only
the
only
reason
I
could
think
of
wanting
to
have
them
go
to
different
places
is
if
there's
some
value
in
like
having
multiple
copies.
At
the
same
time,.
D
So
so
can
we
not
like
what
like
when,
when
all
is
said
and
done
just
so
I
understand:
can
we
can
we
not
simply
rename
unit
test
to
test
and
call
it
a
day
and
then
just
get
rid
of
test,
because
it
already
covers
everything
and
then
we
can
just
move
the
move.
The
contents
of
test
under
unit
test
and
that
would.
A
A
Okay,
that
that
would
be
where
we'd
like
to
get
to,
I
think
yeah
that
makes
yeah,
but
for
what
you're
doing
now,
it
makes
total
sense
to
have
separate
things
to
to
work
on
that,
but
yeah.
In
the
end
it
would
be
nice
to
just
say:
yeah
we've
got
a
test
and
somehow
like
through
environment
variables
or
whatever
the
easiest
way
is.
You
know
you
can
specify
a
filter,
maybe
probably
on
the
command
line.
We'd
like
to
be
able
to
say,
npm
run
test.
A
D
H
What
that
would
mean
is
that
the
binding
that
I
have
so
right
now
I
have
a
binding.gyp
where
I
am
I've
changed
things
slightly
right.
Basically,
the
the
pilot,
the
build
sources,
is
getting
injected
with
what
we
want
right
condition
right.
Do
you
think
that
that
can
be
so?
In
that
case,
I
will
have
to
change
the
binding.gyp
here
here
as
well.
H
H
D
Think
I
think
you
know
having
having
your
own
playground
created
from
scratch
for
for
for
making
this
work
is
perfect,
because
then,
then,
you
do
not
interfere
with
the
with
the
existing
testing
infrastructure
and
you
build
up
a
completely
parallel
testing
infrastructure
from
scratch.
Basically,
but
in
such
a
way
that
we
can
then
simply
just
switch
over
to
it
whenever
we
want
to
right
and
then
just
rename
it
from
from
like
unit
test
to
just
test
and
then.
D
You
know
what
we
do
today
and,
and
the
filter
argument
will
then
remain
viable
and
usable,
even
for
like
npm
test
after
we
do
the
rename
so
yeah.
I
think
this
is
it's
a
good
way
to
go.
H
Okay,
all
right
so
yeah,
so
I'll
just
walk
through.
So
this
is
the
file
that
is
being
called
when
you
run
the
npm
run
a
pre
unit,
so
the
pre
unit
runs
this
file
and
it
this
invokes
a
child
process,
node
ui
variable,
so
that
we
can
inject
whatever
we
want
run.
So
we
take
the
filter
conditions,
parse
the
conditions
right
now.
It's
just
checking
one
right.
H
You
know
the
only
the
first
one,
essentially
the
very
first
one
so,
but
we
can
pass
it
and
pass
more
arguments
right
and
then
inject
everything
as
a
env
variable
right
and
then
in
the
there's
a
I
have
a
separate
binding.js
right
and
I'm
injecting
the
parched
values
into
here.
And
then
you
know
here,
like
gabriel,
from
the
gable
had
provided
a
iot
node
link
class
last
time
so
similar
to
that
I'm
having
a
workflow.
H
So
what
it
means
is
that
I
have
the
target
the
binding
target.
The
build
target
is
actually
dependent
on
a
generate
so
that
I
have
generated
binding.cc,
which
is
getting
invoked.
The
action
part
of
it
invokes
generatebinding.cc,
which
goes
and
generates
this
file
right.
So
inside
this
I
have
a
multiple
maps,
because
if
you
look
at
our
binding.cc,
I
think
we
have
some
versions
right
for
node
in
api
v5
in
api
v3.
H
H
You
know,
maps
and
then-
and
one
more
thing
is
to
like
map
the
file
name
right,
the
file
name
that
is
coming
in
with
the
export
object
name
right,
because
in
some
some
cases
it's
it's
not
something
that
can
be
created
on
the
fly,
because
in
some
cases
it's
completely
different.
Like
async
worker
person,
persistent
the
export
name
is
persistent
async
worker
right.
So
it's
not
even
like
a
camel
case
thing
that
we
can
modify
to
a
different
capitalized
format.
A
A
D
D
Yeah,
this
is
basically
this
combing
through
the
tests
like
this
will
expose
these.
These
inconsistencies
that
that
that
were
allowed
so
far,
because
we
were
doing
everything
by
hand
but
yeah,
ultimately,
we'd
wanna
we'd
want
to
remove
all
these
maps.
So
you
know,
as
you
discover,
these
inconsistencies
feel
free
to
go
and
rename
things
so
that
you
don't
need
this
map
anymore.
A
H
A
F
D
Of
that
they
will
be
accepted,
even
even
though
it
seems
like
a
like
a
trivial
or
unrelated
change
or
whatever,
and
I
mean
if,
if
you
get,
if
you
get
pushback
saying,
why
are
you
doing
this?
This
is
completely
useless.
Then
you
say
yes,
yes,
but
I'm
working
on
this
larger
thing
and
that
in
itself
is
a
good
reason.
So
so
yeah
just
just
make
the
small
prs
and
then
it'll
make
your
job
easier.
With
this
big
feature,
as
you
read.
A
Yes,
it's
a
lot
easier
for
us
to
look
at
those
and
say:
okay,
this,
this
is
like
we
know,
is
not
a
change
to
the
test.
It's
just
a
change
to
the
the
naming
and
then,
when
the
the
actual
functional
thing
you
have
comes,
it's
a
lot
easier
to
look
at
and
understand.
Okay,
it's
just
this
is
all
that's
changing,
rather
than
like.
Oh.
I
D
The
only
thing
I
don't
understand
is:
why
do
you
need
to
call
no
jib
rebuild
from
from
javascript.
H
D
No,
no!
No!
No!
No!
No!
No!
It's
not
it's
not
what
it
is
that
you're
calling
it's!
Why
do
you
need
to
call
it
at
all
because,
like
you
did
this
this,
this
minus
minus
filter
argument
right.
This
comes
all
the
way
from
the
user
from
the
command
line
right.
So
so
the
variable
npm
config
filter
is
available
in
in
in
binding.zip
already
right.
C
D
So
so,
oh
I
see
I
correct
me
if
I'm
wrong,
you
need
to.
You
need
to
call
this
by
hand,
because
npm
doesn't
call
it
for
you
right,
like
npm
will
call.
We
will
start
nodejib
if,
if
you're,
if
you're
doing
like
binding.jit
but
you're,
not
doing
binding.jib
you're
you're
doing
like
unit
test,
slash,
binding.
D
H
Minus,
but
what
you
said
previously
like,
if
this
is
going
to
be
the
new
testing
infrastructure,
then
we'll
just
move
it
out
more
than
binding
the
out,
and
then
we
wouldn't
need
this
file
anymore.
F
H
A
I
A
D
Right,
okay,
but
right:
okay,
but
if,
if
if,
if
no
jib
rebuild
supported
like
yeah,
if
if
node
pre-build
had
like
the
binding.jip,
that
is
being
run
by
nodejib
rebuild
right.
If,
if
that
thing
had
the
code
that
that
you
said
now
at
the
top,
where
it
creates
like
the
list
of
sources
right,
then
then
that
code
that
creates
the
list
of
sources
at
the
top,
could
access
the
npm,
config
filter
variable
and
then
and
then
you
wouldn't
need
to
run.
Binding.Chip
yourself
right.
A
A
D
D
So,
let's
see
here,
we
have
all
right
right
right,
okay,
so
so
we
have
right
now.
What
we
have
is
this
and
then
in
here
we
have
a
a
binding
jib
right.
D
So
so
here
we
just
have
like
a
like
a
static
list
of
sources
right,
but
if
we
replaced
this
static
list
of
sources
with
like
you
know,
we
if
we
had
a
variables
section
here
at
the
top.
D
Exactly
exactly
but
elsewhere
like
if,
if
we
had
that
list
of
variables
at
the
top
here
that
generates
this
list
and
then
here
you
would
make
a
reference
to
that
variable.
D
Then
you
know
we
would
have
the
dynamic.
We
would
have
the
dynamic
source
list
that
that
deepak
is
working
on
right
and
we
would
have
the
the
no
jib
call
from
we
would
have
the
no
jib
call.
We
could
reuse
the
node
call
from
from
from
from
from
from
right
here
right.
D
So
I
guess
what
I'm
asking
is:
oh,
my
goodness
from
right
here,
which
is
very
far
away
because
it's
at
the
bottom
of
this
file.
Isn't
it
okay,
so
yeah!
So
there's
no
rebuild
business
right.
So
basically
I
guess
what
I'm
asking
is
you
know
you?
You
could
just
move
that
execution
of
nodejib
rebuild
to
here
right
and
then
you
wouldn't
need
a
javascript
file
that
does
it.
H
A
A
Dot
cc,
you
want
to
go
to
the
binding
or
yeah
right,
okay,
because
yeah,
I
think
so.
That's
the
one
that
it's
already
click
on
that
one
that
one
you've
already
modified
to.
H
Don't
have
this
right,
the
generating
so
in
the
existing
test
infrastructure
we
don't
have
to
generate
a
binding.cc.
A
H
A
I'm
just
wondering
if
there
was
like
a
new
target
which
was
basically
like
npm,
run,
filter
and
you'd,
specify
your
and
then,
if
it
generated
then
generated
everything
that
was
needed.
Okay,
could
you
then
run
the
existing
npm
run
test,
which
would
do
the
pre-jip
build
and
then
run
the
test?
I
don't
know
if
that
would
work.
H
Yeah,
I
think
that
I
think
it
depends
on
how
we
can
organize
this
here
right,
like
probably
what
you
are
suggesting
is:
can
we
do
so
when
we
run
out
so
basically,
if
we
are
going
to
remove
this
whole
thing
and
have
this
test,
I.
D
I
think
I
got
it.
I
think
I
got
it
okay,
so
your
your
pre
unit
says
node.
Okay,
let's
see
your
pre
unit
says
node
unit
test,
minus
minus
filter
right.
So
what
that
basically
is
is
it
runs
a
script
called
unit
test,
slash,
index.js
or
unit
test.js
right
right.
H
G
D
Say
you
could
say
no
jip
rebuild
minus
c
unit
test
right.
H
D
Or
or
sorry,
no
jip
rebuild
minus
c
unit
test
right.
If
you
change
to
this,
just
just
change
it
just
for
for
argument's
sake,
yeah
rebuild.
D
D
H
Yeah,
yes,
yeah
yeah.
There
we
go
okay.
D
Click
on
that,
okay,
so
now
go
to
the
top
okay.
So
now
here
you
say:
node
minus
p.
Instead
of
saying
at
where,
where
you
say
sources
right,
you
say:
node,
minus
p
process
and
files
to
run.
You
see
that.
D
What
you
will
say
is
no,
because
because
the
problem
is,
if
you,
if
you
put
filter
there,
then
it
doesn't
look
right,
because
it's
like
com,
commas
and
stuff,
you
need
to
process
the
filter
right
to
get
a
list
of
files
yeah
right,
okay,
so
what
you
can
do
here
is
instead
of
node
minus
p
process
m
right.
You
can
say
node,
minus
e
right
and
then
the
name
of
a
file.
Node
minus
e,
create
file
list,
dot,
js.
D
The
standard
output
of
node,
minus
e
or
or
just
simply
node
generate
filelist.js
the
output.
The
standard
output
of
that
will
become
this
list.
H
H
Very
cool:
that's
a
good
idea.
Okay,
all
right!
Okay!
Is
that
anything
anything
else
you
wanted
to
take
us
through
or
questions,
so
I'm
right
now
generating
the
one
thing
I
want
to
point
to.
Does
I'm
just
you
know
kind
of
generating
it
this
way,
do
you
think,
like
I
should
put
in
a
template?
I
don't
think
we
need
a
template
right
like
I
can
just
push
contents
and
then
write
them
directly.
We
don't
need
a
template
for
this
right,
because
this
this
doesn't
need
to
be
neat.
D
A
H
Checked
in
is
it
in
this
case
I
have
checked
in,
but
it
doesn't
begin
like
just
yesterday.
I
added
a
git
ignore
so
right.
A
A
C
I
have
a
paragraphs
on
not
the
ib
years
I
under
the
documentation.
If
you
take
a
look
and
what.
C
Yeah
yeah,
I
added
these
new
docs
and
if
you
have
time
to
review
then
yeah
we
can
publish
this
this
module
on
npm,
like
we
discussed
last
week
and
another
done
api.
I
I
think
that
it's
time
for
a
new
release,
so
I
opened
a
new
issue
and.
C
Yeah,
because
we
have
some
fixes
and
some
new
thief
feature
so
yeah.
If
you
are
good
yeah
I
am
I
can.
I
can
go
for
these
new.
B
A
C
So
I
I
I
I
will
wait
2-3
days
so
and
if
you
don't
have
any
thing
to
add,
we
can.
C
Published
release
it's
almost
two
months
from
last
release,
right.
A
C
A
If
not
thanks
for
everybody's
time
and
we'll
see
you
in
github
and
next
week,.