►
From YouTube: Beyond npm Install... - Darcy Clarke, npm Inc.
Description
Beyond npm Install... - Darcy Clarke, npm Inc.
Discover capabilities of npm & the npm registry you never knew existed.
A
Awesome,
hello,
how's
it
going
everyone
good
how's,
the
day,
good
yeah,
you
sound
super
enthusiastic,
it's
the
last
talk
of
the
day.
I
have
the
privilege
of
having
less
talk
today.
Thank
you
very
much
for
joining
me.
You
can
be
anywhere
else,
but
you
are
here
which
is
awesome,
so
I'll
be
mindful
of
your
time.
A
This
was
sort
of
a
last
minute
talk
that
has
been
evolved
from
a
couple:
meetups
talks
that
I
have
thrown
together
and
just
quickly
the
node
folks
on
the
weekend.
We're
like
hey.
You
want
to
do
a
talk
cool
so
today,
I'm
going
to
be
talking
a
little
bit
things
that
you
may
not
know
about
NPM
and
some
cool
stuff
that
we're
doing
that's
said
before
we
get
started
last
talk
of
the
day,
I'm
sure
everybody's
tired.
Would
you
do
me
a
favor
and
all
stand
up?
A
Okay,
you
can
sit
down,
got
some
oxygen
in
your
heads
now.
Hopefully,
last
talk
today:
you'll,
listen
and
retain
some
of
the
information.
I've
got
awesome
cool.
So,
let's
get
started.
My
name
is
Darcy
Clark,
that's
cool
astronaut,
hat
I
have
a
background
as
sort
of
a
developer
designer
speaker,
entrepreneur,
mentor
UX
advocate
I
love
designs.
A
My
official
title
right
now
is
the
engineering
manager
for
community
and
open
source
at
NPM
Inc,
this
small
little
company.
This
was
a
good
note.
I
stole
this
idea
for
miles
this
morning.
That
opinions
are
my
own.
Indeed,
the
love
I
give
is
also
my
own,
and
so
the
love
I
give
to
you.
It
is
mine
and
I
give
it
to
you
as
a
real
human
being
free
of
charge,
and
we
can
have
hugs
later.
If
you
want
they're
for
your
church,
quick
show
of
hands
who
writes
JavaScript's.
A
Yes,
you're
my
people,
who
writes
no
okay,
even
better
you're
at
the
right
conference,
MPM
who
uses
fpm
great.
Thank
you.
Thank
you
who
uses
yarn?
It's!
Okay!
That's!
Okay!
That's
okay!
We're
all
friends!
Anybody
use
yarn
with
a
PMP,
you
flag!
Anybody
try
to
test
it
out;
no
plug
and
play
okay.
Anybody
just
PMPM!
Anybody!
A
Hey
cool,
look,
okay,
cool
you're,
probably
like
thinking
is
he
having
a
stroke
what's
being
cool,
so
I'm
sure
everybody
has
run
this
right.
Anybody
run
this
today.
Anybody
yeah
it's
couple
Roy
who
works
on
my
team,
so
you
do
this
a
lot
right!
You
do
this
a
lot,
a
lot,
a
lot
a
lot
and
your
CI
systems
are
probably
running
this
right.
They
run
this
a
lot
even
more
lot
lot
lot.
This
is
sort
of
the
BART
system,
like
writing
on
a
chalkboard
type
thing.
A
A
Hundred
million
anybody
gonna
go
for
like
one
prices,
right
style,
no,
okay,
yeah,
okay,
so
we
are
58
plus
billions
so
that
you
guys
really
like
to
install
you
folks
would
like
to
install
packages
right
and
just
to
show
you
a
little
graph
about
this
sort
of
exponential
growth.
Npm
celebrated
its
ten-year
anniversary
a
couple
months
ago,
and
we
have
this
nice
little
video
I'm
sure
for
good
of
audio.
A
Jquery
moves
plug-in
stamp
yum
awesome,
huge
milestones,
right,
IP
m5s,
released
in
2017
MPX,
a
lot
of
people
use
MPX,
yeah
nice,
one
of
the
best
things
in
the
world,
yeah
holy
cow,
so
over
a
million
packages
published
that's
awesome,
ten
years
cool.
So
that's
all
awesome.
But
let's
look
beyond
that
right!
You
do
this
thing
a
lot.
You
know
it
a
lot
of
it.
A
lot
probably
probably
know
better
than
I
do
so.
Let's
talk
about
these
things,
these
these
disparate
things,
we're
gonna
talk
about
the
PACU
minute.
A
How
many
know
what
that
is
already
a
lot
of
people:
great
sweet,
I'm
gonna.
Tell
you
a
little
bit
about
something
that
you
don't
know.
We
talked
a
little
bit
about
sustainability,
the
community
maintenance
in
contributing
and
a
few
other
things
I'm,
even
gonna
showcase,
some
cool
stuff
that
I
don't
think
you've
seen
yet
so
what
happens
when
you
install
sir,
the
coals
notes
here
and
we
actually
fat
to
fetch
this
thing
called
a
packet,
and
so
the
NPM
CLI
touches
the
document,
and
that
has
a
reference
to
where
the
tar
ball
lives.
A
A
So
if
you
ever
hear
node
node
folks
talking
about
document
objects
or
POC,
you
mints,
they're,
talking
about
package
documents,
fun
right,
cool,
it's
kind
of
like
codec
right,
everybody
know:
codec
is
like
also
look
yeah,
okay,
well,
I
know:
I
got
a
lot
of
people
didn't
know
that
slaves,
just
like
compression
and
decompression
codec,
put
together,
really
cool,
sorry,
coder
decoder,
yeah,
coder
or
encoding
I'm
cool.
So
this
is
what
it
looks
like.
This
is
a
sort
of
the
shape
of
this
object.
It
looks
a
lot
like
a
package.json
right.
A
It's
got
a
bunch
of
information
in
here,
but
it's
got
some
information
in
here
that
you
may
not
have
thought
it's
got
references
to
maintain
errs
it's
where
it
got
references
to
all
the
versions
that
you've
published
and
actually,
if
we
look
I,
can
show
you
a
live
version
of
this.
So
here's
lo
dashes
packing
mints.
It's
sort
of
it's
got
things
like
this
tags
on
it.
A
This
is
mutable
data
that
essentially
NPM
controls,
and
so
let's
say
you
add
or
remove
somebody
from
your
team,
the
maintainer
x'
object
will
update
accordingly
right.
So
this
is
not
immutable
data.
This
is
mutable
data.
That
is
not
a
one-to-one
mapping
to
your
package
JSON,
but
it's
something
a
little
bit
more
substantial
and
you
can
actually
go
and
check
out
this
information.
The
URL
is
just
registries
org
and
then
the
package
name
right
cool.
A
So
if
you
take
away
one
thing
from
this
talk
and
you're
like
actually
told
me
one
thing
when
you
hear
a
pack
min
is
not
equal
to
a
package.json
file.
It
is
mutable
record
and
MPM
is
typically
the
source
of
truth
for
all
your
packages.
In
most
cases,
if
you've
ever
used,
yarn
yarn
has
alias
or
essentially
a
cname
which
I
forget
what
the
actual
domain
is,
but
we
actually
mapped
right
directly
to
our
at
the
NPM
registry
so
for
using
yarn,
you're,
actually
using
the
NPM
registry
still
and
for
a
packaged
registry.
A
If
you
can't
find
the
package
in
there,
if
github
can't
find
the
package
information,
it
will
actually
just
proxy
down
to
MPN,
which
is
so
I'm
p.m.
the
registry
is
essentially
the
source
of
truth
for
MPM
packages
cool.
So
that's
a
little
bit
about
sort
of
interesting
information
that
about
your
packages.
You
may
not
know
and
sort
of
high-level
concept
around
that.
Let's
talk
a
little
bit
about
open
source
sustainability.
A
A
You
generate
an
ad
in
your
terminal
right
that
sounds
kind
of
messy
and
it
is-
and
it's
not
necessarily
something
that
we
that
we
think
is
actually
good
for
the
community,
so
NPM
unfortunately
had
to
sort
of
enforce
our
policies
and
say
you
know:
advertising
in
your
terminal
whole
post
install
scripts.
This
is
sort
of
a
abusive.
We
don't
want
to
see
these
types
of
things
happening.
This
is
definitely
something
that
we
don't
think
is
good
for
the
community.
A
That
said,
it
was,
you
know,
definitely
a
symptom
of
something
that,
like
we
know
that
we
needed
to
address,
which
was
how
do
we
support
open
source
software
development?
How
we?
How
do
we
make
it
economical
and
sustainable
for
developers
to
essentially
make
money
through
their
through
their
work
work?
And
so
we
wrote
this
plot
blog
post
in
late
August
and
the
key
here
was,
we
noted.
We
know
this
has
been
a
long
time
coming.
A
Mpm
is
in
a
great
position
to
help
address
this
problem
and
the
time
to
solve
it
is
now-
and
just
so
you
know-
I've
been
at
MPM
for
all
of
about
four
months,
and
this
happened
to
coincide
with
me
starting
there,
so
this
became
my
number
one
goal
is
to
how
do
we
help
or
make
a
difference
here?
So
as
of
NPM
six
thirteen,
we
landed
something
called
funding
who's
heard
of
funding
field:
hey
buddy,
nice,
nice,
anybody
using
it
anybody
define
it
for
the
packages
Wes,
nice
Roy.
A
Hopefully
you
tested
it
right
in
the
back
works
on
my
own
team
he's
actually
the
person
that
implemented
in
the
CLI.
So
the
funding
field
looks
like
this,
and
this
was
a
spec
in
sort
of
a
shape
that
we
had
been
seeing.
Other
third
parties
sort
of
teams
like
open,
collective
and
the
package
maintenance
working
group
had
also
start
to
draft
a
scheme
around
this.
This
type
of
field
that
would
help
define
a
reference
to
a
means
for
you
to
drive
traffic
for
specifically
for
an
option
to
fund
your
your
open
source
development.
A
So
this
is
what
it
has
it's,
a
it's
a
funding
field
and
it's
got
two
keys
there
type
and
URL
type
is
pretty
ambiguous
right
now.
We
don't
actually
have
any
kind
of
like
way
of
sort
of
transforming
from
the
URL
back
down
to,
let's
say
github
and
in
the
future
we
could
see
this
being
utilized
for
things
like
foundation
or
corporate
or
the
the
terminology
could
eventually
become
more
meaningful,
but
right
now
the
type
is
is
pretty
pretty
much
there
for
decoration.
A
The
URL
is
a
really
important
piece
in
this
in
this
spec,
so
something
interesting
now
happens
as
of
NPM
613.
When
you
run
IBM
install
you
get
this
nice
little
prompt.
Three
packages
are
looking
for
funding.
Now
it's
going
to
change
this
number
changes
every
every
time
you
run
this,
but
what
we
are
doing
is
essentially
bubbling
up.
A
When
your
dependencies
have
defined
this
field,
we
were
bubbling
up
the
fact
that
you
know
somebody
has
explicitly
noted
that
they
would
love
if
you
could
help
fund
them
or
that
they
have
a
mechanism
for
you
to
help
fund
or
give
them
given
the
money.
And
if
you
run
the
NPM
fun
command,
it
will
actually
print
out
this
nice
tree
do
some
D
duping
as
well,
which
is
really
nice
and
showcase
these
these
references.
A
And
then,
if
you
actually
brought
an
NPM
fund
with
the
name
of
the
package,
it
works
very
similar
to
MPN
repo
in
which
it
will
try
to
figure
out
where
to
essentially
open
up
a
browser
and
and
where
to
send
traffic.
So
I'll
show
you
what
that
looks
like
so
here
I've
got
terminal,
and
this
is
we're.
Gonna
say
what
version
am
I
on
613
awesome.
A
If
I
Ron
I'm
yeah
minute,
yes,
I
couldn,
you
package.json
I
install
some
depths.
I'm
gonna
install
this
nice
dependency,
I've
made
called
sleepover,
it's
really
fun.
It's
cool
and
I've
defined
the
funding
field
in
my
package.json.
So
if
I
run
MP
I'm
fund,
it
shows
me
my
information,
so
I
have
a
github
sponsors
page
they
referenced
and
if
I
run
an
MP
and
fun
sleepover,
they
actually
prompts
and
opens
up
that
page
right.
A
So
you
can
immediately
go
and
and
donate
or
become
a
sponsor
to
me
feel
free
to
buy
me
a
coffee
if
you'd
like
it's
only
five
dollars
a
month
to
support
me
shameless
plug
cool.
So
this
this
is
something
we
think
is
really
meaningful.
Impactful.
It's
really
just
the
first
step
in
in
us
trying
to
help
solve
this
problem
with
the
community
with
the
community
and
we're
we're
excited
about
where
we
think
it
can
actually
take
us
and
sort
of
moving
forward
and
we've
got
some
some
cool
stuff
coming
down.
A
The
pipeline
that'll
talk
to
a
couple
of
minutes
here,
so
let's
talk
a
little
bit
about
community
so
for
NPM.
Over
the
last
few
years
we
had
actually
actually
last
year
we
sort
of
jumped
over
and
started
using
discourse
forums
to
run
most
of
our
community
discussion
through
and
discourse
through
and
we've.
A
Actually,
since
archived
that
discourse
forum
and
are
now
driving
our
community
back
to
github
and
gap
issues,
we
reopened
issues
on
the
CLI,
which
was
which
was
much
appreciated,
I
think
by
a
number
of
you
know,
folks,
in
community,
and
if
you
actually
go
to
the
landing
page
today,
you'll
see
a
number
of
pieces
of
information
about
public
events
calendar
that
we
now
have
available.
References
to
our
documentation
are
more
tailored
support
portal,
as
well
as
the
archive
for
for
forums
which
still
do
exist
and
let's
talk
a
little
bit
about
maintenance.
A
My
team
has
kicked
off
called
the
essentially
the
project
status
board,
so
you
can
actually
go
to
our
github
org
and
you
can
go
check
out
the
health
of
all
of
our
open
source
projects
and
we're
starting
to
bubble
up
this
information,
not
only
for
our
own
team
to
identify
where
we
need
to
essentially
fix
or
increase
test
coverage
or
update,
licensing
or
terms
or
what
you
know
what
packages
have
vulnerabilities,
but
it
ad,
which
will
help
define
essentially
where
we
spend
our
time.
But
this
is
great
to
also
showcase
and
be
proud
of.
A
When,
let's
say
the
test
coverage
is
a
hundred
percent
on
a
bunch
of
packages,
it's
great
to
show
the
community
that
this
that
we're
working
hard
here.
So
this
is
a
sort
of
a
net
new
tool
that
we're
using
its
inspired
by
West
West
Todd,
who
works
on
packaging
maintenance.
Working
group
works
at
Netflix.
He
built
something
very
similar
for
Express
and
we
sort
of
took
this
concept
and
I've
been
running
with
it.
We've
got
some
really
cool
features
here.
You
can
show
and
hide
columns.
You
can
be
like
who
you
know
who
still
supports.
A
Like
MPI
or
node
version,
0.8
I
think
we
need
to
like
archive
that
project.
So
yeah
and
test
coverage
is
like
terrible,
so
we
need
to
need
to
get
that
in
shape.
So
this
is
really
for
me,
as
in
terms
of
like
an
engineering
manager
or
a
project
manager,
product
manager.
This
is
really
good
because
it
helps
identify
at
in
sort
of
a
high-level
view
that
the
health
of
our
projects,
a
10:00
p.m.
A
so
contributing.
So
if
your
contribute
to
open
source
or
you're
considering
contributor
open
source,
we've
been
trying
to
evolve
in
and
sort
of
grow
the
story
of
how
you
can
contribute
to
NPM
and
in
our
work
we
do,
we
are,
you
know,
usually
radically
as
radically
transparent
as
possible.
You
can
actually
go
check
out
our
Kanban
board.
You
can
go
see
like
how
many
people
have
like
an
open,
cheer
or
Kanban
board
that
you
know
like
everybody
in
the
world
can
look
at
it.
Anybody
anybody
there's
couple
yeah,
Wow!
A
Okay,
if
you
maybe
in
the
open
source,
there's
a
couple
teams
that
will
have
like
opening
up
projects
board.
I,
don't
know
any
other
team
that
does
this
so
I'm.
Just
can't
wait
until
somebody
like
makes
fun
of
me
for
like
how
I've
named
my
columns
or
when
we
like
start
to
move
our
epics
around.
It's
gonna
be
real
fun,
but
you
can
actually
go.
We've
started
to
use
Zen
hub,
so
it's
essentially
adds
a
layer
on
top
of
github
projects
or
like
github
issues
and
pull
requests.
A
This
is
what
our
board
looks
like
right
now.
You
can
actually
go
see
what
we're
prioritizing
you
can
see
how
we're
prioritizing
the
work
that
we're
doing.
You
can
actually
go
issues
that
you'll,
make
and
PRS
that
you'll
make
will
actually
land
in
this
board,
and
you
can
see
how
they
move
across
from
a
backlog
ticket
to
it
to
do
to
something.
That's
in
the
process,
interview
done
and
then
closed
off,
and
we're
really
excited
about
this
and
sort
of
sharing
this
with
the
community.
A
You
can
actually
see
how
we're
operating
day
to
day,
and
hopefully
you
know
it
becomes
a
nice
source
of
truth
for
us
being
that
just
radically
transparent,
with
the
work
that
we're
doing
awesome.
So
we
also
have
obviously
open
issues
and
PRS.
Now
issues
were
reopened
on
the
CLI,
which
was
really
nice,
a
nice.
We
have
this
concept
of
rfcs,
so
you
can
actually,
you
know,
request
a
feature
from
us
from
NPM
the
CLI,
the
registry.
A
If
you
go
to
our
github
org
and
at
the
very
top
we
have
a
project
called
RFC's,
you
can
actually
create
a
pull
request
and
ask
or
sort
of
outline
a
feature
that
you'd
like
to
see
us
implement
and
going
further.
We've
start
to
run
open.
Our
see
calls
bi-weekly
taking
sort
of
the
learnings
from
the
node
foundation
the
way
they
operate
and
open
Jas
foundation
and
running
bi-weekly
meetings
that
anybody
can
join.
We
stream
them
on
YouTube
and
you
can
actually
join
the
zoom
calls.
So
you
can
see
here's
some
lovely
faces.
A
You
can
go.
There's
archived
I
mean
I'm
in
the
middle
of
saying
something
here,
Royce
that
Royce,
you
look
pretty
disinterested,
but
yeah.
This
is
awesome.
So,
if
we're
creating
these
sort
of
artifacts
about
how
you
know
how
we're
operating
and
why
we're
the
we're
making
decisions
and
we're
also
hoping
that
you
know
you
will
come
collaborate
with
us-
have
discussions
with
us
and
you're
totally
enabled
to
come.
Do
that
where
we'd
be
excited?
A
So
as
well
as
we
have
Doc's,
that's
a
reference
to
our
old
Doc's.
I
may
or
may
not
have
a
link
for
you
to
use
to
go
check
out
our
net
new
Doc's.
You
can
go
to
preview,
Doc's,
dot,
MP,
MJS,
calm
and
you'll
actually
see
a
new
experience.
We're
currently
still
baking
this,
but
it
is
the
most
up-to-date
actual
source
of
truth
for
our
Doc's.
We're
gonna,
give
them
a
nice
little
rebrand
and
refresh,
which
is
awesome
and
we're
hoping
this
is
going
to
really
help.
A
We're
gonna
include
search
in
this
as
well
with
something
that
people
have
asked
for
years.
Like
hey,
can
I
search
the
docs
can
I
easily
like
navigate.
We
know
that's
been
tough,
we're
trying
to
fix
that.
So
if
you
get
a
preview
Doc's
time,
pmj
is
calm.
You
can
go
see
this
new
experience.
It's
awesome
cool.
We
also
actively
up
my
team
actively
works
very
closely
with
the
node
foundation,
where
we're
sitting
on
some
of
the
working
groups,
including
the
package
maintenance,
working
group
and
the
tooling
working
group.
A
So
if
you're
ever
like
looking
around
and
trying
to
see
what
we're
doing
in
the
open
source,
world
you'll
probably
find
us
in
those
calls.
So
what's
next
for
NPM
with
some
cool
stuff
that
I
can
share
with
you
so
coming
down
the
pipeline,
we
have
the
concept
of
multiple
finding
entries,
so
Jordan
Harvin,
who
actually
works
on
mbm
so
who
uses
MDM
here,
lots
of
folks
right.
It's
awesome
which
just
got
recently
pulled
into
the
open
Geospatial,
which
is
awesome,
yeah,
Joe,
so
yeah.
A
It's
awesome
and
he's
been
helping
us.
He
wants
to
see
essentially
that
idea
of
you
know
a
single
record
for
funding
turn
into.
You
know
multiple
records
that
can
be
utilized,
for,
let's
say
multiple
maintainer
Zoar,
let's
say
maybe
patreon
links
or
something
like
that
right.
There's
a
lot
of
opportunity
here
and
we're
currently
sort
of
sussing
out
the
RFC
for
it.
Npm
7
has
been
on
our
backlog
for
a
long
time,
we're
actively
working
on
it
and
we
have
queued
up
the
concept
of
workspaces,
which
we
know
people
have
told
us
for
forever.
A
A
We
are
hopefully
going
to
have
NPM
seven,
a
version
of
NPM
seven
staged
and
ready
to
be
consumed,
not
not
ready
to
be
released
fully,
but
in
early
q1
stage
publishes
and
scoped
auth
tokens
are
something
that
I'm
championing
internally
right
now,
so
try
to
sort
of
sophisticate
the
CI
publish
workflow
for
folks
and
if
you're
interested
in
this
feel
free
to
ping
me
afterwards.
There's
a
lot.
That's
going
into
this
there's
a
lot
of
discussion.
That's
going
into
this,
and
the
last
thing
here
is
package
exploration
and
package.
A
Shipping
I'm
sure
you've
always
wanted
this
right.
Why
has
this
never
been
a
thing
on
NPM
Jess,
calm
like
why
the
source
of
truth
from
packages
is
NPM.
Why
do
you
have
to
go
to
get
up
and
check
out
a
repo
which
may
or
may
not
be
the
same
thing
so
who
would
like
a
demo
of
some
cool
stuff?
Yeah
I
can't
hear
you
no
yeah,
okay,
sweet,
so
I'm
gonna
demo,
some
stuff
for
you
right
now
go
as
quickly
as
possible,
but
what
I'm
getting
demo
is
actually
live
right.
A
Now
we
pushed
yesterday-
and
there
were
some
folks
that
I'm
not
sure
if
they're
here,
no
Jason
Miller
from
Google
sort
of
undercut
me
quickly.
Oh
and
PS
I
was
like
I
knew.
You
would
want
to
see
a
demo.
So
I
was
like
nice
go,
so
he
quickly
found
this
and
I'm
sure.
If
you've
already
been
to
the
website,
you
may
have
seen
it
already.
We've
been
making
some
edits,
I'm
pmj
Escom
we've
been
making
some
improvements,
first
of
which
is
some.
You
know
CSS
love,
which
will
continue
to
happen.
A
A
Can
anybody
figure
out
which
one's
new
explore
right?
Cool
cool
you're
like
Darcy,
come
on?
Oh
low
doesn't
work,
okay
actually
am
I
logged
in
so
we
have
a
and
I'm
gonna
start
to
show
you
what
row
you're
giving
me
a
hard
time.
Oh
yeah,
okay,
I
react
so
two
things
to
know
actually,
so
this
is
perfect
sample.
Thank
goodness.
I
went
to
this
first
and
I
told
JD
D.
If
he's
in
the
audience,
which
is
not
that
would
go
low
first.
A
This
is
very
limited
beta.
We
haven't
fully
baked
this
there's
lots
of
features
that
we're
gonna
be
rolling
out
soon,
but
this
is
definitely
something
that
we've
heard
everybody
wants.
If
you
go
to,
let's
say
react:
you
can
actually
go
around.
This
is
limited
availability
as
well,
so
your
user
count
has
to
be
a
paid
teams
to
get
access
to
this
today,
although
we'll
be
rolling
out
to
everybody
in
the
in
the
future,
good.
A
Know
it's
expanding
the
tarball.
This
is
the
source
of
truth,
which
is
also
why
you
might
see
this
nice
little
integrity
and
sha
some
value
at
the
bottom
here.
Just
to
let
you
know,
this
is
exactly
what
is
in
the
registry
and
you
can
click
around.
You
can
look
at.
You
know
your
files
and
you
can
be
like,
oh,
my
goodness,
lik.
This
is
crazy,
Facebook
and
some
really
crazy.
We're
gonna
look
at
some
licensing
your
stuff.
A
What's
really
interesting
is
oh,
you
get
like
versioning
for
free,
so
let's
go
to
like
an
old
version
of
this
package
611
and
we
go
back
to
the
explore
page.
Let's
look
at
the
package.json
look
at
this
I'm
on
611,
pretty
awesome,
you'll
notice
that
the
install
script
is
also
being
updated
so
that
it
actually
adds
the
specific
version
you're
looking
at.
So
you
can
copy
and
paste
that
and
quickly
install
that
specific
version.
A
A
You'll
know
some
other
other
through
the
sidebar.
Everybody
was
getting
tired
of
seeing
github
everywhere
on
your
package
page,
it's
like
they
owned
the
world
right,
like
yeah
up
get
up
cab.
It's
like
come
on
like
there's,
there's
my
names
in
there
somewhere
right,
Gabe,
comm,
slash,
Darcy,
Clark
right,
so
we
reopen
Andrea
expanded
the
URLs
for
for
repose
and
and
home
pages.
This
was
sort
of
a
pain
point
people
we're
not.
You
know
like
this,
didn't
look
very
good.
We
also
have
now
bubbled
up
the
unpacked
size
information
there.
A
We
know
that
there's
other
community
tools,
bundle,
phobia,
etc.
That
provide
also
this
sort
of
metadata
we're
we're
working
on.
You
know
giving
you
a
better
experience
online
here,
so
cool,
maybe
there's
a
better
yeah
I
know:
whoa
man
come
on
you
like
giving
away
the
yeah
we'll
show
you
one
more.
It
is
about
good
yeah.
This
this
one
has
like
is
like
super
deeply
nested
like
information
cool.
So
let's
go
to
a
packaged
page
that
has
defined
funding.
A
So
my
cool
little
sleepover
package
look
at
that
look
at
this
new
little
button
right
so
again,
very
similar.
You
know
github
sponsors
and
you
know
open
collective
there's,
a
million
different
ways
for
open-source
developers
now
to
try
to
make
money.
We
wanted
a
way,
a
mechanism
again
to
to
make
this
meaningful.
So
when
you
define
that
funding
fields,
we
now
will
add
this
button
to
your
package
page.
It
quickly
will,
as
you
would
guess,
when
I
click
it.
It's
gonna.
A
Take
me
to
that
that
link
right
and
yeah,
so
like
lots
of
cool
little
improvements
over
time.
We
imagine
this
to.
You
know,
expand
when
we
have
multiple
funding.
We're
gonna
have
some
new
capabilities
there
and
we
options
right
am
I
missing
anything
now.
Are
we
good?
They
were
good.
Are
you
sure
we're
good?
Well,
we
can
I,
don't
know.
Is
there
anything
else?
I
don't
know,
I,
don't
think
we're
think
we're
good.
So
that's
just
a
few
sorry.
A
So
we
do
have
run
kit.
So
if
you've
ever
liked
on
to
a
website
or
NPM
package,
page
sorry
have
you
seen
this
little
button.
You
click
on
it.
It
takes
you
to
run
kit
which
you
can
actually
start
to
play
with.
Let's
say
the
MPM
package
just
so
you
know
this
is
I,
do
have
code,
maybe
sitting
on
a
branch
for
having
this
embed
in
the
actual
website
itself,
so
that
may
be
coming
as
well.
So
if
I
say
sleep,
let's
say
pulling
this
guy
out,
I'm
gonna
say
sleep
for
two
hundred
two
seconds.
A
Then
it
will
consult
log.
Oh-
and
you
can
just
this-
this
library
sleep
over
essentially
is
using
Atomics,
wait
to
halt
the
execution
and
then
do
something.
So
this
is
actually
running
in
the
browser
so
yeah.
This
is
a
sandbox
in
repple
in
the
browser,
if
you've
never
seen
it
before
so
you.
This
is
on
every
package,
page,
so
kind
of
fun
to
be
like.
If
you
want
to
try
something
you
can
just
click
on
that
button.
Try
it
out
it's
pretty
awesome
cool,
so
I
think
that's
about
it.
I
think!
A
That's
all
I
got
for
ya.
There
may
or
may
not
be
an
extra
commander
here
or
there
that
you
can
run
to
see
some
cool
stuff
in
your
free
time.
If
you
happen
to
run
NPM
Xmas,
it
might
do
something
but
yeah
again
I'll,
be
here
actually
all
week.
The
collaborator
settlement
for
a
lot
of
node.js
folks
that
our
node.js
foundation
folks
are
getting
together
on
the
13th
14th,
where
we'll
be
discussing
sort
of
the
future
of
standard
spec
and
for
us
NPM,
so
feel
free
to
join
us
at
that.
You
can
follow
me.