Greg Reimer

Browserify doesn't use $NODE_PATH to resolve transforms

3

This: ``` bash NODE_PATH=/some/path browserify -t foo main.js > bundle.js ``` ...fails when `foo` is resolved at `/some/path`. Also created a related PR here: https://github.com/substack/module-deps/pull/120 regarding cases where dependencies' transforms...

Only merge own properties

1

The for ... in loop in this module should only copy a property if `item.hasOwnProperty(key)`, otherwise it will copy prototype properties, resulting in unexpected and hard-to-find bugs.

Doing: ``` js mdeps({ paths: ['/some/path'] }) ``` ...fails to resolve transforms under `/some/path`, and also ignores `$NODE_PATH`. This PR includes a unit test and a fix.

I may not understand what it's supposed to do, or maybe it's a bug, but I can't seem to get them to position correctly. If I change the math a...

Stack traces weren't appearing in my logs, that's why I noticed this.

Feature request: Easy way to iterate every path in a pathSet

3

Maybe this is just due to my own peculiar habits for implementing route handlers, or maybe this would be useful to everyone. I'll let you be the judge of that!...

Ability for includePath to ignore the path above the project root

1

`includePath` tests against the full path to the filesystem root. For example: ``` 'filename-rules/match': [1, { pattern: 'kebab-case', includePath: true, }], ``` Gets evaluated against: ``` /Users/foo/Documents/projects/widgets/src/table-widget.ts ``` ...which fails....

Phase transition idea.

3

Idea: add a "phaseless" feature which would allow you to do: ``` js proxy.intercept({ // same options, except "phase" is now optional }, function*(request, response) { // if you omitted...

Intercept req/resp bodies as streams.

1

This would allow people to manipulate source streams directly, as in: ``` js proxy.intercept({ phase: 'response', as: 'stream' }, function(req, res) { resp.stream = resp.stream.pipe(myTransformStream); }); ```