npm ERR! 404 Not Found - cant install plugin

[jjohnlaw]

Hi,

This plugin could be useful for my project, unfortunately im getting:

npm ERR! 404 Not Found - GET https://registry.npmjs.org/@ambimax%2fsemantic-release-composer - Not found
npm ERR! 404
npm ERR! 404  '@ambimax/semantic-release-composer@*' is not in the npm registry.

Is there a config error in the repo or Is this plug-in not publicly available?

Cheers, Jamie

[tortuetorche]

Hi folks,

I figured out how to install this package!

Directly from the GitHub repository, just run:

npm install --save-dev github:ambimax/semantic-release-composer#v1.0.2

Or with the GitHub Packages registry, create a new Personal access token, go to https://github.com/settings/tokens/new

Fill the Note field: Download packages from GitHub Package Registry Select the Expiration date of this new Personal access token Select the repo and read:packages scopes fields Click on the Generate token button

Copy your new personal access token (you should also save it in a passwords manager)

Run this command:

npm login --scope=@ambimax --registry=https://npm.pkg.github.com

Enter your GitLab username Paste your new token as the password Enter your email address, like your-username@users.noreply.github.com

Finally you can install semantic-release-composer, like this:

npm install --save-dev @ambimax/semantic-release-composer

References:

• https://stackoverflow.com/questions/17509669/how-to-install-an-npm-package-from-github-directly/45156653#45156653
• https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#installing-a-package
• https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-npm-registry#authenticating-with-a-personal-access-token

@tschifftner Do you plan to publish this package on NPM?

Have a good day, Tortue Torche

[jzuleger]

Seems like the scope change. It works with

yarn add --dev @iwavesmedia/semantic-release-composer

or

npm install --save-dev @iwavesmedia/semantic-release-compose

[Jonnx]

the iwavesmedia version is still locked to 1.0.0 and the latest is 1.1.0 so maybe somebody forked it to make the install happen. you can also use the following syntax if you want to get around the github login:

"@ambimax/semantic-release-composer": "ambimax/semantic-release-composer",

of the following for a specific version:

"@ambimax/semantic-release-composer": "ambimax/semantic-release-composer#1.1.0",