►
From YouTube: 2021-11-10-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
november
10th
2021
we
will
we
did
have
an
issue
that
generated
with
an
agenda,
but
I
think
the
most
important
thing
this
week
is
to
just
sort
of
touch
base
on
the
summit
and
make
sure
that
you
know
anybody
who's
watching
is
aware
that
the
mini
summit
is
happening
next
week.
It
is
issue
number.
A
A
The
I
I
know,
tierney
you
were
looking
at
inviting
some
people
from
the
sort
of
types
world
into
participate.
I
do
see
on
the
issue.
There's
there's
a
comment
from
simon
about
somebody
being
intra
involved,
who
made
a
bunch
of
in
contributions
to
the
dt
and,
I
think,
oh
seems
like
we've
lost
tierney,
but
it
sounded
like
tierney
mentioned,
also
that
he
had,
you
know,
invited
some
people
in
definitely
types
typed,
and
there
was
an
issue
there.
B
A
B
Yeah
there's
a
discussion
in
the
definitely
typed
repo.
I
think
I
have
the
link
here.
Jesus
zoom
ui
is
weird
on
mobile
yeah.
I
could
see
there
yeah.
I
think
I
just
pasted
it.
I
think
I've
visited
a
panelists
posing
panelists,
okay,
all
right
yeah.
So
that's
the
the
link
to
that.
I've
also
quote
internally.
You
know,
obviously
can't
commit
other
people's
time,
but
you
know
I've
asked
if
they'd
like
to
join
sure.
Okay.
A
B
I
think
should
be
a
good
one.
Perhaps
someone
from
ncc
had
versailles.
A
A
B
Versailles
and
the
ncc,
the
folks
who
do
ncc,
which
they
don't
do
single
binary,
but
they
compile
everything
into
ac
your
entire
node
app
into
a
single
file.
So
I
imagine
they'll
have
okay
opinions
on
this.
A
Okay
sounds
good.
Okay,
that
sounds
good.
A
Okay,
anything
about
the
other
about
the
summit
that
we
should
talk
about.
I
guess
we
did
the
tweet
from
the
node
account
right.
I
guess
just
if
any
of
us
help
try
and
make
sure
the
people
we
I've
got
it
on
like
the
the
tse
agenda,
you
know
so
whatever
we
can
do
to
help
people
be
aware
that
it's
happening
and
hopefully
get
as
many
people
who
are
interested
there.
That
would
be
good,
so
any
yeah.
I
was
just
asking
anything
on
that
before
we
move
on
to
the
next
issue.
A
Nope
nope,
okay,
I
figured
that
was
the
most
important
we'll
do
the
deep
dive
and
then
you
know
we'll
have
some
discussion
into
that.
We
can
do
follow
on
the
other
things
we
do
have
on
the
agenda
that
was
generated
was
the
provide
the
pre-built
node.js
node
images.
I
know
turner
you've
been
working
on
some
stuff.
I
don't
know
if
there's
anything
sort
of
new
to
report.
Since
last
time
we
got
together.
B
Yeah,
nothing
on
the
code
side.
I
I
don't
know
if
I
created
the
issue
before
or
after
we
got
together
last,
but
I
did
create
an
issue
in
the
court
or
not
to
create
an
issue.
I
updated
the
issue
in
notepad
saying
you
know:
I've
been
progressed
and
kind
of
outlined
what
I've
done
and
there
seems
to
be
general
agreement
that
this
is
something
we
should
move
forward
with
there.
B
I've
been
busy
with
other
things,
as
I
mentioned,
michael
I'm
mostly
out
this
week,
and
I
was
getting
ready
last
week
for
my
life
surgery,
so
I
I've
been
otherwise
occupied
with
that
plus
interviewing
for
my
manager,
so
I
haven't
had
a
chance
to
get
around
to
that,
but
I,
the
two
things
there
I
need
to
do
are
create
an
issue
to
move
pre-ignition
advent
to
move
bnb,
slash
devem
into
the
node
project
and
then
pr
pr,
the
dev
container
to
node
core
would
be
the
ideal
path.
B
I
also
do
need
to
still
set
up
actions
to
to
build
the
docker
image
and
publish
it.
I'm
not
super
concerned
about
that,
though,
and
I've.
I
I'm
hopeful
that
we
could
also
get
an
additional
extra
large
runner
from
the
github
actions
team
to
actually
do
this,
which
would
then
speed
it
up-
and
you
know,
be
less
error
pro
and
stuff
like
that.
B
Just
because
there's
more
memory,
more
storage,
etcetera
for
for
actually
running
network,
and
that's
specifically
for
building
the
docker
image
and
publishing
it
not
consuming
it
right.
Yeah,
yeah,.
A
Okay,
that
sounds
sounds
like
you're,
making
some
good
progress,
even
though
you're
busy,
yeah
excellent
okay.
I
know
that
that's
great
and
then
the
the
other
things
we
had
were
sort
of
the
deep
dive
on
documentation
and
maintaining
and
growing
the
level
of
contribution
in
the
future
of
the
next
10.
A
I
was
thinking
that
you
know
maybe
we'll
defer,
since
we
have
the
summit
next
week
and
see
how
that
goes.
If
the
summit
turns
out
to
be
good,
you
know
that's
probably
a
way
to
get
a
more.
You
know
broader
input
into
the
technical
things
and
we
might
move.
You
know
schedule
one
of
those
for
the
documentation
and
these
other
things
versus
diving
into
them
ourselves.
A
A
Sounds
good,
okay,
okay,
so
that's
good,
and
that
takes
us
to
the
end
of
the
thing.
So
I
you
know,
thanks
for
everybody,
for
their
help
on
the
summit
and
maybe
we'll
give
you
a
few
minutes
back.
If
you
you
know,
have
that
time
to
get
ready
for
the
summit.
Do
some
investigation,
whatever
otherwise
we'll
close
out
and
hopefully
talk
at
the
summit
next
week
sounds
good.
Okay,
I'll
talk
to
everybody
later.