►
From YouTube: 2021-12-8-Next 10 years of Node.js
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
next
10
meeting
for
the
8th
of
december
2021
we'll
follow
the
agenda
in
the
issue
that
we
had
in
the
repo
which
was
issue
number
105..
Before
we
get
started.
Does
anybody
have
any
announcements
that
they'd
like
to
share.
A
A
And
then
we'll
move
on
to
the
agenda-
and
I
think
also
maybe
not
on
the
agenda.
But
we
should
talk
a
little
bit
about
the
debrief
from
the
the
summit
and
kind
of
next
steps
from
there.
B
A
I
know
that
tierney's
been
working
on
that
a
little
bit
he's
not
here.
So
I'm
just
looking,
I
know,
there's
an
issue
in
the
admin
repo
and
I'm
looking
to
find
that
right.
So
that's
this
issue
right
here,
number
641
in
the
admin
repo
which
is
move
bnb
devm
to
node.js
dev
container.
A
A
A
A
A
Okay,
those
are
the
two
most
important,
so
I
so
I
think
we
basically
have
the
next
steps
set
on
that
one,
which
is
good
any
other
discussion
on
that
one.
Before
we
move
on.
A
Okay,
if
not
so
the
next
two
were
really
they
were
things
we
tagged
for
the
deep
dives
I
think
it'd
be
best
to
go
back
to
chatting,
maybe
about
the
the
summit.
So
let
me
find.
A
A
A
So
I've
tried
to
push
forward
some
of
the
the
issues
so
on
the
starting.
The
discussion
on
adopting
the
electron
style
guide
there's
actually
a
there
was
a
discussion
issue
open,
so
we
could
go.
Take
a
look
there
node.
A
A
Of
course,
we
already
have
a
style
guide
in
the
node.js
project
in
terms
of
like
wording
and
and
sort
of
things
like
that,
not
so
much
structural
but
like
in
terms
of
content,
so
we
didn't
probably
what
we
should
have
done
is
instead
of
printing
in
the
style
guide
is
we
should
have
extracted
the
structural
parts
we
need
for
parsing
and
put
those
into
the
style
guide
that
we
already
have.
A
So
that's
sort
of
what's
come
out
of
the
discussion
a
little
bit
there
in
terms
of
you
know
the
getting
these
changes
in
and
really,
I
think
in
my
mind,
that's
the
next
step
is
to
probably
close
this
pr
and
you
know,
come
up
with
one
with
that
tries
to
pr
in
just
the
changes
we
need
for
the
structural
part
of
what
we
talked
about
into
the
existing
guide,
so
that
there's
no
confusion
that
this
is
trying
to
replace
all
that
kind
of
stuff.
A
C
C
A
Right
and
then
left
copy
and
paste:
okay,
so
ctrl
c.
C
A
D
A
So
if
we
then
go
back
to
you
know
kind
of
things
further
explore
that
I
did
spend
a
little
bit
of
time
and
had
a
few
discussions
with
tierney.
A
A
A
All
right,
which
basically
just
externalized
enough
of
the
configuration
options
that
it
could
work
on,
one
of
the
docks
that
that
tyranny
had
converted
and
it
also
added
the
ability
to
do
things
incrementally,
so
they
seem
fairly
small.
Although
there
is
another
there,
there
was
another
pr
earlier.
That
was
larger
change,
but
likely
more
complete.
A
So
you
know
that
there's
a
little
bit
of
progress
on
just
looking
at
the
parser
to
see
you
know,
can
we
can
we
use
it,
and
I
guess
it
really
comes
down
to
you
know
if
we're
gonna
convert,
can
we
pr
in
the
changes
into
the
style
guide?
That
would
let
that
parser
work
or
is
it
that
we're
going
to
have
to
do
something
different
and
and
maybe
then
either
tweak
it
or
you
know,
change
it
more
substantially
to
so
we're
still
working
through
those
two
things.
A
A
A
A
Maybe
I
did
not-
maybe
I
meant
to
but
didn't
so
I
don't
because
I
don't
see.
Oh
it
race,
suitable
types,
next
steps
right,
okay,
so
yeah!
So
actually
I
I
opened
this
issue
to
start
a
track.
Some
of
this,
the
work
that
we're
doing-
and
I
probably
should
put
in
some
more
stuff,
but
anyway,
that's
and.
A
So
that's
sort
of
what
I
know
is
up
to
date
up
to
in
terms
of
next
steps
on
that
I
haven't
had
a
chance,
or
I
don't
know
that
anybody
else
has
had
it
had
a
look
at
the
the
other
sort
of
side
of
things,
which
was
the
let
me
get
back
to
there,
which
was
the
single
binary.
A
It
was
like
reaching
out
to
anna
writing
up
an
overview.
What
we
discussed
and
sort
of
moving
that
forward.
A
A
A
Yeah
right,
okay,
so
so
the
question
would
then
be.
Maybe
we
can
spend
a
little
bit
of
time
now
to
plan
for
what
we
think
would
be
the
next
mini
summit
in
terms
of
that's
probably
our
most
useful
thing
to
do
so
as
opposed
to
these
two.
I
might
take
these
two
off
the
agenda
and
so
like.
Actually,
I'm
gonna.
B
Actually
yeah
for
the
next
submit,
I
was
a.
I
was
going
to
propose
to
work
on
documentation,
at
least
because
it
could
be
linked
also
or
at
least
partially
to
to
the
work
done
last
time
around
electron
documentation
stuff,
like
that,
and
I
think
on
the
issue
open
someone
mentioned
something
about
the
guide
which
are
not
really.
B
A
A
These
are
what
we
have
so
we
have
like
modern
http,
simple
type
friend
user.
We
covered
documentation.
We've
said
we're
going
to
put
on
webassembly
esm
support
for
features
from
latest
scripts,
spec
observability
permissions,
quality
security
model,
better
multi-thread
support
than
single
executable
applications.
D
Http
might
be
a
nice
one,
I
imagine
we
could
all
be
in
vichy
folks
into
that
and
get
quite
a
good
turnout.
A
D
A
Okay,
well
again,
I
I
think
I'd
agree
with
with
beth
and
if
there's
no
objections,
that's
probably
a
good
one
to
to
plan,
for
I
think
we
should
reach
out
to
the
ndc
team
to
say:
hey,
do
you
think
this
makes
sense,
or
do
you
already
have
this
covered.
D
A
B
I
I
think
we
also
had
some
examples.
I
think
james
did
some
stuff
also
with
a
web
server
framework.
I
don't
remember
the
name
of
the
working
group
like
six
months
ago,
or
maybe
a
bit
more,
so
we
should
also
see.
I
think
this
group
is
pretty
much
over,
but
I
think
we
also
have
some
some
example
or
feedback
from
james
on
multiple
issues
and
maybe
pr.
A
A
C
That
would
be
with
undici.
A
Yeah,
I
think
it's
like
them
and
then
maybe
just
james
too,
we
want
to
say,
like
hey,
we're
thinking
that
this
would
be
the
next
deep
dive.
You
know
the
next
deep
dive
in
the
mini
summit.
We
think
that
makes
sense
anybody
else.
We
should
be
like
trying
to
invite
and
that
kind
of
stuff,
okay-
and
you
know,
for
the
you
know
good-
to
give
the
context
of
like
hey.
This
is
what
the
team's
doing.
We
identified
this
as
one
of
the
priorities
for
success.
A
A
B
A
A
A
I
think
that
makes
sense,
and
let's
see
I
think
it's
probably
like
it
doesn't
make
sense
to
do
to
do
too
much
until
like
january,
like
reach,
we
could
start
to
reach
out
to
see
if
people
make
sense
and
stuff
like
that.
But
beyond
that,
in
terms
of
like
creating
the
issues
and
all
that
for
visibility,
I
think
I'd
wait
till
january
to
do
that
at
this
point.
A
Okay,
so
I
think
that's
kind
of
our
next
step.
You
know
there's
working
working
away
at
our
next
steps
for
the
ones
we've
already
looked
at
you
know,
and
if
people
do
have
time,
if
they
could
pick
up
any
of
those
sort
of
next
steps
from
the
the
last
mini
summit,
that
would
be
great.
A
You
know
we've
got
a
few
in
play,
but
there's
still
a
few
others
that
could
definitely
be
picked
up
anything
else.
We
should
talk
about
this
week.
B
Do
we
maintain
the
meeting
in
two
weeks
because
it
will
be
the
22?
I
don't
know
if
some
people
won't
be
already
into
christmas
or
stuff
like
that.
A
A
If
not
thanks
for
everybody's
time-
and
we
will
get
together
in
the
new
year
and
hopefully
keep
moving
things
forward
thanks
for
everybody's
time,
thanks
cheers.