►
From YouTube: Open RFC Meeting - Wednesday, November 24th 2021
Description
In our ongoing efforts to better listen to and collaborate with the community, we run an Open RFC call that helps to move conversations and initiatives forward. The focus should be on existing issues/PRs in this repository but can also touch on community/ecosystem-wide subjects.
A
And
we're
live
on
youtube.
Welcome
everybody
to
another
npm,
our
open
rfc
call.
Today's
date
is
november
wednesday
november
24th
2021.
I
will
be
following
along
in
the
agenda
that
was
posted
in
the
rfc
issue,
495
I'll
copy
and
paste
that
reference
for
folks
and
quick
reminder.
A
These
calls
and
all
communications
on
the
fcc's
repo
are
covered
by
a
code
of
conduct,
and
we
just
asked
folks
to
please
be
kind,
as
others
are
speaking
and
please
raise
your
hand
if
you'd
like
to
talk
when
somebody
else
is
and
we'll
call
upon
you
and
quickly
wanted
to
give
the
floor
for
folks
that
had
any
announcements.
A
If
not,
I
know
that
there's
some
holidays
coming
up
american
thanksgiving
is
this
week,
so
just
an
announcement
there
and
hope
folks
are
taking
some
time
off
and
enjoying
time
with
friends
of
family
this
week.
A
The
one
other
note
we
are
cutting
a
release
next
week
of
npm
cli,
we
did
not
cut
one,
I
think
a
week
or
two
ago,
based
on
some
time
off.
So
please
downl.
A
And
yeah
we'll
just
dive
right
into
it.
We
have
us
very
short
agenda,
only
three
items,
and
I
think
that
the
three
authors
of
the
rfcs
that
we've
got
on
the
table
today
are
all
unable
to
join.
A
So
this
might
be
a
short
call
unless
folks
want
to
bring
up
other
topics,
the
first
of
which
is
rfc
488,
make
npm,
install
scripts,
opt-in
and
francisco.
I
did
not
see
his
attendance,
but
this
is
essentially
the
rc
that
is
proposing
that
we
default
to
opting
out
of
installing
or
running
install
scripts
during
npm
install,
I'm
not
sure.
If
there's
any
updates
folks
want
to
share
or
any
commentary,
anybody
wanted
to
give.
A
Nope
I'll
reference,
the
link
and
rc's
just
for
folks
if
they
want
to
give
async
feedback.
I
know
that
on
our
side
we're
trying
to
collect
some
more
data
in
terms
of
the
usage
of
post,
install
scripts
as
well.
As
I
know,
the
run
kit
team,
which
tomoski
is
a
part
of,
have
been
doing
some
of
their
own
investigation
here.
So
ideally,
there
will
be
some
follow-ups
with
actual
results
of
that
investigation.
A
A
Ideally,
this
will
inform
you
know,
usage
patterns
and
what
at
the
npm
cli
would
need
to
introduce
in
terms
of
net
new
features
that
would
help
drive
people
away
from
using
lifecycle
scripts
for
things
like
downloading
native
binaries
or
or
building
having
some
sort
of
mutable
step
within
building
their
packages,
and-
and
ideally
you
know,
making
it
more
likely
that
people
are
falling
into
better
patterns
with
distributing,
let's
say
immutable
package,
artifacts,
so
cool.
A
If
there's
no
other
commentary
that
folks
will
have
to
give
on
that,
we
can
jump
into
the
next
rfc,
which
was
pr481.
This
is
the
prepare
scripts
for
linked
bundle
dependencies.
I
know
that
matt
aka
mystery
command
again
also
wasn't
able
to
attend
today,
but
has
been
working.
I
think
with
michael
pratt
and
some
other
folks
on
on
getting
us
over
the
finish
line.
Jordan
and
isaac
have
a
rfc
they're
meant
to
create
as
well
guard
did
you
want
to
speak.
B
To
this
tangential
to
this
this,
I'm
remembering,
do
we
have
a
similar
issue
with
git
dependencies,
and
specifically,
I
think
even
the
github
folks
have
raised
this
as
an
issue
where
prepare
doesn't
run
for
certain
get
dependencies
too.
Am
I
remembering
this
correctly
and
is
this
a
class
of
problems
that
we
can
overlap
with
with
this
solution,
or
am
I
remembering
incorrectly.
A
I
think
you
might
be
right:
I'd
have
to
go,
find
the
bug.
There
might
be
a
bug
in
the
cli
repo
that
we
can
go
find.
I
don't
think
that
they're
the
same,
I
think
the
the
the
different
classes
of
issues.
I
think
that
the
workspace
we
don't
treat
get
repos
or
get
dependencies
the
same
as
we
do
like
link
depths
right,
and
so
it
seems
that
workspace
is,
it
seems
like
these
are
orthogonal
yet
similar
problems.
B
A
Oh
I
apologize
miles.
I
know
you're
dealing
with
bugs
today
yeah
it
might.
A
This
might
be
a
problem
in
other
places
as
well.
We're
just
not
being
made
aware
of
it,
but
definitely
workspaces,
not
running
lifecycle.
Scripts
seems
to
be
like
yeah,
a
major
bug
as
well
as
get
repository
so
yeah.
Do
we
have?
Can
you
find
that
issue
potentially
car
just
so
that
we
surface
that
at
the
same
time,
I'll
try
and
find
it?
Yet
thanks
cool?
A
Did
anybody
else?
Have
any
comments
on
this
481?
I
know
miles.
You
just
joined
we
sort
of
skipped
over
pr488,
which
is
the
npm
install
scripts
being
opt-in,
and
I
just
noted
essentially
there's
more
research
being
done
here,
not
sure
if
you
had
anything
else,
you
want
to
add
on
that
previous
note,.
A
If
not
no
worries-
and
I
know
that
you're
got
some
zoom
bugs
today,
so
cool.
Let's
move
on
then
to
the
last
item
we
had
and
then
I
will
open
up
the
floor
for
any
other
discussion,
pr,
375,
defining
which
defenses
are
shared
among
workspace
projects.
I
believe
this
is
still
a
work
in
progress
with
isaac
and
jordan
and
we'll
need
to
poke
them.
I
think
asic
to
to
get
an
update
on
the
status
of
this.
A
I
know
that
also
vincent
bailey
who's
been
actually
working
on
the
isolated
mode.
Implementation
is
actually
out
this
week
on
vacation,
otherwise
he's
another
person.
That
would
be,
I
think,
key
to
speaking
to
this.
A
If
not,
then
I
think
we
can
skip
that
item.
Was
there
any
other
discussion
topics
folks
wanted
to
bring
up
for
today.
A
I
guess
I
will
note
that
there's
a
few
internal
drafts
of
rc's
that
our
team
is
working
on,
most
of
which
are
actually
on
this
call
right
now,
and
I
expect
that
we'll
probably
be
opening
up
a
few
new
rc's
going
forward
here
in
the
next
month
or
so,
which
I'm
pretty
excited
for
so
just
be
on
the
lookout
for
that,
but
yeah.
If
there's
no
other
discussion
topics,
people
want
to
bring
up
I'll,
give
you
a
time
back
and
we
can
end
early
today.
A
Cool
okay,
I
will
see,
hopefully
see
y'all
next
week
same
time
same
place
and
feel
free
to
continue
to
give
feedback
and
add
new
rfcs
in
the
repo
itself
and
I'll
talk
to
you
soon.