►
From YouTube: NPM Setup discussion
Description
The team discusses ideas for making the setup and integration of NPM easier.
B
A
It's
more
about
the
pipeline,
so
the
two
elements
of
the
demonstration
that
stated,
which
I
again
I
thought
was
great
I'm,
not
even
trying
to
cause
it
because
drama
here
with
the
presentation
or
anything,
but
it
was.
It
was
more
around
the
idea
of
like
okay,
so
I
need
to
set
up
my
NPM,
oh
I,
see
I
think
we
could
have
a
template
for
that
which
I
think
we've
been
working
on
like
okay
I
mean
because
we
have
templates
for
read,
me--don't,
MD
and
a
couple
of
other
things
in
projects.
A
You
know
you
turn
on
your
package.
It'd
be
really
you
package,
the
core
to
be
really
cool.
To
be
like
add
my
NPM
I
see
for
my
whatever
right.
Maybe
then
I
have
to
go
in
and
that's
where
the
template
comes
from,
and
maybe
it's
a
project
template,
because
we
had
support
the
project
templates
right
now
already,
but
I
was
talking
more
in
terms
of
just
the
pipeline
auto-updating
side
of
that
that
demonstration.
A
C
B
C
Okay,
cool-
and
it
was
just
echoing
it
out
so
basically
was
just
creating
the
file
right,
so
I
do
similar
things
if
I'm
publishing
to
GCP
or
something
or
app
engine
and
I
need
to
create
a
EML
file.
Some
sort
just
went
in
or
what
Daniel
was
talking
and
got
my
wheels
turning
that
can
be
super
cool
to
just
with
environment
those
CI
variables
like
having
box
there,
and
it's
like
I'll
put
this
to
your
in
PMRC
I.
Don't
Daniel,
I,
don't
know!
If
that's
what
you
were
referring
to
as
well.
Sorry,
you.
A
A
For
example,
even
source-
you
know
in
my
in
my
bash
RC
right
I
can
source
external
files
in
my
bash
I
see
yeah.
Does
that
might
be
a
I,
don't
know
because
that'd
be
kind
of
cool
right,
because
then
you
just
create
the
separate
and
the
NPM
configuration
stuff
which
is
pretty
static
right.
You
source
the
external
file.
I,
don't
know
if
that's
possible,
it
just
occurs
to
me.
Cuz
reason
is
auto
populated
just
because
they
might
have
other
stuff
in
there.
Yeah.
B
A
B
D
You
want
to
just
pull
the
NPM
I
stay
up,
but
you
just
had
stayed
and
so,
like
I,
think
the
thing
about
this
is
also
there's
so
many
ways
you
could
kind
of
go
about.
This
like
I,
would
think
at
a
place
where
you're
doing
purely
private
repositories
and
whatnot,
it's
very
likely.
They
might
just
push
this
MP
MRC
with
the
tokens
into
the
repo
or
some
other
places.
D
They
might
push
the
NP
MRC
with
an
environment
variable
instead
of
the
token,
and
then
you
know,
any
oncoming
developers
would
get
given
that
variable
when
they're
setting
up
locally
and
then
within
the
CI.
We
could
have
something
that
grabs
this
file
and
populates
that
single
value,
rather
than
generating
the
whole
file.
D
There's
there's
a
lot
of
different
paths
that
you
could
take
with
this
type
of
configuration,
but
I
do
agree
that,
like
if
I'm
a
new
JavaScript
developer
and
have
no
idea
what
I'm
doing
it
would
be
really
cool
to
just
be
able
to
like
say,
I
want
to
make
a
package
out
of
my
app
and
then
click
a
button,
and
it
will
just
auto
do
this
for
me
because
I
don't
really
necessarily
know
what
that
is
yet
or
how
to
do
it.
Can
you
can
you
click
on
the
get
lab
CI
demo?
Please?
Yes,.
A
So
if,
if
the
NPI
MRC
exists,
then
do
a
thing
well,
I
know
it
doesn't
exist.
I'm,
sorry,
there's
that
exclamation
mark
in
there
there's
a
couple
of
edge
cases
here
right
if
I
have
an
NPM
IC
set
up
already,
because
I
have
some
other
registry
or,
if
I'm,
adding
a
new
root,
because
I
had
multiple
routes
that
I'm
referring
to
already
because
that's
possible.
A
So
I'm
not
like
trying
to
say
we've
done
a
bad
job
or
whatever,
but
and
there's
just
a
couple
of
edge
cases
here,
where
it's
like
I,
wonder
how
we
still
work
around
this,
because
I
can
see
as
people
start
adopting
this
methodology,
they
could
end
up
with
some
some
sort
of
like
overlapping
of
stuff,
but
I
think
for
the
most
part,
when
I'm
looking
what
the
general
concept
of
what
I'm
calling
out
and
you
can
stop
sharing
your
screen.
If
you
want
stiva,
then
I
think
everyone's
seen
it
I
did.
A
The
general
idea
of
what
I'm
calling
out
is
that
there's
anytime,
we
copy
and
paste
a
thing.
It's
just
something
that
jumps
in
my
head
really
quick
is
to
say:
if
we're
just
copying
and
pasting
do
I
need
a
human
to
do
this,
and
the
answer
is
generally
known
right.
It's
the
same
with
any
coding
problem.
If
you're
copying
and
pasting
the
computer
can
do
that,
you
doesn't
need
your
help
to
do
it.
A
A
Sorry,
but
again,
I
know
we've
kind
of
dug
into
this
a
little
deep
and
I
don't
want
to
like
carry
on
too
much
about
it,
but
that's
the
idea.
The
concept
here
is
to
sort
of
how
do
we
iterate
on
this
to
turn
it
into
a
process
that
really
just
supports
what
people
are
doing
run
them?
They
can
jump
through
hoops
and
stuff,
and
this
is
a
wonderful
stuff.
I
don't
mean
to
trivialize
the
effort,
that's
gone
into
this
cuz
I
know
it's.
There.
You've
worked
on
a
lot.
I
know.
D
Has
there
been
any
talk
of
like
integration
of
the
like
package
CI
into
auto
develops,
because
certainly
all
of
these
problems
would
have
to
get
solved
in
order
to
have
that
just
be
like
a
flip,
the
switch
and
then
it
figures
out.
You
know
this
is
a
maven
package.
Let's
just
build
it.
This
is
a
NPM
package.
Let's
just
build
it,
I
don't
know
if
that
discussion
has
come
up
anywhere.
Yet
we.
E
A
A
Yeah
I
think
the
strategy
be
to
look
to
to
sort
of
similar
processes
that
we
use
for
other
parts
of
that
pipeline
and
when
we
say
we
want
to
you
know
we
set
up
order
DevOps.
What
is
order?
Devops
mean
what
part
of
that
is
automatic,
and
how
does
that?
How
can
we
look
at
that
model
as
a
way
to
sort
of
work
where,
as
a
goal
to
work
towards
by
how
we're
building
our
NPM,
maven,
Coenen,
etc,
etc,
and
packages?
Right
again,
it's
all
copy
and
paste?
A
It
may
be
a
prereq
for
having
that
work
is
we
have
to
have
set
the
very
environment
variables,
as
you
demonstrated
Steve,
with,
with
the
OAuth
token
and
with
the
personal
access
token.
Obviously
those
things
might
change,
because
I
think
we're
going
to
combine
the
two
here
at
some
point.
But
you
know
maybe
that's
a
requite
stick,
that's
fine.
We
can
have
required
steps
that
people
have
to
do,
but
then
everything
else
is
just
a
copy
and
paste
anyway
project
ID.
We
know
what
it
is.
You
know
the
root.
A
We
know
what
it
is,
although
with
your
change
of
allowing
differently.
Maybe
that's
different,
but
maybe
just
to
say
you
standard
root
is
the
name
of
the
actual
group
or
the
pack,
the
repo
it's
in
or
whatever
it
is,
and
then
you
can
customize
it
if
you
want,
but
again
just
sort
of
thinking.
In
those
terms.