Created
February 15, 2012 16:31
-
-
Save isaacs/1837112 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| /**package | |
| * { "name": "npm-test-single-file" | |
| * , "main": "index.js" | |
| * , "version": "1.2.3" | |
| * , "description":"No package.json in sight!" | |
| * , "dependencies": { "minimatch": "*" } | |
| * } | |
| **/ | |
| module.exports = "I'm just a lonely index, naked as the day I was born." |
Yeah makes sense. In fact currently I do this via post-install script which works fine but is kind of painful to have to specify both dependency and scripts per each package. Would be nice if npm had a plugin system for cases like this similar to lein plugins
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No, I dont' think it's a good idea for npm to be parsing out require() statements. Pulling out metadata is one thing, but what you'er suggesting is much more involved.
You can just list your dependencies in the metadata.