-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Backbone no longer works w/ Ender (Backbone.$ not set when exports is defined) #3031
Comments
Yep, this was brought up in a few other tickets (see the end of #2997). The solution is to do: Backbone.$ = $; wherever Backbone is first referenced. |
Yeah, I actually tried that. The trouble is, due to the way Ender modules are created, there's no way to add that reference without losing the ability to integrate
I've managed to work around this by just not integrating At the very least, the |
@symmetriq Would you like to send in a patch that fixes the Ender loading problem? Is such a patch possible? |
@jashkenas Done: #3038 |
closing in favor of #3038. |
I use Backbone as a module in some of my Ender-built libraries. As of Backbone 1.1.1, the
Backbone.$
reference is now undefined instead of pointing at the global$
. I assume there's a valid reason to omit$
in some situations, but in this case it prevents Backbone from working as an Ender module.Because
exports
always exists when modules are part of an Ender library,$
doesn't get passed tofactory
:This is where we really need to end up, but it's now unreachable in the context of an Ender library:
The text was updated successfully, but these errors were encountered: