I'm trying to package my node module with npm. My project has a sub-directory named "build/", and I've found that running "npm install" on my project will install all the files in the project to node_modules, except for the "build/" subdirectory. It therefore seems that "build/" is getting filtered by default. It's not clear from the documentation whether this is expected behavior, and whether it is possible to override it.
I have the same problem. Is there a way around it?
I can't see in the code where this is filtered. Any information about this @isaacs ?
I have had this problem too. I think it's in one of npm's dependencies.
Make sure none of the following ignore files include 'build' (or other things you don't want ignored):
npm config get userignorefile
npm config get globalignorefile
git config --global --get core.excludesfile
@jbeard4 did you solve this issue? My guess is that build is in your project's .gitignore file, failing that, can you please check the locations in @mfncooper's response above?
I am trying to construct a failing test for this issue in email@example.com and can't reproduce this behavior.
Here's what I have so far:
mkdir one two
touch a.js build/b.js
npm i ../one
When I run this, I find that the contents of one/build have been installed under two/node_modules, and the file build/b.js does exist.