chore(deps-dev): bump storybook-solidjs-vite from 10.0.9 to 10.1.1

[dependabot]

Bumps storybook-solidjs-vite from 10.0.9 to 10.1.1.

Changelog

Sourced from storybook-solidjs-vite's changelog.

10.1.1

Patch Changes

• fa5706c: Fix git path in package

10.1.0

Minor Changes

• 9058c6f: ### Solid 2 support

  Solid 2 projects should import types and APIs from storybook-solidjs-vite/next in stories, preview, and other app code for correct Solid 2 typings:

  import type { Preview, Meta, StoryObj } from "storybook-solidjs-vite/next";

  You can still import from storybook-solidjs-vite without /next on Solid 2, but that may produce TypeScript errors because those types target the Solid 1 renderer.

  In .storybook/main.ts, both framework names are valid:

  • storybook-solidjs-vite — auto-detects Solid version from installed solid-js (works for Solid 2 projects)
  • storybook-solidjs-vite/next — pins the Solid 2 renderer explicitly

  // Either is fine for a Solid 2 app
  framework: "storybook-solidjs-vite";
  framework: "storybook-solidjs-vite/next";

  Solid 1 projects keep using storybook-solidjs-vite for imports and framework config.

  CSF Next (optional)

  definePreview, preview.meta, and meta.story are also available on both Solid 1 and Solid 2. CSF 3 (Meta, StoryObj, default export meta) continues to work; migrate to CSF Next when you want factory-based typing, not as a requirement for Solid 2.

  // .storybook/main.ts
  import { defineMain } from "storybook-solidjs-vite/node";
  export default defineMain({
  framework: { name: "storybook-solidjs-vite/next" },
  });

  // .storybook/preview.tsx
  import { definePreview } from "storybook-solidjs-vite/next";

... (truncated)

Commits

• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for storybook-solidjs-vite since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

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 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)