We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If we use the loader.noConflict method from the loader.js, with the following aliases,
loader.noConflict
loader.noConflict({ require: 'myRequire' })
the app fails with an error
Uncaught TypeError: Cannot read property 'entries' of undefined at new ModuleRegistry (vendor.js:formatted:68415)
because there is no global require object, we only have myRequire now
require
myRequire
Related to ember-cli/loader.js#139
The text was updated successfully, but these errors were encountered:
Definitely possible to fix, would love a PR.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
If we use the
loader.noConflict
method from the loader.js, with the following aliases,the app fails with an error
because there is no global
require
object, we only havemyRequire
nowRelated to ember-cli/loader.js#139
The text was updated successfully, but these errors were encountered: