Closed retrofox closed 10 years ago
FYI, I can't tell from the readme change what this does. I'm no browserify expert either though. What's a built-in?
Cool, Thanks :+1:
Thanks very much. @deepak1556 can you add a tag and then publish to npm ? I forgot add it
Done!
thanks !!!!!
@deepak1556 please can you publish it ? It still is 0.4.6 https://www.npmjs.org/package/gulp-browserify
i did publish it as v0.5.0, weird!
:-(
is there a way to check my publish history in npm-cli for a package?
@retrofox its there nw :)
thanks again !!!
On 7 March 2014 18:45, Robo notifications@github.com wrote:
@retrofox https://github.com/retrofox its there nw :)
Reply to this email directly or view it on GitHubhttps://github.com/deepak1556/gulp-browserify/pull/63#issuecomment-37071148 .
retrofox.com.ar
What's the use case of this? Builtins that are not used won't be bundled anyway.
@shuhei i imagine a use case where an alternative for a builtin is to be used for ex: component/events. @retrofox could explain a better use case.
@shuhei i imagine a use case where an alternative for a builtin is to be used for ex: component/events
That's exactly our use-case. Thanks for the merge @deepak1556!
:+1:
@shuhei i imagine a use case where an alternative for a builtin is to be used for ex: component/events
That's exactly our use-case. Thanks for the merge @deepak1556!
Do you mean you want require('events')
to return component/events
? If so, does this work?
var extend = require('util')._extend;
var builtins = require('browserify/lib/builtins');
var componentEventsPath = require.resolve('component-events');
opts.builtins = extend(extend({}, builtins), { events: componentEventsPath });
Add a way to ignore builtins from options object.