-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Problem with requireJS and latest build? #1249
Comments
Seems like they changed the name from |
ping @jmeas @jasonLaster |
Where is this change? |
Actually, it seems to be correct. My idea is that your Backbone updated too? |
@Anachron I am using Backbone version "1.1.2". I'll try adding a fake entry now and see if it resolves the issue. |
No joy, unfortunately. Seems the same problem exists with the AMD version:
|
Hey, I mean you should add |
I can't see that anything has changed in the factory fn between the two versions, which is where I would think the problem would be. |
@jmeas Weird. I just tried installing v1.7 and the same problem persists. It was working literally yesterday, so this leads me to believe perhaps there is something wrong with my grunt file or with almond. Are you able to replicate at all? @Anachron You mean like this?
|
@jptaylor yes like that, does it work? |
@Anachron No unfortunately. I mean I'm not even sure what it is doing since it is still exporting to "Backbone". |
@jptaylor sounds like it might be something about your project. Maybe look through the commit history and see if anything stands out? |
Using latest is a bit hairy. This could be a contributing factor: marionettejs/backbone.babysitter#44 |
@rhubarbselleven Interesting, because the source maps are pointing to babysitter as the culprit. Is there anything I can do to test this logic? I created a completely barebones marionette + require project from scratch last night and the problem persists so @jmeas I'm starting to wonder if this is confined to my project. |
https://www.npmjs.org/package/backbone.babysitter hopefully resolved with 0.1.2 let me know @jptaylor |
This is due to Backbone's 1.1.1 release and their AMD implementation (http://backbonejs.org/#changelog). My immediate workaround is to specify the version of bower to be used in
Howto fix this forever. Well not sure yet. @davidsulc suggests using I'm tempted to request limiting Marionette's upper backbone limit to v1.1.0 until there's some more clarity around this. |
ah thanks for the awesome research @rhubarbselleven |
Yup - a combination of things but that does seem to be the root of the problem. At least I know what I'm up against now. Thanks all. |
so...Backbone doesn't work with require js right now because their UMD is mezzed up? |
It must work, the release has been out in the wild for 3 months. There must be something else here. |
@rhubarbselleven @jmeas @samccone Im using backbone 1.1.2 and the |
Which requirejs version are you using @ahumphreys87 ? And are you using almond? |
@rhubarbselleven Im on 2.1.11. Yeah I use almond - is this not working for you? |
Was this ever solved? I'm getting the same issue after I updated to backbone 1.1.2 |
@spchuang, what version of Marionette are you using? And are you using RequireJS? Are you using wrapShim? |
@jmeas, wrapShim:true actually fixed the problem |
I upgraded Marionette to version 1.8.3 and am no longer able to build use r.js/grunt-requirejs. I've replicated by doing the following:
bower.json
Gruntfile.js
main.js (config file)
Running the above returns with: Uncaught ReferenceError: Backbone is not defined
The problem goes away if I remove the Marionette import, and also if I downgrade to version 1.7.
The text was updated successfully, but these errors were encountered: