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
However, that means the snapshots are created twice: one in the current project and one in the referenced project(s).
Also, this is not ideal when the projects have different settings.
If we can leverage Vitest's projects/workspace feature to run multiple instances and combine the result, that would be ideal.
However, that is not likely the case as we are breaking the project boundary with this "source project reference" approach in Storybook.
Another alternative is to disable or filter to only run snapshots withi3n the current project folder. But that means we will not be able to detect the snapshot failures or show the snaphots of the referenced projects.
A workaround right now is to ignore the snapshots with __/ path in the .gitignore file.
But we should discuss and see what else can be done to improve the system.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When using Storybook in monorepo, one way is take the "source project reference" approach:
With vitest-plugin-vis@3.5.1, we support this case by replacing
..in the path with__.However, that means the snapshots are created twice: one in the current project and one in the referenced project(s).
Also, this is not ideal when the projects have different settings.
If we can leverage Vitest's projects/workspace feature to run multiple instances and combine the result, that would be ideal.
However, that is not likely the case as we are breaking the project boundary with this "source project reference" approach in Storybook.
Another alternative is to disable or filter to only run snapshots withi3n the current project folder. But that means we will not be able to detect the snapshot failures or show the snaphots of the referenced projects.
A workaround right now is to ignore the snapshots with
__/path in the.gitignorefile.But we should discuss and see what else can be done to improve the system.
Beta Was this translation helpful? Give feedback.
All reactions