-
Notifications
You must be signed in to change notification settings - Fork 8
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
An in-range update of can-view-callbacks is breaking the build 🚨 #325
Comments
After pinning to 4.3.3 your tests are passing again. Downgrade this dependency 📌. |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for using unique tag names to prevent conflicts with other testsCommitsThe new version differs by 6 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 15 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 Release Notes for Adding support for initializing a custom element using a SymbolCommitsThe new version differs by 19 commits.
There are 19 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 25 commits.
There are 25 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 37 commits.
There are 37 commits in total. See the full diff |
The dependency can-view-callbacks was updated from
4.3.3
to4.3.4
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
can-view-callbacks is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
Release Notes for Automount performance fix for browsers without customElements
This uses domMutate.onInsertion instead of standalone MutationObserver in order to ensure that each element's tagHandler is called only once in environments that do not support customElements. This was causing large performance issues in these browsers.
#109
Commits
The new version differs by 4 commits.
75bd39d
4.3.4
51ee1f7
Merge pull request #109 from canjs/no-mutation-observer
db8c123
adding test to ensure each element is only mounted once by MutationObserver
070d30e
using domMutate.onInsertion instead of standalone MutationObserver
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 🌴
The text was updated successfully, but these errors were encountered: