We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Check that the files declared in the package.json are actually there before publishing.
package.json
Files specified in the [main]?, types, and exports fields in the package.json should be checked for before pushing to npm.
main
types
exports
Is the feature request related to a problem?
Both p-queue@^7.3.1 and p-queue@^7.3.2 don't contain compiled code because the build script didn't generate them and np didn't catch it.
p-queue@^7.3.1
p-queue@^7.3.2
np
Run the check directly after the lifecycle scripts and directly before pushing to npm.
Manually checking is error-prone
The text was updated successfully, but these errors were encountered:
Related: #82.
Sorry, something went wrong.
No branches or pull requests
Check that the files declared in the
package.json
are actually there before publishing.Description
Files specified in the [
main
]?,types
, andexports
fields in thepackage.json
should be checked for before pushing to npm.Is the feature request related to a problem?
Both
p-queue@^7.3.1
andp-queue@^7.3.2
don't contain compiled code because the build script didn't generate them andnp
didn't catch it.Possible implementation
Run the check directly after the lifecycle scripts and directly before pushing to npm.
Alternatives
Manually checking is error-prone
The text was updated successfully, but these errors were encountered: