fix(deps): update dependency solid-js to v1.9.4

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
solid-js (source)	1.8.17 -> 1.9.4

---

Release Notes

solidjs/solid (solid-js)

v1.9.4

Compare Source

v1.9.3

Compare Source

v1.9.2

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/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:

<my-element bool:enable={isEnabled()}></my-element>

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 passive or capture on this object as way to handle all current and future event attributes that browsers might add. This way we don't need specific mechanisms like oncapture: (which is now deprecated).

Instead using on: you can set the event properties you wish.

<>
  <div on:click={{
    handleEvent(e) {
      console.log("clicked", e)
    },
    once:true
  }/>
  <div on:wheel={{
    handleEvent(e) {
      e.preventDefault() // only works on not passive events
      e.stopPropagation()  
      console.log("wheel stopped?")
    },
    passive: false
  }} />
</>

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.23

Compare Source

v1.8.22

Compare Source

v1.8.21

Compare Source

v1.8.20

Compare Source

v1.8.19

Compare Source

v1.8.18

Compare Source

---

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
package-lock.json	28% smaller

[snyk-io]

🎉 Snyk checks have passed. No issues have been found so far.

✅ security/snyk check is complete. No issues have been found. (View Details)

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: solid-quickstart@undefined
npm WARN Found: @solidjs/[email protected]
npm WARN node_modules/@solidjs/router
npm WARN   @solidjs/router@"^0.15.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @solidjs/router@"^0.8.2" from [email protected]
npm WARN node_modules/solid-start
npm WARN   peer solid-start@"*" from [email protected]
npm WARN   node_modules/solid-start-netlify
npm WARN   1 more (the root project)
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: solid-quickstart@undefined
npm WARN Found: @solidjs/[email protected]
npm WARN node_modules/@solidjs/router
npm WARN   @solidjs/router@"^0.15.0" from the root project
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer @solidjs/router@"^0.8.2" from [email protected]
npm WARN node_modules/solid-start
npm WARN   peer solid-start@"*" from [email protected]
npm WARN   node_modules/solid-start-netlify
npm WARN   1 more (the root project)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/vite
npm ERR!   peer vite@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0" from [email protected]
npm ERR!   node_modules/vite-plugin-solid
npm ERR!     vite-plugin-solid@"^2.7.0" from [email protected]
npm ERR!     node_modules/solid-start
npm ERR!       peer solid-start@"*" from [email protected]
npm ERR!       node_modules/solid-start-netlify
npm ERR!         peerOptional solid-start-netlify@"*" from [email protected]
npm ERR!         1 more (the root project)
npm ERR!       1 more (the root project)
npm ERR!   peerOptional vite@"^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0" from [email protected]
npm ERR!   node_modules/vitefu
npm ERR!     vitefu@"^1.0.4" from [email protected]
npm ERR!     node_modules/vite-plugin-solid
npm ERR!       vite-plugin-solid@"^2.7.0" from [email protected]
npm ERR!       node_modules/solid-start
npm ERR!         peer solid-start@"*" from [email protected]
npm ERR!         node_modules/solid-start-netlify
npm ERR!         1 more (the root project)
npm ERR!   1 more (the root project)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vite@"^4.4.6" from [email protected]
npm ERR! node_modules/solid-start
npm ERR!   peer solid-start@"*" from [email protected]
npm ERR!   node_modules/solid-start-netlify
npm ERR!     peerOptional solid-start-netlify@"*" from [email protected]
npm ERR!     1 more (the root project)
npm ERR!   solid-start@"^0.3.11" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/vite
npm ERR!   peer vite@"^4.4.6" from [email protected]
npm ERR!   node_modules/solid-start
npm ERR!     peer solid-start@"*" from [email protected]
npm ERR!     node_modules/solid-start-netlify
npm ERR!       peerOptional solid-start-netlify@"*" from [email protected]
npm ERR!       1 more (the root project)
npm ERR!     solid-start@"^0.3.11" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2025-02-20T18_32_17_821Z-debug-0.log