Using the paths option, doesn't lookup anymore on node_modules about browser-resolve HOT 4 CLOSED

Please create a failing example against this module. Looks like your
example is using browserify, unless that is just bad naming of variables.
On May 16, 2014 9:38 AM, "Sébastien Lorber" [email protected]
wrote:

The doc says:

paths - require.paths array to use if nothing is found on the normal node_modules recursive walk

Actually, I have a configuration where the following works:

return browserify({
        entries: ['./src/js/app.js'],
        extensions: ['.jsx'],
        paths: ['./node_modules','./src/js/home']
    })

While the following doesn't:

return browserify({
        entries: ['./src/js/app.js'],
        extensions: ['.jsx'],
        paths: ['./src/js/home']
    })

So, I guess when using the paths option, the code doesn't try anymore to
lookup into the node modules, while the doc says it should

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/41
.

from browser-resolve.

@defunctzombie sure I'll show you soon. I'm building a starter kit for Gulp / Browserify / React / Less / Phonegap actually and will open source it in some hours

from browser-resolve.

Actually I believe that my PR in #43 fixes this.

from browser-resolve.

cool

from browser-resolve.