module-deps
module-deps copied to clipboard
walk the dependency graph to generate a stream of json output
As we cannot write `__dirname` to package.json, transforms which require directories must be given relative paths. package.json ``` json { "browserify": { "transform": [ ["transform1", {"dirname": "relative/path"} ] ] }...
Hello @substack. We use 2 transform (babel and yamlify). When we update to module-deps 4.0.5, browserify throw next error: ``` SyntaxError: Unexpected character '#' ``` This error in yaml file....
Utf8 encoding of large files, after compiled will be garbled in this way, garbled will disappear; is there some issues? var rs = fs.createReadStream(file,{ encoding:'utf8' });
noParse paths are not resolved to absolute paths as in browserify.
fixes #64 @substack Is this how you intended handling input streams to work?
Pass the collection of `paths` through to `resolve` to support environments with 'interesting' node module environments ala https://github.com/tkellen/js-liftoff/pull/44/files Patched up a minor bug in an error message whilst I was...
I encountered the problem in https://github.com/substack/node-browserify/issues/1260 I think there is something can be done in `module-deps` to fix that problem. But I am not sure if it's the right way....
*\* This is an experiment - don't merge! **
Hello @substack et al, I have a issue that I don't totally understand and a fix that I don't totally understand either :stuck_out_tongue:. Perhaps by explaining the issue and showing...
Since https://github.com/substack/node-browserify/commit/837515284ad65fa5e0f15d24191f61a487d947ab, the `noParse` option has been renamed to `noparse`. But module-deps [is still waiting for `noParse`](https://github.com/substack/module-deps/blob/master/index.js#L349) with the old name.