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.
how to ignore private packages?
See original GitHub issuebuilding off of #15
can you provide an arg or some sort of publish config option to ignore private packages in the changelog? The suggest fix here will not work for our repo.
I’d like some sort of option or config to do this and ignore our private root packages from our CHANGELOG. It does not seem that command.bootstrap.ignore from lerna.json is an option either.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:6 (2 by maintainers)
Top Results From Across the Web
npmrc ignored private package - node.js - Stack Overflow
Another way is to create group endpoint in the private instance which will point hosted + proxy to public packages and update your...
Read more >About private packages - npm Docs
User-scoped private packages can only be accessed by you and collaborators to whom you have granted read or read/write access. For more information,...
Read more >How to ignore files from your npm package | Zell Liew
First, npm will check your repository for a .gitignore file. If there is a .gitignore file, npm will ignore files according to what's...
Read more >Handling private packages - Composer
You can find more information about how to set up your own package archive on Packagist.com. Satis#. Satis on the other hand is...
Read more >Configuration options | Yarn - Package Manager
Note that you can now also disable scripts on a per-package basis thanks to dependenciesMeta . ... Path to file containing private key...
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
Lerna(v3.21.0) does not publishes the private packages if we use
--no-privateflag in publish command.Reference: https://github.com/lerna/lerna/tree/master/commands/version#--no-private
However that also makes it not bump the package versions of published packages in the private packages, which will remove semlinks and thus break the entire repo if the version no longer matches.
i.e., in private package A, referencing ^5.0.0, with a public package bump of B to 6.0.0 - this will BREAK the monorepo. There is no scenario where this is not a bug since lerna is managing the packages of both private and public packages.