►
From YouTube: Experience publishing NPM package using package docs
Description
Learnings and stumbling blocks from following the documentation
A
Everyone,
this
is
katie
product
designer
for
package
and
in
think,
big
recording.
I
saw
that
there
was
a
discussion
about
how
we
might
improve
the
docs
and
especially
for
new
people
onboarding.
We
have
a
fresh
set
of
eyes,
and
so
I
did
manage
to
publish
an
npm
package
to
my
test
project,
but
this
wasn't
a
super
smooth
process
for
me,
and
so
I
wanted
to
just
kind
of
talk
through
how
I
found
the
documentation
and
what
I
did
to
resolve
the
problems
and
and
to
do
this.
A
I've
also
rolled
back
a
few
commits
to
when
things
were
still
broken
and
obviously
not
all
of
this
feedback
will
be
relevant,
because
I
am
certainly
missing.
Some
of
the
background
and
domain
knowledge
that
perhaps
a
lot
of
people
who
are
reading
the
documentation
would
have,
and
but
you
only
get
a
fresh
set
of
eyes
once
so.
I
thought
I'd
make
this
video,
and
so
I
started
here
and-
and
I
did
need
to
install
node.js
and
was
able
to
do
that.
A
Maybe
if
you're
familiar
with
npm,
you
would
understand
the
scoped
naming,
but
this
was
all
very
overwhelming
and
also
having
to
do
this
in
the
command
line.
I
was
thinking
if
I've
made
a
mistake
or
something.
How
am
I
going
to
correct
it,
and
even
looking
at
this
project,
my
org
bar,
I
guess
that
bar
would
be
the
name
of
the
project
and
the
org
would
be
the
organization.
A
A
Video-
and
this
could
again
just
be
like
more
on
the
documentation
on
the
npm
side
of
how
to
create
a
package,
but
I
wouldn't
have
known
that
in
the
test
project
repo,
I
should
create
a
npm
rc
and
that
also
the
package.json
would
be
living
there.
The
package.json
that
I
generated
with
npm,
init
and
so
yeah
that
was
that
was
interesting
and
then
use
the
get
lab
endpoint
for
mkm
packages.
I
had
no
idea
what
this
meant.
A
I
don't
know
if
this
is
like
an
enterprise
versus
not
enterprise.
Edition
yeah,
like
I
assumed
that
I
would
be
project
level,
because
my
home
page
of
my
application
is
pro,
has
a
project
id
but
yeah.
I
wasn't
really
too
sure
what
to
do
with
this
information
and
then
moving
on
to
authentication,
and
so
I
had
seen
this
personal
access
token
workflow
done
before,
maybe
for
creating
a
pipeline,
or
something
like
that,
so
I
had
a
little
bit
of
context
for
it.
A
What
the
preference
is
yeah?
So
if
I
go
into
access
tokens,
one
thing
that
I
was
not
sure
is:
does
the
name
matter
like?
Can
I
kind
of
not
contain
certain
characters,
or
does
it
have
something
to
do
with
that?
Yeah
like
does
that
matter
at
all?
Is
there
any
formatting,
the
expiration
date
and
then
in
terms
of
their
scopes
or
permission
levels?
A
Read
registry
and
write
registry
seemed
like
the
obvious
choices,
but
I
just
didn't
want
something
to
go
wrong,
so
I
actually
selected
all
of
these
so
yeah,
oh
yeah.
It
says
here
with
the
scope
set
to
api,
so
I
just
didn't
read
that
carefully
enough,
but
all
of
them
did
work,
and
so
I
was
able
to
generate
that
token.
A
A
I
was
like
this
cannot
be
the
token
name,
because
that's
that
doesn't
look
like
a
token
to
me,
and
I
had
to
like
kind
of
in
a
new
tab,
look
at
some
documentation
about
what
gitlab
tokens
will
look
like,
and
then
I
saw
a
screenshot
of
something
where
it
was
above
and
I
was
able
to
find
it
that
way.
That
was
just
like
a
little
interesting
funny
stumbling
block,
and
then
this
is
where
things
I
think
like.
I
was
able
to
create
this
npm
rc
by
watching
that
youtube
video.
A
And
then
this
was
all
like
pretty
straightforward
project
id
was
easy
to
find
and
obvious
that
I
needed
to
do
something
and
then
npn
config
set-
and
this
was
the
same
thing
like
pretty
pretty
easy
to
know
and
what
I
needed
to
do.
And
so
in
terms
of
like
what
I
learned
from
the
youtube
video
is
that
I
also
needed
to
make
some
edits
in
the
package.json,
which
I
guess,
we've
done
through
mpm
init,
and
it
said
something
about
following
a
naming
convention.
A
But
maybe
it
would
have
been
helpful
to
kind
of
understand
which
of
these
fields
are
important
and
how
they
need
to
be
set
up
similar
to
this,
like,
as
in
maybe
yeah,
I'm
not
sure
like
an
example
or
something.
So
I
only
learned
this
from
the
youtube
video
that
I
need
to
set
the
name
because,
like
when
you're
doing
it
in
the
command
line,
it
says:
what
do
you
want?
A
The
name
of
your
package
to
be,
or
something
like
that,
and
I
wouldn't
have
known
about
this
so
yeah
that
was
interesting
and
and
then
what
else
needs
to
change?
Oh,
yes,
so
also,
this
was
like
not
coming
out
of
the
box.
This
line
here
and
I
learned
about
that
from
the
youtube
video.
I
don't
know
if
it's
somewhere
in
here,
oh
yeah,
maybe
this
is
it.
This
looks
no.
This
is
this
is
a
ci
job
token
yeah.
A
That
was
the
other
interesting
thing
is
that
this
is
all
reading
like
one
two
three
and
then
here's
this
authenticate
with
ci
job
token,
which
is,
I
guess,
another
kind
of
authentication
I
could
have
chosen
to
do
so
without
the
youtube
video.
I
wouldn't
have
known
this
and
then
so
I
basically
made
these
changes
and
I
did
npm
publish
and
it
failed.
I
can
show
that.
A
So
it's
gonna
fail
on
403
forbidden,
and
I
was
like
doing
things
like
taking
bits
of
this
url
and
trying
to
figure
out
which
one
of
them
gives
me
a
response
and
which
one
doesn't.
I
think
it
was
like
when
I
do
this.
I
get
yeah
packages
invalid,
but
then,
if
I
take
it
back
to
this,
this
will
be
empty
or
something
oh,
no
yeah.
This
has
a
package
in
it
now
because
I've
put
one
there
and
then
this
actually
oops
is
like
yeah
correct.
A
So
that
was
a
little
bit
confusing
like
when
you
google,
this
403
in
conjunction
with
npm.
It's
a
lot
of
things
like
if
you're
trying
to
put
publish
to
the
public
registry,
and
so
actually
how
I
did
end
up
solving
this
was
paying
a
bit
more
close
attention
to
that
youtube.
Video,
and
I
see
that
in
the
youtube
video
he
doesn't
do
npm
config
set
on
either
of
these
and
we're
going
to
take
away.
A
This
closing
quotation
and
the
other
thing
that
was
different
about
the
youtube
video
is
that
it
doesn't
actually
point
to
a
specific
project,
and
I
think
it's
like
this.
So
this
is
all
learnings
from
the
youtube
video,
not
the
not
the
documentation,
but
I
think
that-
and
this
is
now
correct-
oh
yeah-
and
then
this
needs
to
be
not
in
quotation
marks
and
this
needs
to
be
equals.
A
A
I
think
that
he
might
have
copied
this
directly
out
of
the
documentation,
but
you
can
see
that
that
it's
different
from
the
documentation
that
I
copied
in
for
whatever
reason
this
did
work
and
the
the
way
that
I
copied
it
out
of
the
npm
documentation
did
not
and
so
yeah
it
was.
It
was
interesting
yeah.