►
From YouTube: Follow-up to speed-run on fetching packages from npmjs.org when not available in GitLab
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
Oh
hello,
this
recording
is
intended
to
serve
as
a
follow-up
to
a
speedrun
I
recorded
the
other
day,
demonstrating
how
to
fetch
packages
from
NPM
public
repository.
When
the
package
is
not
found
in
the
get
lab.
Npm
registry
I
showed
off
how
the
functionality
working
using
a
CI
job
that
was
pulling
that
attempted
to
pull
an
item
from
my
git
lab
package
registry
and
when
it
did
not
succeed
in
doing
that,
it
pulled
it
from
NPM
public
registry.
A
What
I
didn't
show
in
that
video,
which
I
think
is
an
important
step,
is
to
show
how
to
disable
this
feature.
If
you
don't
want,
don't
actually
want
this
to
work.
So
it's
important
to
note
that
this
feature
is
enabled
and
disabled
at
the
instance
level.
So
that
means
forget
lab
comm.
This
is
enabled
for
everybody.
A
A
To
settings
into
the
CI
CD
section-
and
this
is
a
new
settings
area-
that
we
were,
that
we
are
adding
in
12.9,
and
this
will
include
configuration
items
for
the
package
registry
as
we
move
forward
for
now.
It's
really
where
you
would,
where
you
would
disable
the
forwarding
of
NPM
package,
requests
to
the
NPM
public
registry
to
disable
it
you
simply
unselect
it
and
then
click
Save
Changes
and,
of
course
you
can
re-enable
it
and
save
changes
as
well.
A
Okay,
well,
I,
just
wanted
to
share
that
video
again.
This
feature
comes
out
in
milestone,
twelve
point:
nine,
which
is
just
ten
days
away
on
March
22nd,
and
it's
actually
available
right
now
on
get
lab
comm.
So
if
you
have
any
feedback
on
the
issue,
you
could
follow
along
in
the
actual
issue
or
you
could
reach
out
to
me
at
T
or
Z
at
get
babcom
thanks
again.