You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Storybook's project.json reports the addons that are listed in .storybook/main.ts. It does this by calling getActualPacakgeVersion on each of the addons:
info "addons": {
info "$SNIP/node_modules/.pnpm/@storybook+addon-onboarding@8.5.0-alpha.8_react@18.3.1_storybook@8.5.0-alpha.8/node_modules/@storybook/addon-onboarding": {
info "version": null
info },
info "$SNIP/node_modules/.pnpm/@storybook+addon-essentials@8.5.0-alpha.8_@types+react@18.3.12_storybook@8.5.0-alpha.8/node_modules/@storybook/addon-essentials": {
info "version": null
info },
info "$SNIP/node_modules/.pnpm/@chromatic-com+storybook@3.2.2_react@18.3.1_storybook@8.5.0-alpha.8/node_modules/@chromatic-com/storybook": {
info "version": null
info },
Instead, it should produce:
info "addons": {
info "@storybook/addon-onboarding": {
info "version": "8.5.0-alpha.8"
info },
info "@storybook/addon-essentials": {
info "version": "8.5.0-alpha.8"
info },
info "@chromatic-com/storybook": {
info "version": "3.2.2"
info },
Reproduction link
N/A
Reproduction steps
See above
System
Any
Additional context
No response
The text was updated successfully, but these errors were encountered:
shilman
changed the title
[Bug]: getAbsolutePath results in broken project.json
[Bug]: Monorepo getAbsolutePath results in broken project.jsonNov 19, 2024
Describe the bug
Currently Storybook's
project.json
reports the addons that are listed in.storybook/main.ts
. It does this by callinggetActualPacakgeVersion
on each of the addons:https://github.com/storybookjs/storybook/blob/next/code/core/src/telemetry/package-json.ts
However, in monorepos we recommend using absolute paths with the following pattern:
This generates addon entries like the following:
Instead, it should produce:
Reproduction link
N/A
Reproduction steps
See above
System
Additional context
No response
The text was updated successfully, but these errors were encountered: