►
From YouTube: 2022-07-20-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
july.
20Th
2022
will
follow
the
agenda
that
was
in
the
issue.
Sorry,
it
was
in
the
repo
that
was
issue
number
142..
A
Before
we
get
started.
Does
anybody
have
any
announcements
they'd
like
to
share.
B
I
guess
I'll
just
share.
You
know
that
another
openjs
monthly
blog
post
on
the
progress
for
the
openssf
project,
alpha
thing
with
node.js,
went
out.
I
think
yesterday
or
the
day
before,
so
I
think
the
node.js
channel
tweeted
it
and
the
openjs
channel
tweeted
it.
So
it's
an
easy
way
to
find
the
link
and
see
how
progress
is
going,
which
has
been
good.
A
Sounds
good.
The
other
thing
I
think
I
will
add,
is
there's
discussion
of
sort
of
mini
mini
summit
on
typescript.
There
was
some
discussion
at
the
collaborator
summit.
There's
been
some
additional
discussion
and
some
of
the
issues
that
came
out
of
that
and
so
we're
looking
at
creating
you
know
a
time
either
next
week
or
the
week
after.
A
I
will
open
an
issue
in
this
repo
a
little
bit
later
today
that
that
talks
about
that.
It's
currently
in
an
issue
which
I
don't
have
the
number
off
the
top
of
my
head,
but
if
you're
interested
in
in
that
and
that
discussion
look
out
for
that
issue-
and
you
know
see
if
you
can
plan
to
join
that
as
well.
A
Okay,
so
let's
move
on
to
the
things
that
were
tagged
with
the
agenda
and
then
I
think,
after
that
we
might
spend
just
a
little
bit
of
time,
looking
at
our
sort
of
overview
of
the
different
initiatives
and
stuff
like
that,
we
can
talk
about
the
next
steps,
so
the
first
one
is
create
communications
channel
to
js
newsletters
periodicals.
This
is
number
110
that
one,
I
think
we're
just
kind
of
waiting
on
the
foundation
side
of
things.
A
A
Sure,
just
like
you
know,
I
think
what
we,
what
we
want
is
like
is
is
now
the
time
to
get
that
going
or
is
it
a
month
from
now
or
what
is
it?
You
know,
don't
want
to
have
it
on
our
agenda
every
two
weeks,
if
it's
not
going
to
happen
for
three
months
or
whatever
so
just
to
get
the.
B
Yeah,
I
think,
with
the
new
marketing
and
comps
person,
who
is
also
spinning
up,
you
know
kind
of
re,
reviving
the
marketing
committee
meeting.
I
think
that's
a
good
time
yeah,
so
we
should
talk
about
it.
A
A
A
A
B
There
we
go,
I
think
we
can
discuss,
maybe
a
little
bit
about.
I
think
it's
an
issue
you
open
or
something
like
that.
Where
you
discuss.
Let
me
find
it
where
you
discuss
that
we
were
missing
yeah,
better
multi-threaded
support,
issue,
number
139,
sure.
B
Yeah,
okay,
yeah
last
technical
priority.
We
didn't
actually
do
into
the
deep
dive.
Do
we
want
to
try
to
organize
something?
A
Yeah,
that's
a
good
point.
That
is
a
good
point.
Let
me
just
put
that
on
to
the
agenda
or
in
the
list
of
the
minutes
here
I
think
we
we
discussed
it
a
little
bit
in
the
previous
calls
that
that
likely
makes
sense
to
do
that
at
the
upcoming
collaborator
summit.
Right.
Yes,.
A
I
I
we're
definitely
hoping
to
have
one
and
I've
been
trying
to
see
if
we
can
do
it
at
the
red
hat
offices,
but
I
haven't
we
haven't.
We
haven't
been
able
to
close
on
that.
Yet
there's
just
you
know,
costs
involved
getting
figuring
out
who's
going
to
pay
them
kind
of
stuff
there's.
Also
in
the
issue
discussing
it,
some
other
people
are
going
to
explore
if
there's
some
space
in
some
other
company
that
could
could
host
it,
but
I
think
we're
very
actively
trying
to
to
confirm
on
that
side
of
things.
A
B
Yeah,
because
I
think
we
just
thinking
about
it
for
the
not
confused,
I
think
there
is
what's
the
name-
nordic
gs,
which
is
the
same
week.
A
So
I'm
just
going
to
put
a
you
know
in
the
in
that
issue.
We
discuss
and
let's
plan
for
the
next
club
summit,
which
should
be
early
october,
so
sort
of
on
that
one,
we'll
we'll
we'll
keep
that
as
a
placeholder
and
we'll
submit
a
topic
for
that
when
we,
when
we
get
there.
Okay,
perfect,
okay,
so
that
that
leads
directly
into
what
I
was
going
to
share
as
well,
which
is.
A
A
I
don't
know
if
there's
anything
sort
of
discussed
on
that
one
suitable
types
that
one
I
did
mention
that
there's
a
proposal
that
we
have
like
another
mini
summit
on
that
to
talk
about
you
know
it's.
I
think
the
current
proposal
is
around
ergonomics,
so
this
is,
you
know,
being
able
to
run
typescript
more
easily
with
node,
without
necessarily
bundling
typescript
or
anything
like
that
into
node
and
there's
different
ideas,
and
so
to
make
some
progress
on
that
front.
A
So
we
will.
I
will
create
an
issue
that
will
cover
that
which
would
be
related
to
this
one.
There's
still
lots
of
work
in
terms
of
in
existing
things,
we'd
identified
so
modifying
our
style
guides.
So
we
can
better
generate
types
and
and
stuff
like
that.
So
I
think
we've
got
a
good
list.
It's
just
a
matter
of
if
we
have
volunteers
people
to
move
them
forward.
A
Similar
state
we've
done
the
deep
dive.
We
have
like
some
concrete
next
steps
so
again
a
matter
of
moving
forward
versus
sort
of
thinking
about
what
it
would
be
web
assembly.
A
You
know
again,
we
had
the
deep
dive
there.
There
was
some
discussion.
A
You
know
we
might
want
to
document
the
project
agreement
on
that
front,
although
I
think
we
should
look
and
see
me
just
take
a
quick
look
there.
I
think
we
may
already
have
a
maintaining
esm
section.
A
B
A
Okay,
so
I
think
that's
like
under
esm,
if
we
don't
have
a
maintaining
dsm
dock,
that
actually
would
be
probably
a
good
thing
to
look
at.
There's
also
the
related
work
on
loaders
and
we
did
have
an
action
to
try
and
encourage
get
work
started
on
support
for
esm
and
the
vm
module.
So
maybe
that's
when
I
should
open
an
issue
in
this
repo
and.
B
A
Can
think
about
that?
Maybe
you
discuss
in
a
call
one
meeting
so
I'll
put
myself
like
it's
open
issue
on
this
support
features
for
latest
ecmascript,
so
I
think.
A
A
A
A
A
A
So
I
don't
know
if
there's
anything
more
on
those
that
you
think
we
should
talk
about
in
terms
of
like
next
steps,
things
we
should
plan
for
other
than
like
you
know,
there's
there's
obviously
work
in
all
these
different
areas.
We
could
individually
get
involved
in,
but
that's
I
think
that
more
takes
somebody
saying
hey.
I
want
to
get
involved
in
that
specific
effort
versus
this
team.
Necessarily,
you
know
working
on
working
on
them
on
the
development
part.
A
Yeah,
I
think,
actually
that's
a
you
know.
Maybe
it's
a
good
time
where
we've
done.
We've
done
a
good
amount
of
work.
We
have
documented
a
number
of
things
like
in
terms
of
the
technical
priority,
so
sending
out
a
survey
to
say:
do
people
agree
that
we've
got
all
the
main
things
top
priorities
you
know
do
these.
This
is
what's
proposed,
aligned
with
what
you
saw,
so
I
think
that
yeah,
so
that
do
you
want
to
open
an
issue
for
that.
A
And
yeah,
maybe
we
can
plan
next
time
to
like
give,
you
know,
gives
us
a
couple
times
a
little
bit
of
time
to
think
about
it.
Maybe
if
you
can
think
about
it
and
take
us
through
it,
you
know
tag
it
for
the
agenda
for
next
time
and
we
could
plan
to
spend
a
good
amount
of
the
agenda
next
time
to
flesh
out
what
that
might
look
like.
A
Okay,
if
not,
I
think
maybe
we
could
give
people
back
a
little
bit
of
time
and
I'll
go
off
and
create
the
issues
I
took
the
list
of
john
you.
You
can
do
that
when
you
you
do
yep
and
yeah
I'll,
also
open
the
issue
related
to
the
sort
of
mini
summit
and
we've
got
a.
I
think
we've
got
a
little
a
list
of
once
we
open
these
things.
You
know,
we've
got
a
list
of
things.
We
can
all
work
on
to
try
and
move
move
related
stuff
forward.
A
Definitely
looking
at
that
list,
it's
it's!
You
know
having
gone
through
all
the
technical
priorities,
it's
good
to
have
a
view
on
what
are
the
important
things
we
could
be
working
on
those
you
know,
even
if
we
don't
have
people
working
on
them,
it's
good
to
know
what
they
are
and
and
to
sort
of
know
what
we
want.
What
we'd
like
to
get
done?
If
we
had
time.