@astrojs/solid-js

• 5.0.4

  Jan 20, 2025

  🐞 Patch Changes

  • #13011 cf30880 Thanks @ascorbic! - Upgrades Vite
• 5.0.3

  Jan 15, 2025

  🐞 Patch Changes

  • #12887 ea603ae Thanks @louisescher! - Adds a warning message when multiple JSX-based UI frameworks are being used without either the include or exclude property being set on the integration.
• 5.0.2

  Jan 13, 2025

  🐞 Patch Changes

  • #12923 c7642fb Thanks @bluwy! - Adds the client entrypoint to optimizeDeps.include
• 5.0.1

  Dec 20, 2024

  🐞 Patch Changes

  • #12799 739dbfb Thanks @ascorbic! - Upgrades Vite to pin esbuild
• 5.0.0

  Dec 3, 2024

  ✨ Major Changes

  • #12524 9f44019 Thanks @bluwy! - Updates Vite dependency to v6 to match Astro v5

  🍿 Minor Changes

  • #12539 827093e Thanks @bluwy! - Drops node 21 support

  🐞 Patch Changes

  • #12524 9f44019 Thanks @bluwy! - Updates vite-plugin-solid to handle Vite 6
• 5.0.0-beta.1

  Nov 27, 2024

  ✨ Major Changes

  • #12524 9f44019 Thanks @bluwy! - Updates Vite dependency to v6 to match Astro v5

  🍿 Minor Changes

  • #12539 827093e Thanks @bluwy! - Drops node 21 support

  🐞 Patch Changes

  • #12524 9f44019 Thanks @bluwy! - Updates vite-plugin-solid to handle Vite 6
• 4.4.4

  Nov 21, 2024

  🐞 Patch Changes

  • #12481 8a46e80 Thanks @marbrex! - Resolve vite peer dependency problem for strict package managers like Yarn in PnP mode.
• 4.4.4-beta.0

  Nov 21, 2024

  🐞 Patch Changes

  • #12481 8a46e80 Thanks @marbrex! - Resolve vite peer dependency problem for strict package managers like Yarn in PnP mode.
• 4.4.3

  Nov 15, 2024

  🐞 Patch Changes

  • #12364 9fc2ab8 Thanks @jdtjenkins! - Handles checking Svelte 5 component functions to avoid processing them as Solid components
• 4.4.2

  Sep 17, 2024

  🐞 Patch Changes

  • #11998 082f450 Thanks @johannesspohr! - Fix view transition state persistence
• 4.4.1

  Aug 9, 2024

  🐞 Patch Changes

  • #11624 7adb350 Thanks @bluwy! - Prevents throwing errors when checking if a component is a Solid component in runtime
• 4.4.0

  Jun 17, 2024

  🍿 Minor Changes

  • #11234 4385bf7 Thanks @ematipico! - Adds a new function called addServerRenderer to the Container API. Use this function to manually store renderers inside the instance of your container.

    This new function should be preferred when using the Container API in environments like on-demand pages:

    import type { APIRoute } from 'astro';
    import { experimental_AstroContainer } from 'astro/container';
    import reactRenderer from '@astrojs/react/server.js';
    import vueRenderer from '@astrojs/vue/server.js';
    import ReactComponent from '../components/button.jsx';
    import VueComponent from '../components/button.vue';
    
    // MDX runtime is contained inside the Astro core
    import mdxRenderer from 'astro/jsx/server.js';
    
    // In case you need to import a custom renderer
    import customRenderer from '../renderers/customRenderer.js';
    
    export const GET: APIRoute = async (ctx) => {
      const container = await experimental_AstroContainer.create();
      container.addServerRenderer({ renderer: reactRenderer });
      container.addServerRenderer({ renderer: vueRenderer });
      container.addServerRenderer({ renderer: customRenderer });
      // You can pass a custom name too
      container.addServerRenderer({
        name: 'customRenderer',
        renderer: customRenderer,
      });
      const vueComponent = await container.renderToString(VueComponent);
      return await container.renderToResponse(Component);
    };

• 4.3.0

  Jun 6, 2024

  🍿 Minor Changes

  • #11144 803dd80 Thanks @ematipico! - The integration now exposes a function called getContainerRenderer, that can be used inside the Container APIs to load the relative renderer.

    import { experimental_AstroContainer as AstroContainer } from 'astro/container';
    import ReactWrapper from '../src/components/ReactWrapper.astro';
    import { loadRenderers } from 'astro:container';
    import { getContainerRenderer } from '@astrojs/react';
    
    test('ReactWrapper with react renderer', async () => {
      const renderers = await loadRenderers([getContainerRenderer()]);
      const container = await AstroContainer.create({
        renderers,
      });
      const result = await container.renderToString(ReactWrapper);
    
      expect(result).toContain('Counter');
      expect(result).toContain('Count: <!-- -->5');
    });

• 4.2.0

  May 9, 2024

  🍿 Minor Changes

  • #10937 7179930 Thanks @florian-lefebvre! - Adds a devtools option

    You can enable the official Solid Devtools while working in development mode by setting devtools: true in your solid() integration config and adding solid-devtools to your project dependencies:

    npm install solid-devtools
    # yarn add solid-devtools
    # pnpm add solid-devtools

    import { defineConfig } from 'astro/config';
    import solid from '@astrojs/solid-js';
    
    export default defineConfig({
      integrations: [solid({ devtools: true })],
    });

• 4.1.0

  Apr 11, 2024

  🍿 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

  Jan 5, 2024

  🐞 Patch Changes

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

  Jan 4, 2024

  ✨ 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

  Dec 27, 2023

  🐞 Patch Changes

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

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

• 3.0.1

  Sep 8, 2023

  🐞 Patch Changes

  • #8365 a525d5db1 Thanks @ryansolid! - Fix hydration in Solid renderer
• 3.0.0

  Aug 30, 2023

  ✨ Major Changes

  • #8188 d0679a666 Thanks @ematipico! - Remove support for Node 16. The lowest supported version by Astro and all integrations is now v18.14.1. As a reminder, Node 16 will be deprecated on the 11th September 2023.

  • #7924 519a1c4e8 Thanks @matthewp! - New include and exclude config options

    The Solid integration now has new include and exclude config options. Use these if you want to use Solid alongside another JSX framework; include specifies files to be compiled for Solid and exclude does the opposite.

  • #8179 6011d52d3 Thanks @matthewp! - Astro 3.0 Release Candidate

  🐞 Patch Changes

  • #8264 1f58a7a1b Thanks @natemoo-re! - Automatically unmount islands when astro:unmount is fired