►
From YouTube: npmCamp 2016 - Lightning Talk - State of the CLI: npm@3, stability, feature ... ~ by Kat Marchan
Description
Lightning Talk - State of the CLI: npm@3, stability, feature work, and beyond~ by Kat Marchan
A
Sorry,
I
can't
do
that
from
over.
Here
anyway,
you
can
grab
my
talk.
You
can
npm
install
my
talk.
Of
course
you
can
also
reach
me
at
twitter.
That's
my
twitter
handle,
so
this
is
gonna,
be
a
kind
of
a
brief
overview
over
these
points,
I'm
going
to
talk
about
npm
at
3:00
and
where
that's
at
right
now,
I'm
going
to
talk
about
the
stabilizing
work
that
we're
doing
and
kind
of
what
that
means.
I
guess
also
sustaining
work.
A
Got
me
talking
about
the
state
of
triage
that
forest
talks
about
all
the
time
and
me
by
extension,
and
then
some
product
related
work
that
weíre
also
doing
on
the
CLI,
because
you
know
there's
actual
features
on
it
and
we're
actually
attached
to
a
company
so
npm
at
three.
It's
a
year
old.
Now,
we've
had
this
thing
out
for
a
year.
It
is,
it
is
very.
It
is
very
nice
and
stable.
Now
like
we,
we
have
pretty
high
confidence
in
the
quality
and
the
reliability
of
the
installs
that
it
does
now.
A
It
is
shipping
by
default
and
node
six,
which
is
going
to
become
its
LPS
in
October
and
NPM.
To
still
around,
please
don't
use
it,
but
it's
still
around
if
you
really
really
need
to-
and
it's
gonna
be
in
no
in
Note
4,
for
as
long
as
that
LTS
lasts
and
I
I,
don't
know
what's
happening
with
the
rest
of
the
LTS
stuff
so,
but
for
now,
Note
4
will
have
an
NPM
to
please
upgrade
and
if
you
really
really
need
convincing
for
updating.
Oh,
this
is
playing.
A
How
do
I
play
this
video
there
we
go.
This
is
what
the
progress
bar
it
looks
like
now.
It's
changed
a
lot
since
the
Ergo
and
it's
actually
really
really
sweet.
So
if
you
want
this
progress
bar,
you
want
to
update
on
PM
and
if
you
want
to
use
it
for
your
own
project,
there's
a
er
Rebecca
pass
yarn
a
slash
gauge
on
on
github,
it's
just
gauge
on
github,
and
you
can
get
one
of
these
things
for
yourself
and
customize
it
for
your
project.
A
So
speaking
of
bodies,
what
we're
doing
right
now
at
the
NPM
CLI
team
is
focusing
on
sustaining
work.
That
is
the
main
focus
so
for
those
of
you,
unfamiliar
with
the
term
sustaining
word,
they're,
sustaining
work
and
expanding
work
and
kind
of
sustaining
work.
Is
we
have
this
thing?
We
have
this.
This
thing
that
we
we
have,
and
we
kind
of
want
to
make
it
be
not
terrible,
so
we're
just
going
to
make
sure
that
this
asset
is
right.
Now
works
really
well.
That
means
we're
gonna
fix
bugs
that
wings.
A
We're
gonna
work
on
the
test
suite.
That
means
we're
going
to
you
know,
address
those
big
issues
that
we
keep
getting
thrown
our
way.
It
also
means
that
we've
not
only
have
we
stabilized
the
test,
suite
we're
working
on
getting
CI
working,
also
windows.
We
had
a
big
push
earlier
this
year
to
get
the
test
suite
passing
on
Windows
and
fixed
at
a
number
of
window
specific
bugs
in
the
process.
So
we
have
a
lot
more
confidence
in
how
well
the
NPM
CLI
works
on
Windows.
A
A
We
won't
support
it.
You
won't
we're
not
gonna
help
you
with
it
not
yet,
but
what
we
won't.
We
won't
help
you
with
those
buttons
I'm.
Sorry
I'm,
not
sorry,
so
that
also
involves
a
lot
of
shrink-wrap
fixes.
Shrink-Wrap
is
kind
of
an
ongoing
thing
for
us
like
we're,
trying
to
make
sure
that
it
works
really
well
a
siddhis
right
now
there
are.
A
A
Some
of
you
might
know
that
we
were
doing
a
weekly,
really
a
weekly
release
cycle,
where
we
would
delay
a
release
by
a
week
and
then
so
on
and
so
forth,
but
we
would
have
a
release
every
week.
That's
now
moved
to
a
monthly
release
cycle,
so
we
have
more
time
to
you
know,
do
our
work
instead
of
doing
our
releases.
A
A
A
We
have
like
a
couple
people
helping
us
on
the
tracker,
there's
no
way
that
we
can
ever
manage
that,
like,
realistically
speaking,
most
of
those
are
also
like
just
support
issues,
so
we're
trying
really
hard
and
spending
a
lot
of
time
to
try
and
keep
that
number
under
control
and
that
number
it's
about
us
under
control.
Hence
we
think
we
can
do
it
really.
A
So
we
triage
every
damn
day
we
go
through
a
few
requests.
You
might
see
that
there's
a
lot
of
feature
requests.
We
go.
We
have
a
meeting
every
single
day
to
go
through
them.
We
discuss
them,
we
consider
them.
We
take
them
very
seriously.
We
look
at
the
underlying
needs
that
these
things
are
talking
about
to
us.
We
we
do
not
like
throwaway
feature
requests,
even
if
it
might
seem
like
if
it
ever
seems
that
way.
I'm
really!
Let's,
let's
talk
about
that,
but
we
do
closed
a
lot
of
them.
A
We
have
to
close
a
lot
of
them.
We
cannot
spend
too
much
time
on
them,
because
we
have
a
lot
of
other
ones
to
look
at
that's
kind
of
how
triage
works
right.
You
have
you're
trying
to
figure
out
what
is
going
to
get
you
the
most
bang
for
your
buck
as
far
as
survival
goes
in
a
very
depressing
way,
so
it
means
the
big
bucks
take
a
much
higher
priority
off
our
time.
A
A
Finally,
I
want
to
talk
a
little
bit
about
product,
so
we,
you
know
the
CEO.
Our
team
is
basically
the
open-source
arm
of
the
NPM
Inc
right.
So
we
are.
We
are
the
ones
that
are
really
facing
this,
like
big,
open
source
community,
we're
the
thing
that
people
install
like
everything
that
we
do
is
open
source.
So.
A
Either
way
we
are
still
part
of
NPM
Inc
and
we
are
trying
to
support.
We
are.
We
are
not
trying.
We
are
actually
supporting
their
efforts,
but
our
efforts
to
do
product
work.
What
is
product
basically
things
that
will
make
the
company
money
and
then
eventually
or
we
directly
benefit
the
open-source
community.
A
So
what
is
that
we
have
an
effort
to
do
analytics
that
Rebecca
is
leading
I.
Don't
have
the
issue
number
for
that,
if
you're
interested
in
looking
at
analytics
that
I'm
p.m.
and
how
how
NPM
opted-in
is?
So
it's
often
just
before
anyone
like
jumps
down
my
neck
about
this
we're
going
to
send
analytics
data,
so
we
can
start
collecting
more
information
about
what
our
users
need
and
that'll
help
us
a
lot.
It'll
be
opt-in
for
people
who
want
to
cooperate
with
us
and
there
is-
and
it's
all
gonna
be
open
source
work.
A
So
if
you
want
to
help
with
that
in
any
way,
there
is
an
issue.
Some
people
I
think
someone
already
took
it
up
to
help
implement
it.
For
us,
which
is
fantastic,
we
also
have
new
login
features
coming
up,
meaning
like
the
whole
login
thing
is
getting
revamped
a
little.
That
means
you're
gonna
get
single
sign-on,
that's
like,
oh,
so
you
can
once
it's
implemented
at
first,
it's
going
to
be
for,
like
NPM
Enterprise,
once
that's
stable
there,
and
we
know
what
we
need
and
we
know
that
it
works.
A
We're
gonna,
take
that
and
we're
going
to
turn
it
into,
for
example,
github
based
like
it
login,
so
you
can
actually
link
up
your
github
account
with
your
NPM
account.
Instead
of
signing
up
separately,
two-factor
authentication
for
publishing,
which
is
really
cool.
That
is
something
that
might
also
come
with
that
effort
like
it.
This
is
all
touching
the
authentication
and
and
log
inside
of
NPM.
So
look
forward
to
that
and
we're
looking
at
other
things
in
the
future.
A
For
example,
front-end
we're
looking
at
how
to
support
front
and
better
that's
an
ongoing
conversation
and
that's
pretty
much.
My
talk,
forest
and
I
are
here
and
our
intern
Emma.
If
you'll
raise
your
hands,
y'all
can
come
up
and
talk
to
us
anytime
during
the
conference.
We
are
literally
here
to
talk
to
y'all,
so
please
come
approach,
us
Rebecca,
what's
gonna
be
here,
but
Rebecca
can't
today,
so
it's
just
gonna
be
the
three
of
us
and
of
course
anytime
on
Twitter
feel
free
to
ping
us.
Thank
you.