Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Unable to npm pack scoped package
See original GitHub issueType of Issue
[x] Bug Report
[ ] Feature Request
Description
Running ng-packagr then npm pack in dist folder fails if the package.json name is scoped:
"name": "@foo/bar"
The npm pack generates this error message:
404 Not Found: @foo/bar@latest
Tried npm pack @foo/bar but same result.
How To Reproduce
See descriptions
Expected Behaviour
Running npm pack works with scoped package name.
Version Information
"ng-packagr": "^1.5.0-rc.1",
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
[BUG] npm pack fails for scoped package from private registry ...
If the package has been previously installed, clean the cache: npm cache clean --force. Run the pack command: npm pack @myregistry/some-package.
Read more >Unable to publish scoped NPM package on internal Artifactory
i am trying to publish a simple (there is only a js file inside) scoped NPM package on my company's Artifactory.
Read more >Creating and publishing an organization scoped package
On the command line, navigate to the package directory. Run npm publish . Private packages will say private below the package name on...
Read more >npm packages in the Package Registry - GitLab Docs
If you plan to install a package through the instance level, then you must name your package with a scope. Scoped packages begin...
Read more >npm Registry - JFrog - JFrog Documentation
If Artifactory is running behind a reverse proxy, make sure to disable URL decoding on the proxy itself in order to work with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Indeed that is the issue as seen here. Rolling back to npm 5.3 should fix the problem.
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
This action has been performed automatically by a bot.