-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Support jQuery versions 1.12 and 2.2 #12787
Conversation
👍 this just started causing me problems, too. Should we consider locking the version down in ember-cli bower.json blueprint ? If we don't do that 1.13.x of jQuery will cause this same problem. |
embers test suite needs to also run against this (and pass) before we will consider merge. |
Basically, update https://github.com/emberjs/ember.js/blob/master/bower.json#L8 to use 1.12 |
When running Error: Could not find module ember-dev/test-helper/index
http://localhost:13141/ember-template-compiler.js:58 in missingModule
http://localhost:13141/ember-template-compiler.js:80 in internalRequire
http://localhost:13141/ember-template-compiler.js:44 in requireModule
http://localhost:13141/tests/?skipPackage=container,ember-testing,ember-debug&dist=min&prod=true:135
Test failed: global failure
Failed assertion: Error: Could not find module ember-dev/test-helper/index
http://localhost:13141/ember-template-compiler.js:58
Took 8ms to run 1 tests. 0 passed, 1 failed.
Failed!
npm ERR! Test failed. See above for more details. |
But I'm getting the same error when running it with |
I am also getting that error when testing the Not really sure how to push forward on this one. |
They've just made a blog post about the new releases, maybe the changelogs helps someone in pin-pointing this issue? |
In my case I'm getting the following errors: Uncaught Error: Assertion Failed: Ember Views require jQuery between 1.7 and 2.1 As a temporary solution I did:
I hope this serves as a temporary remedy while we Ember's team provides a definitive solution. Thank you! |
Can I ask the hypothetical question of, "What if the assert is just removed?". Bower and NPM seem better suited to manage/resolve dependencies. People manually managing dependencies management will just have to read the documentation if there comes a time ember is not compatible with a new version of jquery. |
I would like to see one of these two things happen:
I would prefer to simply remove the assertion... |
👍 on removing the assertion, it seems like it's a bit of a hangover from before the ember-cli world, I believe in any case using ember outside of ember-cli when bower is controlling versions is an advanced usecase anyway so the assertion is less useful |
#12793 removes the assertion |
@thijsvdanker @rwjblue I just bumped to jQuery 1.12 and ran the Ember test suite locally without failures. |
☔ The latest upstream changes (presumably #12793) made this pull request unmergeable. Please resolve the merge conflicts. |
Pinning to 1.11.3 since Ember doesn't yet run under jQuery 1.12. See ember-cli/ember-cli#5317 and emberjs/ember.js#12787
…releases being tested
…releases being tested
I just pulled this project and was unable to get tests running. Applying the follow gets all tests passing. Upgrade ember-suave to 1.2.3 https://github.com/dockyard/ember-suave/issues/84 jQuery version pin emberjs/ember.js#12787
The Ember 1.13 test (default) crashed because of the jQuery 1.12 upgrade bug (emberjs/ember.js#12787) The beta and canary tests failed because I forgot to remove them from the travis config in commit ce1df21.
The 1.12.0 and 2.2.0 release of jQuery have been tagged a couple of hours ago.
The regex for checking jQuery versions for Ember Views didn't pass for 1.12.x or 2.2.x