►
From YouTube: 2022-07-20-Node.js Technical Steering Committee 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
I
think
I
will
mention
that
there's
discussion
of
a
mini
mini
summit
on
pipe
script,
related
typescript
support
and
ergonomics
and
stuff
like
that.
So
if
that's
a
topic,
you're
interested
in,
I
do
plan
to
open
an
issue
in
the
next
10
on
the
organization
for
that
probably
this
afternoon,
and
there
is
an
issue-
I
don't
have
it
off
the
top
my
head,
but
there
is
an
issue
in
the
node
repo,
where
that's
being
discussed
as
well.
So
if
you're
interested
just
want
to
make
sure
that.
A
Okay,
the
next
section
is
cpc
and
board
meeting
board
minute
updates
on
the
board
meeting
board
front.
I
don't
have
too
much
to
update
other
than
that.
The
next
meeting
is
this
friday.
So
if
there
is
anything
you'd
like
me
to
bring
up
there,
let
me
know
also-
I
guess
it's
worth
mentioning.
This
will
be
my
last
board
meeting
and
we
won't
necessarily
have
anybody
on
the
the
you
know
the
tse
to
to
be
that
link.
I
don't
think
that's
an
issue.
A
B
A
I'm
just
a
general
member,
you
know
I
I
am
running
for
there's
positions
where
there's
voting
members,
you
know
from
the
regular
members,
but
I'm
a
regular
member.
Okay.
B
So
I
did
not
attend
this
this
week.
I
don't
know
if
you
did,
but
I
did.
I
didn't
see
any
I
I
did
read
the
minute.
You
know
that
I
did
read
the
issue
and
the
minutes
stuff
and
and
they're
actually
called
minutes,
but
whatever
it
was
and-
and
I
didn't
really
see
anything
that
called
out
to
be
mentioned
here,
did
you
do?
Do
you
have
a
different?
That's
your
recollection
as
well,
michael.
You
were.
A
No,
I
I
think,
that's
true
other
than
we
should
that
you
know
it
was
mentioned
about
the
cpc
or
the
cpc
sort
of
representative
cycle
which
is
on
now,
and
we
have
an
issue
later
on,
so
we
should
close
out
on
that,
but
other
than
that,
I
didn't
have
anything
in
particular
to
call
it
right.
Okay,.
A
Okay,
so
yeah,
let's
move
on
then
to
the
issues
that
are
tied.
The
first
one
is
reinstate
ronag
to
the
tsc.
Let's
issue
43
897
and
I
suspect,
rich.
You
added
that
to
the
agenda.
B
Yes,
removal
when
people
in
the
90
day
period
don't
vote
on
any
in
any
of
the
votes
and
attend
fewer
than
25
of
the
meetings
is
automatic.
It's
not
a
decision
of
the
tsc.
So
if
we
want
to
re-add
robert,
we
need
to
do
that
and
the
charter
indicates
that
that
can
that
that
must
be
done
with
the
vote.
So
we
have
12.
We
have
a
quorum
here
and
beth
has
also
indicated
a
plus
one
in
the
in
the
issue
for
this
meeting.
B
So
I
don't
know
if
anybody
has
anything
they
want
to
say,
but
assuming
not,
it
would
be
great
if
everybody
could
use
emoji
reactions
or
something
or
sure
put
things
in
the
chat
whatever,
but
if
we
could
just
get
everybody
to
indicate
their
vote,
I
can
then
add
the
json
file,
blah
blah
blah
blah
so
obviously
on
plus
one
beth
is
plus
one
and
let's
see
here
we
have
reuben.
B
Do
we
have
michael
dawson?
Yet
we
do
do
we
have
richard
lau?
We
do
do
we
have
greece?
Yes,
we
do
antoine's
in
there
already
jeffrey.
Do
we
have
a
vote
from
jeffrey?
You
can
do
the
plus
or
minus
zero
if
you
don't
wanna.
If
you
wanna
stance
here,
michael,
we
have
michael
zazzo's
in
there
and
darshan
in
there
joy
I
see
nikita.
I
don't
see
joy's
vote
one
way
or
the
other.
B
Jay,
do
you
have
a
vote
on
reinstating
robert.
B
And
mateo
you're
in
favor
of
reinstating
robert
is
that
is
that
correct
or
I
am
in
favor.
Okay,
all
right
joy
isn't
abstain.
Everybody
else
here
is
in
favor
and
beth
isn't
in
favor
at
voting
in
absentia.
I
think
that
closes
that
issue
so
great
I'll,
take
care
of
all
I'll.
Take
care
of
stuff.
A
B
A
B
There's
other
discussion
in
there
around
around
other
things
that
you
know
I'll
take
somewhere
else
or
maybe
we'll
have
in
the
closet,
but.
A
Okay,
perfect,
okay:
we
can
move
on
to
the
next
one,
then,
which
is
node
cpc
membership
for
2022
2023.
This
has
been
on
the
agenda.
A
number
of
times
discussed
a
few
times
for
context.
The
last
comment
seems
to
be
to
leave
it
open
for
another
week
which
is
now
passed,
so
I
think
we
just
confirmed
rich
and
joe
at
this
point.
B
Yeah,
if
they're
at
this
point,
it's
consensus
if
nobody
objects,
if
you
know
we
have,
we
have
quorum
here
if
nobody,
unless
somebody
has
questions,
concerns,
objections
joe
and
I
are
effectively
reappointed
for
another
year,
I'm
going
to
do
a
quick
click
over
to
the
issue,
to
make
certain
that
nobody,
el,
that
nobody
has
said
anything
yeah.
Nobody
has
said
anything
in
the
issue.
Nobody
else
has
nominated
themselves,
etc,
etc.
So
I
think
I
think
we're
done
as
long
as
we
just.
C
Know
it's
it's
a
fantastic,
fantastic
role.
It's
just!
I
couldn't
at
the
time
and
you're
doing
a
good
job.
So
I'm
not
you
know
I
have
I
I
had
to
reduce
my
evening
work
yeah
due
to
obvious
reason.
So.
A
Okay,
great
yeah,
so
thanks
and
moving
on
then
to
the
next
issue,
which
is
number
612.
I
would
like
to
become
a
member.
This
is
related
to.
B
I
think
it
was
me
yeah
right
so.
B
B
I
think
mateo
commented
yeah,
let's
see
here
so
I
said
yes
yeah
a
week
ago,
I
said
I'd
take
a
look
at
the
crowded
instance
to
see,
if
that's
at
least
something
we'd
like
to
keep
going
and
identify
any
text
there
that
you
said
so
yeah
I
said
I
said
I
would
follow
up
and
I
did
not.
I
dropped
the
ball
so
yeah
I
could
say
I'll.
B
Do
it
again
and
actually
do
it
this
time
unless
somebody
else
wants
to
be
responsible
for
figuring
out
the
status
of
our
internationalization
efforts
and
what
we
should
do
with
them,
it's
other
than
the
you
know,
leaving
this
person
hanging
this.
Isn't
this
isn't
a
time
critical
thing,
but
I
will
I
will
abs.
I
will
be
trying
to
be
better
about
actually
getting
it
done
this
week.
A
C
B
I
don't
know
what
a
champion
would
mean
in
this
case,
but
we
we
what
we
what
we
tend
to
have
with
internationalization
efforts,
is
a
lot
of
people,
volunteering
and
then
not
doing
anything.
No,
no,
that's
not
fair.
It's
not
that
they
don't
do
anything,
a
lot
of
people,
volunteering
and
then
doing
a
little
bit
and
then
you
know
getting
you
know,
sort
of
like
I
said
I
would.
I
would
look
at
crowding
and
then
I
didn't.
You
know
that
sort
of
thing
happens
a
lot.
B
It's
a
huge
amount
of
work
to
do
internationalization,
right
and
or
even
to
do
it
badly
is
a
huge
amount
of
work,
honestly
and
and
yeah.
So
you
know
I,
if
we're
going
to
do
it,
I
think
it.
I
think
this
is
a
case
where
it
really
needs.
B
You
know
yeah.
If,
if
we're
going
to
continue
doing
it
the
way
we
we
had
originally
set
it
up
to
be
done,
we
probably
need
some.
We
probably
need
a
tsc
champion
of
some
kind
or
something,
but
I
don't
know
I'm
rambling
at
this
point
I
I
would
say,
let's
pick
this
up
next
week,
we'll
figure
out
the
crowd
in
peace,
at
least,
and
I
think,
if
we
can
keep
crowding
great
and
if
we
can
figure
out
a
way
to
integrate
that
into
the
website
even
better.
B
A
C
On
that
topic,
I've
reviewed
a
few
pr's
that
we're
adding
french
translation
of
some
pages
of
the
website
and
translations
were
good,
that
the
english
content
itself
was
so
outdated.
So
we
also
have
that
problem.
B
Right
we're
not
keeping
the
english
we're,
not
keeping
the
english
content
up
to
date.
I
I
actually
noticed
this
morning
that
there's
a
there's
an
article
in
there
about
how
to
parse
arguments
that,
like
it's
from
2011
that
recommends
yargs,
I
think-
and
you
know
and
like
we
now
have
an
experimental
parsers
module.
Maybe
that
should
be
a
link
to
that,
but.
C
B
Yeah
yeah
agreed
website
content
overall
is
a
is,
is
another
like
is
there's
a
few
of
these
issues
like
where
there's
like
a
large
team
of
mostly
inactive
people
like
website
team
has
over
100
people
on
it,
but
there's
like
maybe
five
active
people.
You
know
and
like
this
is.
This
is
something
we
probably
want
to
address
at
some
point,
but
it's
also
not
super
time
critical
and
we
have.
We
have
a
private
segment
to
get
to.
So
maybe
we
should
keep
going.
B
And
I'll
and
I'll
I'll
I'll
actually
take
a
look
at
crowding
this
week
rather
than
say,
I
will
and
then
not
do
it
so.
A
Okay,
so
the
next
one
is
node.js
loaders
proposal
rename
loaders
to
hooks.
This
is
number
95
in
the
loaders
repo
and
I
think
jeffrey
you
added
that
to
the
agenda.
D
D
So
this
is
our.
We
have
a
repo
node.js,
loaders
and
the
you
know,
basics
up
here
and
then
status,
which
maybe
I
should
call
that
roadmap.
But
this
is
like
where
we
are
and
what
we're
doing
so.
Loaders
were
created
in
the
first
place,
along
with
the
esm
effort,
basically
to
provide
a
way
to
continue
to
like
patch
modules
in
esm,
because
that
was
you
know,
trivially
easy
in
common
js,
and
that
was
like
essentially
the
way
that
everyone
customized
node
was
by
monkey
patching
whatever
module.
D
They
wanted
to
change
the
behavior
of
that's
not
possible
in
esm,
like
at
least
in
any
of
the
same
ways
that
it
was
possible
in
common.js,
and
so
this
idea
of
like
registering
custom
loaders
that
get
that
can
like
override
parts
of
the
module
system
before
any
user
code
is
loaded,
was
created
and
so
and
that's
what
has
been
continued
to
get
developed.
D
D
I'd
also
like
to
say
that
the
loaders
team
has
very
little
in
common
with
the
modules
to
the
former
models
team,
like
I
think,
I'm
the
only
common
member
between
the
two
and
it's
a
much
more
productive
group,
much
more
collegial
much
more
collaborative
there's,
never
any
need
for
you
know,
votes
or
escalations,
or
things
like
that.
So
you
know
it's
a
it's
a
it's
a
safe
place
to
work.
D
It's
a
good
group
to
bring
questions
to
the
the
main
people
working
on
stuff
are
me
and
jacob
over
here,
and
also
antoine
and
guy
bedford
and
then
bradley
various
and,
although
he's
kind
of
taking
a
bit
of
sabbatical,
these
are
the
people.
Who've
contributed
to
a
lot
of
the
issues.
Probably
the
biggest
ones
are
andrew
bradley's,
probably
andrew
bradley
and
mayo
are
probably
the
two
biggest
stephen
bellinger
been.
D
I
think
representing
datadog
instrumentation
has
also
been
quite
active
and
then
a
few
of
these
others
guiltair
has
been
around
so
so
yeah.
The
goal
has
been
to
like
just
as
a
initial
goal:
try
to
close
any
gaps
remaining
in
esm
with
with
comma.js,
so
that
anyone
who
wants
to
do
anything
in
esm,
as
as
close
as
much
as
possible,
should
be
able
to
so
that
at
least
node
isn't
the
one
holding
anyone
back
from
building
an
app
in
esm,
building
a
library
in
esm
and
we're
pretty
far
most.
D
You
know
if
you
look
at
these
check
boxes
that
are
done.
The
next
major
thing
is
moving
loaders
off
thread.
That
would
let
certain
things
be
accessed.
Synchronously,
which
is
important
for
the
import.
meta
resolve
api
that
browsers
standardize.
That
sync,
because
our
resolve
is
async,
it
might
offer
other
opportunities
for
sharing
code
between
the
two
between
the
esm
loaders
and
the
commonjs
loader.
D
And
then
this
is
something
that
comes.
That's
come
up.
We've
been
talking
about
it
for
a
long
time,
but
it
came
out
more
prominently
recently
in
the
typescript
discussion
a
way
to
like
right
now.
You
always
call
loaders
via
loader
flag
and
there's
no
other
way
to
register
them.
So
it's
something
that's
been
kind
of
on
the
to-do
list
for
a
long
time
of,
like
think
about
some
other
way
that
users
can
define
loaders
for
node
to
to
register
before
loading
application
code.
D
D
D
Currently,
I
think,
like
tools
like
ts,
node
have
gotten
this
to
work
where
you
basically
are
registering
like
a
like
an
old
school
style,
common
js
loader,
in
addition
to
the
new
esm
loader
to
handle
cases
of
common
js
intermixed
in
the
in
the
tree
like
when
esm
imports,
com.js
or
recommendations
requires
commonjs,
etc.
D
So
it
would
be
nice
to
improve
the
ergonomics
of
that,
and
you
know
ultimately
be
nice
to
not
need
to
create
two
types
of
loaders
for
two
module
systems,
but
at
the
very
least
like
we're
gonna
start
with
eliminating
the
bugs
and
gotchas
that
are
in
it
already,
and
if
there
can
be
broader
merging
later
later
on
down
the
road,
then
that
would
be
great,
but
that's
a
more
of
a
future
effort
and
then
down
here
is
where
I've
been
putting
like.
D
Basically
everything
else
that
people
have
been
requesting
that
feels
out
of
scope
for
simply
achieving
parity
for
common
js.
Probably
the
biggest
like
new
feature
here
is
import
maps
which
are
becoming
increasingly
important
because
dino
relies
on
them.
That
is
their
module
resolution
system
essentially
and
browsers,
I
think,
have
I
think,
chrome
has
shipped
them.
I
think
they're
in
some
kind
of
standards,
process
or
they've
been
standardized.
They
don't
remember
where
they
are
in
the
process,
but
these
are
becoming
more
like
across
platform
standard
for
resolution.
D
D
It's
probably
important
for
us
to
support
it
first
class
built
in
and
then
various
helper
functions
for
things
that
people
want
to
reduce,
boilerplate
for
or
want
to
have
access
to
utility
methods,
et
cetera,
and
then
the
rest
of
these
are
here
from
feedback
from
the
typescript
team
about
basically
like
they
want
to
customize
node
to
make
it
feel
like
a
typescript
runtime,
and
there
are
all
sorts
of
little
odds
and
ends
of
places
where
you
would
want
to
customize.
To
do
that
like,
and
some
of
them
are
things
you
might
not.
D
Think
of,
like
you
know,
tab
completion
and
the
rebel,
and
you
know
they
want
to
have
access
to
the
algorithm
that
we
have
for
discovering
named
exports
from
common
js
so
that
they
could
do
stuff
with
them
in
the
rebel
and
other
places.
So
this
raises
the
question
that
just
leading
into
the
other
issue,
which
is
that
you
know
historically
all
custom,
not
me
at
all,
but
most
customization
in
node
has
been
done
through
monkey,
patching
core
modules
and
or
monkey
matching
like
things
off
of
core
modules.
D
But
I
think,
there's
been
a
desire
to
move
away
from
that,
because
it's
a
very
blunt
tool
and
that
doesn't
let
us
kind
of
control
how
people
customize
the
runtime
at
all
I
mean
it
opens
this
up,
for
anyone
could
inject
anything
and
is
there
any
security
around
it,
etc.
D
So,
as
we
move
beyond
customizing
module
resolution,
loading
there's
been
a
desire
to
maybe
make
like
more
formal
apis
for
the
types
of
customizations
that
the
typescript
team,
that
instrumentation
teams
like
datadog,
and
also
that
that
one's
mostly
covered
by
like
the
diagnostic
channel
and
the
other
one
is
the
yarn
team
with
with
plug
and
play.
I
think
arkansas
here
is
a
member
of
that
team
like
plug
and
play,
tries
to
load
everything
essentially
from
a
virtual
file
system.
D
D
You
know
the
work.
The
term
loaders
is
a
little
confusing
since
we
have
a
a
load
hook
and
if
you
look
at
the
the
docks,
it's
like
loaders
hooks,
you
know,
and
then
we
define
like
these
are
our
three
loader
loader
hooks,
so
we've
kind
of
been
discussing
off
and
on
for
a
long
time
like.
We
should
just
call
this
the
hooks
api,
because
we're
providing
hooks
for
people
to
register
functions.
D
Maybe
that's
too
broad,
because
the
other
types
of
hooks
in
the
code
base,
like
asynchronous
performance,
hooks
we're
open
to
suggestions
this
this.
This
has
been
discussing
it,
so
I
wanted
to
just
like
not
that
the
tsc
needs
to
make
that
decision,
but
I
just
wanted
to
make
you
aware
that
that
conversation
was
happening
if
people
wanted
to
chime
in
on
this
issue.
D
D
D
That's
not
just
like
you
know:
command
line,
flags
or
environment
variables,
but
they're
more,
like
hey.
Here's.
A
custom
function
run
this
at
some
defined
point
in
node's
internal
flow,
so
that
was
kind
of
the
broader
discussion.
That's
spun
out
of
you
know:
hey.
We
should
have
a
better
name
for
our
team,
so
I
just
wanted
to
bring
that
up
with
the
with
the
tse.
A
There
any
questions
that
we
need
to
cover
before
we
go
to
on
this
before
we
move
on
to
the.
I
think
we
wanted
to
finish
around
this
time.
I
might
just
quickly
read
the
strategic
initiatives
part,
but
is
there
anything
else
on
this
before
we
move
on?
We
should
talk
about.
D
Yeah,
I
maybe
comment
on
this
thread.
If
I
mean
I
feel
like
at
this
point,
there's
no
other
team
focusing
on
like
customization
issues,
so
that's
kind
of
de
facto
become
ours.
D
I
mean
everyone
comes
to
us
for
that,
because
they're
used
to
monkey
patching
from
common.js,
so
they
feel,
like
you,
know,
hey
the
api
that
allows
monkey
patching
must
be
where
I
go
to
customize
node,
so
it's
kind
of
naturally
become
our
scope,
but
if
the
tsc
has
ideas
for
how
to
better
manage
like
that
aspect
of
node
to
split
about
the
like
the
non-module
customizations,
you
know
yeah,
please
reach
out
to
me
and
comment
on
that
issue
and
we
can
keep
talking
about
it
where
we
can
reschedule
it
for
the
next
dsc
meeting.
D
A
Thanks,
okay,
so
just
the
last
thing
was:
the
strategic
initiative
saw
the
va
currency,
michael
posted,
that
the
updates
are
still
blocked
in
various
issues.
So
if
anybody
has
time
to
go
help
with
those
different
issues,
that'd
be
great
joey.
Do
you
want
to
just
quickly
cover
startup
performance.
C
Sure
I've
unblocked
the
I've
removed
the
blocker
fixed
the
blockers
of
the
runtime
snapshot,
progress
so
but
we'll
be
sending
it
out
for
review
this
week.
Hopefully
yeah.
A
Okay,
great
and
on
the
next
10
front,
just
mentioned,
as
mentioned,
there's
some
discussion
about
helping
to
set
up
the
session
on
typescript
related
stuff,
we're
planning
a
session
on
threading
at
the
next
collaborator
summit
and
working
through
some
of
the
actions
in
the
technical
priority
working
summary
and
related
issues
in
the
next
10
repo,
if
anybody's
interested.
A
So
with
that,
maybe
we'll
close
out
and
move
to
the
private
session.
Unless
there's
anything
else,
somebody
thinks
we
should
cover.