Bump @astrojs/solid-js from 3.0.1 to 4.0.1

[dependabot]

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

Release notes

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

astro@3.6.5

Patch Changes

• #10287 a90d685d7 Thanks @​ematipico! - Fixes an issue where in Node SSR, the image endpoint could be used maliciously to reveal unintended information about the underlying system.

  Thanks to Google Security Team for reporting this issue.

@​astrojs/sitemap@​3.1.1

Patch Changes

• #10179 6343f6a438d790fa16a0dd268f4a51def4fa0f33 Thanks @​ematipico! - Revert withastro/astro#9846

  The feature to customize the file name of the sitemap was reverted due to some internal issues with one of the dependencies. With an non-deterministic behaviour, the sitemap file was sometime emitted with incorrect syntax.

• #9975 ec7d2ebbd96b8c2dfdadaf076bbf7953007536ed Thanks @​moose96! - Fixes URL generation for routes that rest parameters and start with /

@​astrojs/preact@​3.1.1

Patch Changes

• #10200 c692d0c66a5062937e47402dc700d41c2a5dfc5c Thanks @​Princesseuh! - Fixes passing children to server-rendered components causing an error

@​astrojs/sitemap@​3.1.0

Minor Changes

• #9846 9b78c992750cdb99c40a89a00ea2a0d1c00877d7 Thanks @​ktym4a! - Adds a new configuration option prefix that allows you to change the default sitemap-*.xml file name.

  By default, running astro build creates both sitemap-index.xml and sitemap-0.xml in your output directory.

  To change the names of these files (e.g. to astrosite-index.xml and astrosite-0.xml), set the prefix option in your sitemap integration configuration:

  import { defineConfig } from 'astro/config';
  import sitemap from '@astrojs/sitemap';
  export default defineConfig({
    site: 'https://example.com',
    integrations: [
      sitemap({
        prefix: 'astrosite-',
      }),
    ],
  });
  

  This option is useful when Google Search Console is unable to fetch your default sitemap files, but can read renamed files.

@​astrojs/react@​3.1.0

Minor Changes

• #10136 9cd84bd19b92fb43ae48809f575ee12ebd43ea8f Thanks @​matthewp! - Changes the default behavior of transition:persist to update the props of persisted islands upon navigation. Also adds a new view transitions option transition:persist-props (default: false) to prevent props from updating as needed.

  Islands which have the transition:persist property to keep their state when using the <ViewTransitions /> router will now have their props updated upon navigation. This is useful in cases where the component relies on page-specific props, such as the current page title, which should update upon navigation.

... (truncated)

Changelog

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

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

• #9482 72b26daf694b213918f02d0fcbf90ab5b7ebc31f Thanks @​natemoo-re! - Improves compatability with the Qwik adapter

• #9479 1baf0b0d3cbd0564954c2366a7278794fad6726e Thanks @​sarah11918! - Updates README

3.0.2

Patch Changes

... (truncated)

Commits

• 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
• 1baf0b0 [docs] minimal integration READMEs (#9479)
• 60dc8da [ci] format
• 72b26da Skip check for known Qwik components (#9482)
• 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	5297468
🔍 Latest deploy log	https://app.netlify.com/sites/comforting-toffee-89c331/deploys/660174c6ccb4d6000844c6d0
😎 Deploy Preview	https://deploy-preview-8--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 #11.