Skip to content

v0.16.2

Choose a tag to compare

@github-actions github-actions released this 01 Oct 05:29
· 321 commits to main since this release

compare changes

poveste dev rendered no story at all for a consumer installed with npm, silently, in both 0.16.0 and 0.16.1.

It is a patch: no commit in the range is a feat, none carries a ! marker or a BREAKING CHANGE footer, and nothing is deprecated, renamed or removed. There is nothing to do on upgrade — no configuration key changed and no version floor moved.

🩹 Fixes

  • poveste dev shows your stories again (#1060, #1066). The sidebar listed every story and its variant count, the URL never gained ?variantId=, and the panel stayed empty — with no error and no warning anywhere a reader could see one. The cause was two Vue runtimes in one page: Poveste's chrome depends on Vue under an aliased name, an alias is a distinct package name, and a package manager installs a second copy of Vue whatever your project already has. The chrome's components rendered with one copy while the router reacted with the other, so the first render was never invalidated. Nothing warns, because neither copy is wrong — they cannot see each other. If poveste dev showed your stories, you were not affected, and poveste build followed by poveste preview was never affected either, so a reader who only built a book lost nothing. Installing with pnpm was also never affected: it resolves both names to one copy on its own.

🤖 CI

  • The publish gate installs every published plugin from a tarball (#1052, #1067), at the peer ranges each plugin declares rather than at ranges copied into the script. Nothing a consumer installs changes.

Upgrading

Nothing to do. No configuration key changed, no option was removed or renamed, and no engines.node, peer dependency or export floor moved on any published package. Stories that worked on 0.16.1 work here unchanged.

If poveste dev was blank for you, upgrade and it renders. The condition was installing with npm into a project that has a Vue of its own; it was reported on plain Vue and on Quasar.

If you only ever ran poveste build, there is nothing here you were missing.


   🐞 Bug Fixes

  • ci: Run a consumer-install pass for every published plugin, at declared ranges  -  by @50rayn in #1067 (0f0c6)
  • node: Give a consumer's chrome and stories one Vue, which an npm alias split  -  by @50rayn in #1066 (5c288)
    View changes on GitHub