-
Notifications
You must be signed in to change notification settings - Fork 684
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
Comments
i think that's a bug in browserify ? not sure. |
Yup, same issue. I would love a move.js build that was compatible with a browserify pipeline. Are there any plans for one? |
Same issue here. Trying to make it work with browserify-shim, but those requires are breaking it. |
does this fix it? browserify --noparse move.js main.js > bundle.js |
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! |
When bundling my code with move.js included, browserify tries parse inner
require
method. Any way how can I avoid it? Renaming locally innerrequire
to_require
does help.Thanks.
The text was updated successfully, but these errors were encountered: