The following new files will not be part of your published package
See original GitHub issueDescription
I’m used to seeing ? The following new files are not already part of your published package:
… but today I got the following message
yarn run v1.22.10
$ np
? The following new files will not be part of your published package:
This didn’t make any sense, because the functionality of the listed file was indeed included in the published package.
Expected behavior
I expected to be told that The following new files are not already part of your published package
as I have always been told before
Environment
np - 7.5.0 Node.js - 14.15.1 npm - 7.5.4 Git - 2.9.3 OS - OSX 11.2.3
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:11 (2 by maintainers)
Top Results From Across the Web
npm publish isn't including all my files - Stack Overflow
The problem was I had a files array in package.json. If this is present, then only the specified files get published, and everything...
Read more >How to publish packages to npm (the way the industry does ...
It's simple to publish a package onto npm. There are two steps: Create your package. Publish the package. But publishing packages the way...
Read more >npm-publish - npm Docs
Description. Publishes a package to the registry so that it can be installed by name. By default npm will publish to the public...
Read more >Control What you Publish Inside your Npm Packages - Medium
If there is no .npmignore , npm will look for a .gitignore file. Certain files are always included ( package.json , …), ...
Read more >Publishing packages | Dart
Learn how to publish a Dart package to pub.dev. ... You can always upload new versions of your package, but old ones will...
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
It did include the file, so it does appear to be a false negative. @sindresorhus was asking for a repro though, so that link (to the exact sha) should provide it.
I just experienced the same issue in a private repository.
I think this message is inaccurate and left a comment on where it was added here: https://github.com/sindresorhus/np/pull/595/files#r637090752