Failed init with private packages
See original GitHub issueI’m unable to run npx sb init
on an existing codebase due to errors with private packages (GPM).
error An unexpected error occurred: "https://registry.npmjs.org/my-private-repo: Not found".
The same packages work fine for normal npm -i
or yarn
CLI dependency management.
Is there a known requirement / issue around this?
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Get an error during publishing Private Package - Stack Overflow
I have a folder plaza which I want to convert to private package under ... npm init --scope=@ocean; npm login (logged in my...
Read more >Creating and publishing private packages - npm Docs
To share your code with a limited set of users or teams, you can publish private user-scoped or organization-scoped packages to the npm...
Read more >Handling private packages - Composer
Private Packagist provides mirroring for packages' zip files which makes installs faster and independent from third party systems - e.g. you can deploy...
Read more >Working with private modules - Play with Go
This means it will try the Go module mirror run by Google and fall back to a direct connection if the proxy reports...
Read more >Go Modules Reference - The Go Programming Language
go mod graph: go mod init: go mod tidy: go mod vendor: go mod verify: go mod why ... For example, the module...
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 FreeTop 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
Top GitHub Comments
Apart from private packages, packages installed from the custom/org registry are also not installing as they are not found in the npm registry, this also breaks the
sb init
command.Error:
npm accept flag of
--registry
can we have same for this command?Several of our private repos work ok during
init
, two do not. The working dependencies comprise both packaged releases and just regular git repos. My best guess is some slight difference in permission settings… but if I can install normally (having setup my GPM token) then it should work. 🤷♂️