-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update jsdom to the latest version 🚀 #10
base: master
Are you sure you want to change the base?
Conversation
Version 12.0.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 30 commits.
There are 30 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 13 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 10 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 11 commits.
See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 35 commits.
There are 35 commits in total. See the full diff |
Update to this version instead 🚀 CommitsThe new version differs by 25 commits.
|
Update to this version instead 🚀 CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
|
|
|
|
|
|
|
|
|
|
Version 11.12.0 of jsdom was just published.
The version 11.12.0 is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of jsdom.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Commits
The new version differs by 22 commits.
4d26c67
Version 11.12.0
d6688e5
Implement Element.prototype.closest()
9191218
Upgrade NWSAPI to v2.0.7
500a209
Change storageQuota to operate on code units, not bytes
23d67eb
Add the storageQuota option
b4db242
Remove unused form-data-symbols.js file
70fd739
Fix a few entries in the changelog
eae1062
Upgrades cssstyle dependency to ^1.0.0
022c204
Update hosts in Travis configuration
2761d3c
HashChangeEvent and PopStateEvent should no longer bubble
f1270e7
Roll Web Platform Tests
d6f8a97
Enable Blob-slice.html test in Node.js v10
3afbc0f
Implement Web storage - localStorage, sessionStorage, StorageEvent
7b4db76
Handle Node.js v6 timeout in execution-timing tests
a5a7785
Run failing tests to confirm their status
There are 22 commits in total.
See the full diff
FAQ and help
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper bot 🌴