netlify[bot]
commented
4 months ago Deploy Preview for cn-devtools-app ready!
| Name | Link |
|---|---|
| Latest commit | 7602f9fa3376a8324b3bafdee85633998c6246e9 |
| Latest deploy log | https://app.netlify.com/sites/cn-devtools-app/deploys/66b59e28a11b100008cb1d88 |
| Deploy Preview | https://deploy-preview-324--cn-devtools-app.netlify.app |
| Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
This PR contains the following updates:
1.8.19->1.9.3Release Notes
solidjs/solid (solid-js)
### [`v1.9.3`](https://redirect.github.com/solidjs/solid/compare/v1.9.2...v1.9.3) [Compare Source](https://redirect.github.com/solidjs/solid/compare/v1.9.2...v1.9.3) ### [`v1.9.2`](https://redirect.github.com/solidjs/solid/compare/v1.9.0...v1.9.2) ### [`v1.9.0`](https://redirect.github.com/solidjs/solid/releases/tag/v1.9.0): - LGTM! [Compare Source](https://redirect.github.com/solidjs/solid/compare/v1.8.23...v1.9.0) 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 `` inside other `` tags which will lead to the browser "correcting" it in less than intuitive ways. #### Improved Exports While each environment in `solid-js/web` has 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 `is` attribute 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: ```jsConfiguration
📅 Schedule: Branch creation - " 1 " (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.