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

Inner require conflicts with browserify #42

Open
gobwas opened this issue Apr 23, 2014 · 5 comments
Open

Inner require conflicts with browserify #42

gobwas opened this issue Apr 23, 2014 · 5 comments

Comments

@gobwas
Copy link

gobwas commented Apr 23, 2014

When bundling my code with move.js included, browserify tries parse inner require method. Any way how can I avoid it? Renaming locally inner require to _require does help.

Thanks.

@yields
Copy link
Contributor

yields commented Apr 23, 2014

i think that's a bug in browserify ? not sure.

@ben-eb
Copy link

ben-eb commented Dec 9, 2014

Yup, same issue. I would love a move.js build that was compatible with a browserify pipeline. Are there any plans for one?

@d-oliveros
Copy link

Same issue here. Trying to make it work with browserify-shim, but those requires are breaking it.

@yields
Copy link
Contributor

yields commented Mar 6, 2015

does this fix it?

browserify --noparse move.js main.js > bundle.js

@axelpale
Copy link
Collaborator

axelpale commented May 4, 2015

This browserify issue is strongly related to the package.json issue. Fortunately I'm on a verge of solving it for good. A pull request appearing in a couple of hours!

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

5 participants