You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a great little package. Just wondering why .npmignore is cleared out (with the exception of the temp directory) before running npm pack? This means that files that I want to keep out of the package (tsconfig, eslint, prettier & VS Code config files and TypeScript source files, for example) and therefore add to .npmignore get included. I'm sure there's a reason, but would be great if an existing .npmignore file (if it exists) could be updated, rather than replaced.
The text was updated successfully, but these errors were encountered:
Hi,
This is a great little package. Just wondering why .npmignore is cleared out (with the exception of the temp directory) before running
npm pack
? This means that files that I want to keep out of the package (tsconfig, eslint, prettier & VS Code config files and TypeScript source files, for example) and therefore add to .npmignore get included. I'm sure there's a reason, but would be great if an existing .npmignore file (if it exists) could be updated, rather than replaced.The text was updated successfully, but these errors were encountered: