►
From YouTube: Node.js Technical Steering Committee meeting 2019-08-07
Description
A
Okay,
we're
now
live
with
the
August
seventh
meeting
of
the
nodejs
technical
steering
committee.
We've
got
eight
of
us
on
the
call
and
not
the
largest
agenda.
We've
ever
had
not
the
smallest
agenda.
This
is
you
know
the
agenda.
That's
just
right!
So
we'll
start
with
announcements.
Does
anyone
have
any
announcements
they'd
like
to
make
new
releases
yesterday?
A
A
B
Real
quick
yeah
go
for
it.
No,
we
could
probably
skip
this
one
Anatoli
started.
It
posted
a
comment
and
there's
now
a
conversation
back
forth
like
as
of
like
an
hour
to
ago
conversations
moving
again
and
that's
that's
the
main
thing
we
want
to
make
sure
it's
happening.
There's
no
decision
to
be
made
right
now,
they're
they're,
discussing
anatoly's
concerns,
and
we
should
leave
it
on
the
agenda
for
next
week,
but
we
don't
need
to
talk
about
it
this
week.
I
don't
think.
A
C
C
D
Yeah
well,
I
think
I.
Okay,
so
obviously
doing
this
would
require
I
think
more
stuff
because
it
would
produce
more
builds.
I
I'm
sure
this
has
probably
been
talked
about
in
the
past
that
maybe
it's
possible
to
produce.
Oh
I
see
you
build
as
well,
but
I
I'm,
not
I'm,
really
not
sure
the
default
builds
should
be
done
just
because
it
really
does
add
a
lot
of
sort
of
like
weight
in
that
respect
to
know
Jess
exam
a
lot,
but
your
binary
I'm
not
really
sure.
A
So
there's
there's
a
comment
from
eleven
days
ago.
That
has
a
little
bit
more
specific
numbers
here,
so
it
add
about
eleven
megabytes
to
the
git
checkout,
but
you
know
the
get
checkups
already
around
like
half
a
gig,
so
it's
not
a
huge
increase.
It
doesn't
seem
like
it
would
really
affect
compile
time
too
much
and
the
binary
would
be
five
point.
Five
megabytes,
which
is
about
30%,
larger
personally
I,
would
love
to
see
a
slim
down
the
binary,
if
possible,
like
especially
with
how
many
people
are
using
node
now
in
serverless
environments.
A
Well,
binary
size
does
not
necessarily
make
like
a
huge
difference
for
cold
starts.
It's
not
negligible
so
I'm.
Personally,
not
a
huge
fan
of
seeing
us
make
the
binary
size.
Much
larger
I
would
love
to
see
some
evidence
of
like
people
specifically
requesting
this.
It
seems
like
those
who
are
interested
in
internationalization
I'm,
not
saying
everyone
shouldn't
be,
but
those
who
are
working
directly
on
internationalization
want
to
see
the
full
line.
Tl
but
like
I
personally,
have
not
seen
like
a
large
number
of
issues
of
like
individuals
who
are
asking
for
it.
A
B
A
Making
sure
it's
okay
with
you
yeah,
it
seemed
like
from
what
I
was
reading
on
here,
and
this
is
something
to
maybe
take
to
the
build
group.
The
issue
is
more
about
like
the
stuff
and
downloads
not
being
fronted
by
the
CDN,
which
is
something
that
independently
we
should
be
looking
at,
but
yeah.
This
is
something
we
could
maybe
find
some
different.
A
B
A
A
Gonna
get
that
file
open,
and
so
for
those
of
you
who
are
watching
on
the
stream.
The
note
G
has
technical
steering
committee
started,
keeping
a
strategic
initiatives
document
a
couple
years
ago
now
and
in
it
we
outline
all
the
different
things
that
we
are
working
on
that
are
like
high
priority.
We
used
to
do
kind
of
like
a
stand-up
that
was
about
individuals,
work,
and
now
we
have
the
stand-up
that's
more
about
like
specific
initiatives.
A
So
if
you
go
to
the
TSC
repo
there's
a
strategic
initiatives
markdown
and
we're
just
going
to
kind
of
walk
through
this
and
give
an
update,
so
the
first
one
that
we
have
is
modules.
That's
me,
modules
is
coming
together
well
and
we
are
still
aiming
to
hopefully
unflagged
prior
to
the
node
12
LTS
in
October,
the
kind
of
there's
like
three
or
four
big
things
that
we
need
to
figure
out.
A
First,
we
don't
yet
have
consensus
a
hundred
percent
on
if
we
want
to
keep
some
of
the
design
decisions
that
we've
made
specifically
about
not
allowing
dual
entry
points
that
would
allow
like
you
to
have
a
separate
entry
point
for
ESM.
Then
then
commonjs,
the
other
one
is
like
the
file
extension
resolution
algorithm
we
no
longer
automatically
resolve
file.
Extensions
I
saw
personally
I
have
the
bias
of
not
wanting
to
see
either
those
features
reintroduced,
but
we
haven't
reached
full
consensus
in
the
group
about
that.
A
Then
there's
two
features
that
we're
working
through
one
is
called
exports,
I,
don't
know
if
everyone,
the
TSA,
has
seen
this
yet
I
believe
that
it's
landed
in
12
as
an
experiment
will
feature
behind
a
fat,
a
flag
that
allows
you
to
to
define
the
exports
of
a
module.
So
what
you
can
get
through
deep
searching
in
a
module
and
only
and
like
it
limits
the
exports
to
only
the
ones
that
are
defined
in
the
package.json.
A
The
version
that's
upstream
now
and
twelve
as
far
as
I
know
now
supports
both
common
j
s
and
es
m,
and
so
there's
work
being
done
stabilizing
that
feature
as
well
as
some
of
the
like
DX
and
behavior.
For
it
the
other
one
is
loader
hooks.
So
this
is
the
ability
to
write
custom
hooks
that
change
the
way.
What
happens
when
you
import
a
module?
This
is
extremely
important
for
stubbing
modules
or
for
intercepting
modules,
which
is
work
that
a
PMS
have
to
do.
A
It's
a
feature
that
we
want
to
have
at
the
very
least,
mostly
sketched
out,
so
we're
hoping
that
in
the
next
two
to
three
weeks,
we'll
have
a
better
idea
of
the
rest
of
the
roadmap,
but
we're
still
as
far
as
I
know,
on
track
for
a
very
least
having
no
flag,
maybe
remaining
experimental
for
a
little
bit
when
we
go
into
LTS
James,
that's
what
we
did
for
HTTP
two,
if
I
recall
right.
Okay,
sorry,
I.
C
C
C
A
A
A
A
A
A
A
Okay,
so
we'll
move
to
the
next
one
open
web
standards,
that's
myself
and
Joey
Joey
he's
not
on
the
call.
So
I
will
take
this.
We
have
a
standards
initiative
that
spun
up
under
the
open,
Jas
umbrella
and
we've
started.
Having
some
meetings,
I
think
part
of
the
idea
is
running
a
pre-meeting
before
tc39.
We
can
review
things
and
make
sure
we're
all
on
the
same
page.
I
think
there's
also
some
work
being
done.
Looking
at
like
adopting
some
more
of
these
standards
in
core,
but
this
is
still
very
high
level.
A
B
Hopefully,
we'll
get
an
update,
actually
actually
just
I'm
gonna.
Put
a
note
in
that.
We
had
agreed
last
time.
I
thought
that
we
were
going
to
invite
Christian
Klaus
to
these
meetings
to
to
sort
of
help
the
Python
3
thing
you
know
you
can.
You
can
tell
us
where
things
are
at
what
he's
stuck
on
what
we
can
do
to
help
move
us
forward.
So
I'll
leave
a
note
to
that
effect.
Unless
anybody
objects.
C
Progressing
along
nicely,
it's
a
really
big,
complicated
protocol.
The
implementation
is
equally
big
and
complicated.
The
the
biggest
issues
I've
had
have
actually
been
getting
it
yeah
to
work
reasonably
well
within
existing.
You
know,
api's
and
like
API
expectations,
but
making
progress
on
it
still
looking
at
the
goal
of
opening
the
PR,
probably
you
know,
realistically,
it's
probably
going
to
be
mid,
September
opening
the
PR
get
landed
in
in
in
the
main
repo
as
experimental.
C
A
B
B
The
basic
the
basic
improvement
is
that
when
tests
fail
in
a
certain
way,
NCI,
instead
of
it
causing
a
subsequent
test
to
fail,
it
will
show
up
as
the
test
that's
actually
causing
the
failure
causing
the
failure.
If
that
makes
sense,
it
has
to
do
with
the
way
Windows
deals
with
Tempah.
It
deals
with
the
temp
directory
in
our
in
our
tests.
B
A
E
A
The
next
thing
on
the
agenda
is
a
tracking
issue
for
an
update
on
CPC
and
board
meetings.
I
can
handle
that
today
so
biggest
things
that
the
CPC
this
week
we're
the
landing
of
the
official
process
for
new
projects
applying
to
the
foundation.
That's
one
of
the
bigger
ones,
that's
available
in
the
main
repo
there's,
an
email
address
and
a
template
to
fill
out.
That
goes
through
a
small
internal
private
discussion
with
the
CPC
voting
and
non-voting
members.
A
Just
it's
like
a
silent
cure
to
make
sure
there's
no
like
really
really
large
objections.
If
there's
no
larger
objections,
then
projects
go
into
an
incubating
period
and
during
that
incubating
period,
all
that
kind
of,
like
due
diligence,
is
done
to
onboard
them
into
the
foundation.
If
anyone
has
questions
about
that,
please
feel
free
to
reach
out.
I
have
helped
draft
a
bunch
of
that
with
Jordi
Burson,
so
I'm
pretty
familiar
with
how
the
process
works.
A
If
you
have
projects
that
you
think
would
make
sense
in
the
foundation,
you
know
it's
a
good
time
to
maybe
try
to
get
them
in
the
other
one
that's
going
on.
That
is
worth
people's
attention.
Although
I
think
there's
some
issues
that
have
been
opened
is
the
travel
fund,
and
so
there's
been
the
discussion
about
moving
the
management
of
the
larger
travel
fund
to
the
cross
project
Council.
A
This
would
be
specifically
the
fun
that's
Dell
that
that
is
for
for
the
collaborator
summit,
since
the
collaborator
summit
is
expanding
beyond
just
nodes,
similar
to
what
we
did
in
Berlin.
This
does
not
mean
that
the
node.js
project
itself
could
not
have
it
and
maintain
its
own
separate
travel
fund,
but
I
think
that
the
intention
was
that
if
we
wanted
to
maintain
a
travel
fund,
it
would
be
a
smaller
fund
for
non-foundation
related
activities.
So
you
know
that's
similar
to
like
when
we
send
people
to
tc39
or
when
we've
sent
people
I.
A
Think
like
we
have
one
request
right
now
to
send
someone
to
a
very
specific
node
event,
so
we
still
have
the
ability
to
have
and
maintain
our
own
budget,
but
you
know
we
would
no
longer
be
responsible
for
maintaining
the
broader
travel
fund.
Now,
with
that
being
said,
since
all
of
us
can
be
cross
proud,
like
attend
the
cross
project,
Council,
anyone
who
has
been
participating
in
the
travel
fund
and
wants
to
continue
to
do
so
can
do
it
in
the
exact
same
way.
A
The
there
is
a
process
that
it's
going
through
the
new
travel
fund.
It's
still
only
at
stage
one
in
the
process,
hopefully
moving
to
stage
two
tomorrow.
So
no
it's
moving
to
stage
one
tomorrow,
so
there's
still
a
lot
of
room
to
augment
how
it
would
work
before
it
lands.
So
if
people
have
any
thoughts
about
that,
there's,
a
pull
request
open
that
you
can
chime
in
on.
Does
anyone
have
any
questions
about
that
before
I
move
on.
A
Okay,
one
thing
that
I
think
is
worth
letting
everyone
know
about
just
in
case
you're
not
aware
there
is
lists,
thought
up
in
JSF
org
and
that's
a
handful
of
different
mailing
lists
for
the
foundation
itself,
including
a
mailing
list
for
the
projects.
There's
an
announcement
mailing
list
on
the
project's
mailing
list.
A
The
next
meeting
is
coming
up
on
the
23rd
far
as
I
know,
I,
don't
think
that
there's
any
specific
business
at
this
upcoming
board
meeting,
but
if
anyone
has
things
that
they'd
like
brought
to
the
board,
you
know
it's
between
now
like
in
the
next
week
or
so
we'll
plan
to
raise
it
since
Michaels
out
of
office.
Right
now,
please
feel
free
to
ping
me
about
that
in
case
you're
not
aware,
I'm
still
on
the
board,
but
I've
now
Google's
rep
on
the
board
rather
than
representing
node
or
the
up
and
Jas
foundation.
A
You
know
I'm
still
very
much
wearing
my
nut
hat
well
playing
between
hats
while
in
there
but
I'm
still
very
much.
You
know
thinking
about
the
interests
of
the
node
project
during
the
recession.
So,
as
always,
please
feel
free
to
come
to
me.
If
you
have
any
thoughts,
concerns
or
questions
and
with
that
I
think
that's
the
whole
agenda.
Does
anyone
have
anything
else
to
bring
up.