New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"core" folder missing on NPM registry (not a Lerna issue) #1932
Comments
Yikes, that's a nasty surprise. Thanks for the heads up and opening the issue upstream! |
(I'll leave this open until we get some resolution on npm/npm-packlist#24) |
The upstream issue has been resolved with: npm/npm-packlist@9230bb8 -- It was also impacting NPM v6.8.0 This fix got released in |
this is to workaround an issue where core folders were not being published. this is due to lerna/lerna#1932
Had the same issue with NPM v6.8.0 ... but fortunately, I knew I had a version I could update to, so when I updated (ie: 'sudo npm install -g npm'), it installed v6.9.0 and the problem seems to have been resolved. It now includes my 'core' sub-directory. |
Update to lerna v3.13.1 and you will no longer encounter this problem when running |
DISCLAIMER: this is not a bug from Lerna but an issue arising from one of its dependency => npm-packlist
Expected Behavior
core
would lead to all non-blacklisted files to be included in the tarball sent onto NPM registryCurrent Behavior
core
has suddenly become blacklisted by default without noticePossible Solution
!core
or!/path/to/core
in.npmignore
at the root of your Lerna package to explicitly whitelist the now blacklisted folder back.Steps to Reproduce (for bugs)
core
anywhere in the tree with a file "path/to/core/index.js"path/to/core
and any of its content will be included in the tarball on publishpath/to/core
and any of its content will be missing from the tarball on publishThe text was updated successfully, but these errors were encountered: