Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different behavior of watchify and browserify #314

Open
sueess opened this issue Mar 22, 2016 · 1 comment
Open

Different behavior of watchify and browserify #314

sueess opened this issue Mar 22, 2016 · 1 comment

Comments

@sueess
Copy link

sueess commented Mar 22, 2016

Is watchify not just a wrapper of browserify?

The two listed browserifyFunction don't handle the source the same. For example the "watchified"-function finds my imports and the non "watchified" not. Why these differences?

// Method one: Without watchify
browserifyFunction = browserify(browserifyOptions);

// Method two: With watchify
var options = assign(watchify.args, browserifyOptions);
browserifyFunction = watchify(browserify(options));
@sueess
Copy link
Author

sueess commented Apr 8, 2016

Watchify ignores the options of tsify, while browserify alone does not? Any ideas?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant