I have a file that is generated by npm install command (using preinstall task). I don't want to add it in the git repository, nor in the NPM project.
Supposing the file name is foo.json, I added it in .gitignore file as foo.json.
Is this enough to avoid uploading it on NPM registry?
I know I can add .npmignore file that will surely ignore the file, but I won't add it if .gitignore already does this.
Best Answer
If a project has both an .npmignore and .gitignore file, npm will only use the .npmignore file.
From the documentation:
Use a
.npmignorefile to keep stuff out of your package. If there's no.npmignorefile, but there is a.gitignorefile, then npm will ignore the stuff matched by the.gitignorefile. If you want to include something that is excluded by your.gitignorefile, you can create an empty.npmignorefile to override it.
In simpler terms, npm prefers the .npmignore file, but it will fall back to the .gitignore file.
In many cases, both Git and npm can ignore the same files, so it makes sense to just use a .gitignore file.
If you need npm and Git to ignore different files, then you need to maintain separate .gitignore and .npmignore files.
More information on what to put in .npmignore files: Should I .npmignore my tests?
For anyone reading this trying to ignore a file/dir from git but wish to include it in npm publish and have tried using an empty .npmignore file with no luck. This works.
In your .gitignore file, add the file/dir you wish to exclude **/build for example and in your .npmignore file make sure you specify the same file/dir but with the ! prefix so for the build example you would include !**/build