chore(deps): update all non-major dependencies #844
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
☁️ Nx Cloud ReportCI is running/has finished running commands for commit d2ea9e1. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
^17.3.9->^17.3.10^17.3.9->^17.3.10^4.17.7->^4.17.9^18.3.8->^18.3.10^4.3.1->^4.3.2v4.1.7->v4.2.0^9.11.0->^9.11.1^5.30.4->^5.30.6v4.1.0->v4.1.1^19.8.0->^19.8.2^3.2.6->^3.2.7^1.8.22->^1.9.1^4.0.2->^4.0.4^5.4.7->^5.4.8^3.5.8->^3.5.10^3.5.8->^3.5.10Release Notes
angular/angular-cli (@angular-devkit/build-angular)
v17.3.10Compare Source
@angular-devkit/build-angular
vitejs/vite-plugin-react (@vitejs/plugin-react)
v4.3.2Compare Source
Ignore directive sourcemap error #369
actions/checkout (actions/checkout)
v4.2.0Compare Source
eslint/eslint (eslint)
v9.11.1Compare Source
webpro-nl/knip (knip)
v5.30.6Compare Source
2a36139)4b314e2)84db245)2b550b0)8ed9314)ed4bad2)0784ca5)cf6c5fe)v5.30.5Compare Source
d4c5af9)1e64b6c)module.exports = require()to be re-exports (e2bdb95)e40f618)nrwl/nx-set-shas (nrwl/nx-set-shas)
v4.1.1Compare Source
nrwl/nx (nx)
v19.8.2Compare Source
19.8.2 (2024-09-26)
🚀 Features
🩹 Fixes
❤️ Thank You
v19.8.1Compare Source
19.8.1 (2024-09-25)
🚀 Features
🩹 Fixes
babel-plugin-transform-async-to-promisesfrom@nx/rollup(#27669)❤️ Thank You
sveltejs/prettier-plugin-svelte (prettier-plugin-svelte)
v3.2.7Compare Source
solidjs/solid (solid-js)
v1.9.0: - LGTM!Compare Source
This release like the last is focusing on small quality of life improvements and adjustments that will help us move towards 2.0. So while not the most exciting release to everyone it provides some really important features and fixes to some developers.
And unlike many previous releases the vast majority of the work and features came from PRs from the community. So really all I can say is Looks Good to Me!
Better JSX Validation
While still incomplete across templates we've added JSDOM to the compiler to better detect invalid HTML at build time by comparing what we expect the template to be with what a browser would output. This now includes things that are nested we didn't detect before like putting
<a>inside other<a>tags which will lead to the browser "correcting" it in less than intuitive ways.Improved Exports
While each environment in
solid-js/webhas its own methods to be used in the compiler. We are now exporting the client methods from the server to prevent weird import errors. Now these methods will throw if used in this environment but shouldn't break your build.Additionally we have seen some issues in bundlers that incorrectly feed our ESM exports back through the browser field. While this is a known issue they all pointed issues at each other and with no intention of fixing it. We have removed the browser field in this release, meaning some legacy packages may have issues resolving browser if they don't support export conditions.
This is regretful but this blocked deployments on several platforms and since this was the only fix at our disposal after two years of attempting to push this issue to the bundlers to no avail, we've moved forward with it.
Custom Element improvements
We have a few improvements to our custom element support in this release. First off we now detect elements with the
isattribute as custom elements which means all the special behavior is afforded to them.We've also improved our event handler delegating retargetting to better handle shadow DOM events. There were cases where we skipped over part of the tree.
Finally we've added the
bool:attribute namespace to handle explicitly setting certain attributes according to boolean attribute rules. While this isn't necessary for built-in booleans currently we handle most attributes as properties and we lacked a specific override. But now we have it:Support for handleEvent Syntax in Non-Delegated Events
A little known thing is that events actually also support objects instead of functions (See: https://developer.mozilla.org/en-US/docs/Web/API/EventTarget/addEventListener)
We(thanks @titoBouzout) realized we can use this mechanism as a way to set advanced rules like
passiveorcaptureon this object as way to handle all current and future event attributes that browsers might add. This way we don't need specific mechanisms likeoncapture:(which is now deprecated).Instead using
on:you can set the event properties you wish.Other Updates
We've fixed an issue with lazy images. Apparently, cloneNode doesn't handle them properly so we've updated our heuristic to treat templates with lazy images to be handled with
importNode.We've improved our Hydration Mismatch Error to output the template of that it can't find the matching ID for. This should make it easier to track down where the hydration errors are occurring. There have been several hydration improvements over the later 1.8 releases so upgrading will likely improve the situation for those who have been facing issues.
Finally, we've improved some of the types in the JSX and Signal Setter in this release.
Big thanks to those who contributed to this release: @wkelly17, @olivercoad, @titoBouzout, @trusktr, @Huliiiiii. And thanks to all of you who gave feedback on the Metadata/Head Tag RFC. While it didn't make it in this time around you've definitely given us stuff to consider for its future design.
Best,
@ryansolid
v1.8.23Compare Source
sveltejs/language-tools (svelte-check)
v4.0.4Compare Source
v4.0.3Compare Source
Componentin type positions. Instead you need to prepend it withtypeof. Here's how you do it:let x: Component. After:let x: ReturnType<typeof Component>let x: typeof Component. Afterlet x: typeof Component(no change)vitejs/vite (vite)
v5.4.8Compare Source
Please refer to CHANGELOG.md for details.
vuejs/core (vue)
v3.5.10Compare Source
Bug Fixes
v3.5.9Compare Source
Bug Fixes
Configuration
📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.