jsdoc3/jsdoc — pull request #161 by Jakobo (2012-08-15 20:27:21+00:00)
Title: Loading JSDoc via npm URL results in missing node_modules directory

npm allows you to reference a package via it's URL and it will download it into node_modules. This allows you to use the devDependencies section of a package.json to load JSDoc into node based projects. Unfortunately, the `node_modules` directory gets ignored by npm when being imported. Attempts to run `./jsdoc -T` will fail saying `common/util` cannot be found.

This fix updates the folder from `node_modules` to `nodejs_modules`, and updates corresponding docs. It doesn't seem to have any adverse affects. The benefit, however, is being able to include the latest JSDoc from github as an npm dependency:

```json
{
"devDependencies": {
"JSDoc": "https://github.com/jsdoc3/jsdoc/tarball/master"
}
}
```

Tests ran:

1. re-ran ./jsdoc -T with new paths
2. re-ran full-form jar command with new paths copy/pasted from doc changes
3. imported as an NPM module and verified functionality (see: https://github.com/Jakobo/inject/commit/9046a28629c72f47d57a2cfbb09e3307dc8262a3 for an example of it in use)

I couldn't find any directory related sanity tests to augment with the change, so hopefully this is sufficient. I know there's a lot of value in keeping the `rhino_modules` and `node_modules` directories based on convention. I think the ability to use JSDoc via npm may outweigh the convention though.