s/vendor/node_modules/g

[isaacs]

Then you can get rid of this:

require.paths.unshift(require('path').join(__dirname, '..', 'vendor'));

[indexzero]

@isaacs Do you know how to ignore only some of the folders in the node_modules folder?

[isaacs]

Not sure what you mean. You want to bundle your deps? Use the bundleDependencies list in package.json. Check out how npm does it with its own internal dependencies.

[indexzero]

@isaacs This is a git issue. For example in most of my projects I put the following in the git ignore:

npm-debug.log
node_modules

I could update the git ignore to only explicitly ignore those modules in the package.json and vendor the others, but I was hoping there might be a less verbose option

[isaacs]

Why not just remove that .gitignore, and vendor in node_modules?

rm -rf node_modules #clean start
npm install
find node_modules -name .gitignore | xargs rm
git add node_modules
git rm -rf vendor
echo npm-debug.log > .gitignore
git add .gitignore
git ci -m "vendor in node_modules ftw"

[Marak]

@isaacs - I seem to have memories of getting fail when attempting to vendor things in the node_modules folder.

Knowing that vendoring into node_modules is a good idea, I will experiment again.

[dominictarr]

the point is also to not save everything you have installed with npm in git.

what if node also treated a second folder (i.e. vendor) just like node_modules?

@indexzero I think you can have a line like !node_modules/foo in the .gitignore and it will not ignore it.

[isaacs]

Or, you could just install all your deps with npm, list them in your
package.json file as dependencies, keep ignoring node_modules in git,
and add all your dependencies to the bundleDependencies list. npm help json

On Thu, Aug 11, 2011 at 16:38, dominictarr
reply@reply.github.com
wrote:

the point is also to not save everything you have installed with npm in git.

what if node also treated a second folder (i.e. vendor) just like node_modules?

@indexzero I think you can have a line like !node_modules/foo in the .gitignore and it will not ignore it.

Reply to this email directly or view it on GitHub:
https://github.com/nodejitsu/http-server/issues/3#issuecomment-1787028

[Marak]

@isaacs - So like, the reason that static is vendored is because it's from a custom fork we made which doesn't have a github repo or npm package.

[isaacs]

Ok. You can still give it a package.json and put it in node_modules and bundle it. or you can do require("./vendor/static") to include it.

Modifying require.paths is a bad idea. It's brittle, makes your programs less intelligible to newcomers, and will throw in node 0.5 and higher.

[jfhbrook]

So like, the reason that static is vendored is because it's from a custom fork we made which doesn't have a github repo or npm package.

Why is this so? Is this something we can change?

[dominictarr]

fixed is nodejitsu@1c5e147

@jesusabdullah, basically the problem that that cloudhead is not maintaining his projects.

[isaacs]

@dominictarr Awesome! Welcome to future of node!

[dominictarr]

cheers!
for future reference, the most difficult change is

#.gitignore
node_modules

to

#.gitignore
node_modules/*
!node_modules/$BUNDLED_DEP 

! means to not ignore this line.
see git help ignore