Skip to content

fix(deps): update …storybook-astro/framework to v1.16.0 - #309

Open
tbhb-dev-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/storybook-astro-framework-1.x
Open

tbhb-dev-renovate[bot] wants to merge 1 commit into
mainfrom
renovate/storybook-astro-framework-1.x

Conversation

@tbhb-dev-renovate

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@storybook-astro/framework (source) 1.15.0 → 1.16.0 age confidence

Release Notes

storybook-astro/storybook-astro (@​storybook-astro/framework)

v1.16.0

Compare Source

Added
  • Storybook 11 support, alongside Storybook 10 (#​205). Both packages accept Storybook 11, its prereleases included, as do the framework's optional peers for the React, Preact, Vue and Svelte renderers. Storybook 11 needs Node 22.12 or later. Install @storybook/builder-vite at the same version as storybook. The renderer's type declarations now build against Storybook 11's story context types, and with the Docgen Server enabled, a stories file's meta docblock still becomes the component description on Storybook 11 (#​207).
  • Solid stories work with the Storybook 11 builds of storybook-solidjs-vite, which export the Solid 1 preview entry as renderer/solid1 (#​208).
  • The Controls & ArgTypes docs page has a "Components manifest and AI agents" section (#​323). Its .storybook/main.js example turns on the components manifest that @storybook/addon-mcp reads, on Storybook 10.6 and 11, and it lists what the manifest needs. Since 1.14, builds with the manifest and the Docgen Server on no longer log a manifest error (#​183).
  • With the Docgen Server and the components manifest on, AI agents now get an Astro component's props and slots (#​353). @storybook/addon-mcp's docs-show used to return only the name and description, because Storybook doesn't pass the props table's rows to agents. The docgen payload now also carries them as Markdown (apiDescription): a Props type in the shape Storybook gives React components, with each prop's type (a union of literals lists its values, even behind a type Variant = … alias), whether it's optional, its default as the component writes it ('/home' stays quoted, defaultTitle doesn't gain quotes) and its description, then a list of slots and how a story fills them through args.slots. /manifests/components.html shows the same Markdown, and storybook build writes it in each component's services/core/docgen/ file. As for React components, docs-show now shows code for a component's first three stories and lists the rest by name (agents fetch those with the story documentation tool).
  • With the Docgen Server on, AI agents now get each Astro story's description and an Astro snippet (#​354). @storybook/addon-mcp's docs-show used to list no stories for an Astro component, and docs-show-story failed with "Available stories: none". The framework now provides Storybook's story docs: the snippet comes from the same generator as Show code, frontmatter import included, and is built from the args written in the stories file (merged over the meta's). A story whose args aren't all literal values, such as a component in a slot or an imported image, gets a warning naming the arg instead of a snippet. A function arg, such as an fn() spy or a method like onClick() {}, is left out, as Show code leaves it out. A story whose render function doesn't take args, or whose parameters (or its meta's) isn't written inline, such as one set from a variable or spreading another object, gets a warning instead of a snippet, since the snippet could show the wrong story. A story's hand-written parameters.docs.source.code is used as written, or gets a warning when it isn't a plain string (one built with dedent, say), and objectProps: 'inline' set on a story or its meta applies. With the Docgen Server on, a standalone <Source> block, such as one in an MDX page, shows this snippet, so it doesn't follow Controls, even for a story set to docs.source.type: 'dynamic'. Show code under a story on the Docs page doesn't use it and still follows Controls, as does the Code panel after the first edit. Args and an objectProps set in .storybook/preview.js aren't applied to the snippet. The description is the story's parameters.docs.description.story, as on the Docs page, or else its JSDoc comment. storybook build writes the snippets to services/core/story-docs/. Works on Storybook 10.6 and 11.
Fixed
  • Leaving an Astro story while the server is still rendering it no longer reloads the preview iframe (#​271). Storybook gives a story it removes a few ticks to finish, then reloads the page; the Astro render now stops waiting as soon as Storybook aborts it, and drops the server's response. This affected clicking another story during a slow render. On a story that uses mount, leaving the story or changing a Control while it renders still reloads the preview when its play function keeps running for more than a few ticks after mount() returns, such as while it awaits findBy* queries or other polling, because Storybook puts the story back into its playing phase after mount() returns.
  • An Astro render whose story has gone, because Storybook aborted it or its canvas left the document, no longer reports a server failure that arrives afterwards (#​303). An abandoned portable story run used to reject with the error, or with "Unable to reach Astro rendering server", and a Docs page could pass it to a story block that had already unmounted.
  • Leaving an Astro story while it renders now cancels its render request, instead of only ignoring the response (#​342). In server mode, clicking quickly through several slow stories could leave six or more requests open to the render server, fill the browser's connections to it, and make the current story fail with "Unable to reach Astro rendering server"; the abandoned fetches are now aborted. In dev, an abandoned request no longer holds its 5 s timer. In both modes the server still renders every request it received, including ones still queued behind another render, so the current story can still time out when the renders queued ahead of it take more than 5 s together. A story Storybook has already removed when its render begins, such as a play function calling mount() after the story was left, no longer sends a render request at all.
  • Show code and the Code panel no longer break on args that JSON can't represent (#​273). A Symbol arg, or an object prop holding a BigInt or a reference back to itself, used to throw inside the source decorator, leaving Show code empty and logging a story render error. Such a prop is now left out of the snippet, and a BigInt is written with its n. Inside object and array props, a Date is now written as new Date(...) instead of a string, NaN and Infinity as themselves instead of null, and undefined, function and Symbol array entries as undefined. An own __proto__ key is written as ["__proto__"], so the pasted literal adds the key instead of setting the object's prototype.
  • A @storybook/addon-vitest run exits as soon as its tests finish, instead of printing close timed out after 10000ms and waiting out Vitest's teardownTimeout (#​312). The addon starts two Vite servers, and the framework's internal Astro server for the first one was never closed.
  • In a project with more than one astro.config.* file, Storybook now searches in Astro's order, .mjs, .js, .ts, .mts, then .cjs and .cts (Astro 6 and 7 no longer read these two, but Storybook still checks them last) (#​257). Before, it checked astro.config.ts first, so a leftover astro.config.ts next to an astro.config.mjs supplied the integrations, vite.plugins, fonts, scopedStyleStrategy and compressHTML.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 has been generated by Mend Renovate CLI.

@tbhb-dev-renovate
tbhb-dev-renovate Bot enabled auto-merge (squash) November 17, 2026 00:57
@tbhb-dev-renovate
tbhb-dev-renovate Bot force-pushed the renovate/storybook-astro-framework-1.x branch from cddb140 to cac0ac3 Compare November 19, 2026 01:24
Signed-off-by: tbhb-dev-renovate[bot] <289255489+tbhb-dev-renovate[bot]@users.noreply.github.com>
@tbhb-dev-renovate
tbhb-dev-renovate Bot force-pushed the renovate/storybook-astro-framework-1.x branch from cac0ac3 to b91ecdd Compare November 19, 2026 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants