►
From YouTube: 2022-09-13-Package Maintenance Team 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
So
welcome
to
the
node.js
package
maintenance
team
meeting
for
september
13th
2022
we'll
follow
the
agenda
from
the
issue
that
was
in
the
repo
which
was
issue
number
538.
Before
we
get
started
any
announcements.
People
would
like
to
share.
A
If
not
I'll
just
mention
the
collaborative
summit
is
coming
up
in
dublin
at
the
end
of
september,
beginning
of
october,
so
if
you're
a
collaborator
or
interested
in
becoming
one,
this
is
a
good
way
to
sort
of
get
to
meet
some
of
the
other
collaborators
and
ramp
up
on.
What's
going
on,
okay,
so
we'll
move
over
to
the
issues,
so
the
first
one
is
how
to
accelerate
modernization
of
the
ecosystem
number
513.
A
B
B
Yeah,
I
think
the
I
I
did
comment.
I
think
it
was.
B
Volley
back
to
the
the
op,
but
I
think
the
the
gist
of
the
conversation
coming
out
of
that
initial
post
was
what
does
modern
actually
mean,
and
you
know
is
like
say
say:
maybe
using
experimental
fetch
over
http
like
a
significant
or
meaningful
sign
of
modernization,
and
so
I
think
dominic
has
pointed
out
that
we
have
a
deprecation
guidelines
stuff,
and
so
I
think
it
was
maybe
more
about.
B
Like
our
some
sort
of
like
another
risk
assessment,
I
don't
think
the
premise
of
basing
it
on
like
syntax
or
api
usage
alone.
I
think
if
that
was
a
deprecated
api
because
of
security
reasons,
that's
that's
something
entirely
different,
but
even
at
work,
I'm
finding
cases
where
I
just
want
to
use
https
to
just
kind
of
cut
through
a
bunch
of
library
stuff
you
know
like.
Is
that
really
wrong?
All
right,
so
I
glued
together
by
certs
instead
of
offloading
it
all
to
another
library
like?
Is
that
really
that
bad?
B
B
A
A
B
I
guess
the
the
duality
of
the
node.js
module
system.
You
know,
I
think,
sometimes
yes,
I
mean
it's
modern
in
the
way
that
it's
like
more
of
like
esm,
I
guess
benefits,
maybe
more
from
like
a
recency
bias,
not
necessarily
like
a
you
know.
I
mean
everything
has
its
trade-offs,
there's,
certainly
things
in
esm
that
you
could
do
in
common
js
that
just
aren't
there
yet.
So,
if
I'm
actually
trying
to
do
all
the
things
I
want
to
do,
I
might
want
common
js.
You
know.
B
I
know
that
even
in
like
babble
plug-ins
or
like
some
presets,
they
literally
use
like
2015
as
the
cut
off
of
like
modern.
Maybe
that's
a
little
bit
different
for
browsers
and
stuff.
Anyway,
I
think
the
conversation
is
valuable.
B
There
is
good
argument
to
keep
updating
that
guideline,
but
it
seemed
like
the
preponderance
or
the
a
lot
of
it
was
folk
if
the
op
was
focused
more
on
what
apis
am
I
using
you
know
and,
like
I
said,
you
know,
there's
probably
more
to
mine
there
rather
than
like
you
know,
api
a
versus
api
b,
so
yeah,
I
guess
yeah
close
it,
but
you
know,
I
think
it's
certainly
worth
calling
out
like.
We
want
to
keep
the
discussion
going
start
with
that
doc
and
you
know
yeah
yeah.
B
D
By
just
scanning,
for
the
conversation
seems
to
be
very
yeah,
it's
very
chart
term,
so
maybe
just
breaking
down
the
conversation
like
that
request
comment
like
that's
a
very
good
one
like
the
library
is
deprecated,
but
still
have
millions
of
downloads.
Every
week,
like
maybe
that's
a
conversation.
Words
have
like
a
part
of
this
specific
issue.
B
Yeah,
I
think
so,
like
jordan's
point
like
does
using
cjs
versus
esm,
necessarily
make
your
app
more
or
less
insecure
versus
using
something.
That's
like
officially
deprecated.
You
know
dependencies
or
so
I
think
it's
more
question
about
like
risk.
I
guess
like
the
way
that
like
say
socket,
I
was
thinking
about
hey
a
patch
release
just
introduced
a
bin
in
its
package,
json
that
seems
kind
of
suspicious.
You
know
things
a
little
bit
more
underneath
the
surface,
but
yeah.
B
A
No
okay,
the
2022
promotion
events.
I
think
this
one.
You
know
we
had
some
some
ideas
of
some
promotion
to
do.
I
don't
know
that
we've
made
any
progress
on
that.
I
can't
remember
if
it
was
this
group
I
asked
before,
but
like
are
other
people
going
to
be
at
the
collaborator
summit.
B
Well,
maybe
that
last
issue
could
be
a
good
collaboration
topic
with
the
npm
cli
team.
You
know:
do
they
have
an
opinion
on
the
matter?
They
may
leave
a
document.
We
might
not
even
have
to
write
anything
else
which
issue
the
the
what
we
were
just
talking
about.
Oh
right,
modern
packages-
so
I
know
obviously
npm
is
you
know,
does
a
lot
around
security
and
flagging
and
signals-
and
you
know-
maybe
I
don't
know
if
they're
less
opinionated
or
more
opinionated
than
say
a
group
like
this.
D
A
D
A
A
D
A
D
A
A
Into
the
promotion
we
can
have
a
you
know
basically
again
promote
it
to
people
collaborators
who
might
be
there,
and
the
status
and
update
of
next
steps
for
pkgs
create.
A
I
don't
think
there's
there's!
No,
I
don't
think
there's
an
update,
but
I
still
think
that
one
might
be
actually
a
good
one,
even
a
good
one,
to
discuss
in
the
collaborator
summit
if
there's
anybody
who's
sort
of
eager
to
get
started
on
something
that
one,
I
think,
is
quite
interesting
and
useful
right
in
in
terms
of
like,
if
we
had
some
project
opinions
on
time,
how
you
start
the
creation
of
your
modern,
your
modules,
integrating
the
support
info,
integrating
some
other
things
and
stuff.
A
The
next
one,
I
don't
think,
there's
any
update
either
in
terms
of
suggested
list
of
modules,
but
you
know
might
be
related
a
little
bit
to
the
pkgs
create
now
that
takes
us
to
the
end
of
the
agenda.
I
don't
know
if
there's
any
other
issues
that
oh
there's
zach,
sorry
I'm
gonna
promote
him
and
he
might
I
know
at
one
point
I
think
he
was
looking
at
that.
So
maybe
he
has
enough
stuff.
C
Yeah,
can
everyone
hear
me
fine,
yes,
yeah,
so
I've
been
keeping
an
eye
on
the
repo.
Since
I
was
my,
my
status
was
updated.
Mainly
I've
just
been
closing
the
the
dependable
pr's,
because
I
plan
on
going
through
and
doing
a
full
pass
on
the
on
the
dependencies
and
everything
and
really
I
want
to
look
at
the
there's,
a
open
pr
from
way
back,
which
is
like
the
basis
of
the
1.0.0-rc
one
or
two
I
think
for
pkgs
create.
C
So
I
want
to
look
at
getting
the
network
merged
in,
and
you
know
formalized
and
everything
and
moving
forward
based
on
that
since
the
code's
being
used
and
published
on
npm.
So
that's
kind
of
what
I'm
looking
at
my
next
steps.
I've
been
kind
of
held
back
by
other
life
events
and
stuff,
but
yeah.
A
A
Bit
and
then
moving
forward
sounds
sounds
good,
okay,
any
other
issues
we
should
talk
about
before
we
close
out
for
today.