-
Notifications
You must be signed in to change notification settings - Fork 62
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
add .npmignore #35
add .npmignore #35
Conversation
Hey @CaryLandholt I really appreciate these PRs. This is something I've been meaning to do with the contrib plugins. I just want to check in with the rest of the team so hold off on these for now until we get a response on this issue: gruntjs/gruntjs.com#65 |
You bet - thanks! |
Alternatively, you could specify the files to install in package.json, files section. This way, you have one less file, and the same result. |
@XhmikosR Good idea, I think that is the way we are currently leaning. Just giving that issue a bit more time for other core devs to respond. |
@XhmikosR, are you suggesting to use the files array configuration inside the package.json file? |
Yeah, that's what I was suggesting. It is the inverse but the result is the same. |
@shama what was the ignore pattern that we agreed upon? was it to only include |
If @CaryLandholt wants to address it that would be great. Otherwise I'll write a script that does this for all the contrib tasks soon. See: gruntjs/gruntjs.com#65 (comment) |
Hey @CaryLandholt if you have time, could you updated this PR based on gruntjs/gruntjs.com#65 ? |
Seems inactive, closing. This should be addressed in the future script across all contrib plugins |
During npm publish, certain files and directories can be ignored from the package.
See https://npmjs.org/doc/developers.html#Keeping-files-out-of-your-package.
This reduces the package size.
Package consumers need only the minimum files necessary to execute the package functionality.
Keeping
Ignoring