Bump @astrojs/solid-js from 3.0.1 to 4.1.0

[dependabot]

Bumps @astrojs/solid-js from 3.0.1 to 4.1.0.

Release notes

Sourced from @​astrojs/solid-js's releases.

@​astrojs/solid-js@​4.1.0

Minor Changes

• #10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @​ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

  This change is in line with Astro's Node.js support policy.

Changelog

Sourced from @​astrojs/solid-js's changelog.

4.1.0

Minor Changes

• #10689 683d51a5eecafbbfbfed3910a3f1fbf0b3531b99 Thanks @​ematipico! - Deprecate support for versions of Node.js older than v18.17.1 for Node.js 18, older than v20.0.3 for Node.js 20, and the complete Node.js v19 release line.

  This change is in line with Astro's Node.js support policy.

4.0.1

Patch Changes

• #9355 2e4d110a876efc4ddcdeda403259317d1cbb742d Thanks @​marvin-j97! - Upgrades vite-plugin-solid to ^2.8.0

4.0.0

Major Changes

• #6791 37021044dd4382a9b214f89b7c221bf1c93f3e7d Thanks @​patdx! - Render SolidJS components using renderToStringAsync.

  This changes the renderer of SolidJS components from renderToString to renderToStringAsync. It also injects the actual SolidJS hydration script generated by generateHydrationScript, so that Suspense, ErrorBoundary and similar components can be hydrated correctly.

  The server render phase will now wait for Suspense boundaries to resolve instead of always rendering the Suspense fallback.

  If you use the APIs createResource or lazy, their functionalities will now be executed on the server side, not just the client side.

  This increases the flexibility of the SolidJS integration. Server-side components can now safely fetch remote data, call async Astro server functions like getImage() or load other components dynamically. Even server-only components that do not hydrate in the browser will benefit.

  It is very unlikely that a server-only component would have used the Suspense feature until now, so this should not be a breaking change for server-only components.

  This could be a breaking change for components that meet the following conditions:

  • The component uses Suspense APIs like Suspense, lazy or createResource, and
  • The component is mounted using a hydrating directive:
    • client:load
    • client:idle
    • client:visible
    • client:media

  These components will now first try to resolve the Suspense boundaries on the server side instead of the client side.

  If you do not want Suspense boundaries to be resolved on the server (for example, if you are using createResource to do an HTTP fetch that relies on a browser-side cookie), you may consider:

  • changing the template directive to client:only to skip server side rendering completely
  • use APIs like isServer or onMount() to detect server mode and render a server fallback without using Suspense.

3.0.3

Patch Changes

... (truncated)

Commits

• 66bc104 [ci] release (#10739)
• 683d51a feat: upgrade the minimum Node.js maintainance LTS version (#10689)
• 2dd00a0 chore: import sort source code, exception for the astro package (#10242)
• 75084b4 [ci] release (#9609)
• 2e4d110 [solidjs integration] Update solidjs dependency (#9355)
• e862d07 [ci] release (#9580)
• 825ba1a [ci] format
• 3702104 Render async SolidJS components (#6791)
• 98fa8f0 [ci] release (#9491)
• 36bedf1 [ci] format
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[netlify]

✅ Deploy Preview for comforting-toffee-89c331 ready!

Name	Link
🔨 Latest commit	61eedd4
🔍 Latest deploy log	https://app.netlify.com/sites/comforting-toffee-89c331/deploys/661d226e00ae000008bb1224
😎 Deploy Preview	https://deploy-preview-11--comforting-toffee-89c331.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.

[dependabot]

Superseded by #13.