[Problems with npm private installation]

2 hours ago, GreenSock said:

Welcome aboard, @Savvytech!

 

Sorry to hear about the trouble. I'm not familiar with that at all, but perhaps @Prasanna has some wisdom to share. 

 

Thanks! 

 

1 hour ago, Prasanna said:

@Savvytech this issue seems to be a bug in the npm cli. NPM had fixed this bug earlier but it seems like the issue has reappeared in the latest update.

 

There are bugs raised previously (ref: https://github.com/npm/cli/issues/1703#issuecomment-774684656) and it's mainly due to package name aliases. So, if you want to get rid of this issue then the simplest solution would be to not use package name alias.

 

Here's how to use gsap package without package name alias:

Installation:
$ npm install @gsap/member

 

Usage:

 

import GSAP from '@gsap/member'

 

I hope this helps

 

Thanks! Seems to be working now.

[Problems with npm private installation]

Hi,

 

Currently signed up as a greensock free member(trying out before subscribing for paid plans)

 

After installing via npm private registry,npm outdated no longer works properly.

 

It keeps throwing this error Error: Only tag, version, and range are supported

 

Any advise?

 

[NPM Private Registry 403 Error]

On 5/13/2021 at 11:11 AM, BrianCross said:

Hi everyone, I'm getting the following error while trying to install from the private registry:

$ npm install gsap@npm:@gsap/shockingly

npm ERR! code E403
npm ERR! 403 403 Forbidden - GET https://npm.greensock.com/gsap - bad authorization header. Please login again
npm ERR! 403 In most cases, you or one of your dependencies are requesting
npm ERR! 403 a package version that is forbidden by your security policy, or
npm ERR! 403 on a server you do not have access to.

This is a Next JS project that I'm starting. I just worked on another Next JS project and had no issues installing from the private registry. I've searched a few threads and all suggested solutions result in the same error. I've double checked the authorization token and I actually copied the .npmrc file and .env.local that contains the actual token from the previous project.

 

Hi @BrianCross , do u mind sharing on how to configure the token in .env and also reference them from .npmrc? What i tried doesn't seems to work.