[js] Update stimulus-use 0.50.0-2 → 0.50.0 (patch) #2246
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ stimulus-use (0.50.0-2 → 0.50.0) · Repo
Release Notes
0.50.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
v0.50.0
Native Stimulus 3 Support (#170)
Delete Circle CI config
docs: add gahia as a contributor for bug, code (#202)
Fix isElementInViewport (#178)
docs: add craisp as a contributor for bug, code (#200)
Test Treeshake-ability in GitHub Action (#152)
Use GitHub Action for JavaScript Tests (#199)
Bump Cypress E2E actiont to `ubuntu-latest`
Bump follow-redirects from 1.13.2 to 1.14.8 (#187)
Bump karma from 6.1.0 to 6.3.16 (#190)
Bump minimist from 1.2.5 to 1.2.6 (#192)
Bump postcss from 8.2.10 to 8.2.13 (#195)
Bump log4js from 6.3.0 to 6.4.6 (#198)
Bump node-fetch from 2.6.1 to 2.6.7 (#197)
Bump async from 2.6.3 to 2.6.4 (#196)
Bump url-parse from 1.5.3 to 1.5.10 (#189)
Bump engine.io from 4.1.1 to 4.1.2 (#182)
clears timeout on unobserve (#185)
Fixed typo in README (#175)
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands