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
Following up the discussion at #11745 (comment) (and below) we want to
have a sensible preview.tsx (which already exists as template in the codebase) when installing cli-storybook-vite (which is done automatically since RW 8 on first execution of yarn rw sb).
At least no. 3 may be considered for a patch release for the current v8 release as it may fix things (although no issues have been reported so far that are rooted in this).
The text was updated successfully, but these errors were encountered:
paths.ts uses a different path for the new location, the old location can be removed. This was because there was a period where we had both, and they work fundamentally differently. If we think it'll be valuable, we can add paths to the various Storybook config files, but they should follow the newer naming convention as the current/old ones imply that they're in the config folder.
Anything relying on that configureStorybook script needs to be updated - I'm positive that anything those UI library scripts were doing for Storybook no longer work.
Following up the discussion at #11745 (comment) (and below) we want to
preview.tsx
(which already exists as template in the codebase) when installingcli-storybook-vite
(which is done automatically since RW 8 on first execution ofyarn rw sb
).[https://github.com/redwoodjs/redwood/blob/main/packages/cli/src/lib/configureStorybook.js](configureStorybook.js)
, however it needs to be ensured that this is not needed anywhere else, i.e. https://github.com/redwoodjs/redwood/blob/v8.4.1/packages/cli/src/commands/setup/ui/libraries/chakra-ui.js#L10)web/config
) are migrated to the newweb/.storybook
directory (i.e. https://github.com/redwoodjs/redwood/blob/v8.4.1/packages/project-config/src/paths.ts#L126-L128) – may be wise to do a fulltext search to ensure nothing is left out hereAt least no. 3 may be considered for a patch release for the current v8 release as it may fix things (although no issues have been reported so far that are rooted in this).
The text was updated successfully, but these errors were encountered: