๐Ÿ”Ž checking possible migrations.. ๐Ÿ”Ž found a 'viteConfigFile' migration: โ•ญ Automigration detected โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”‚ โ”‚ โ”‚ Storybook 8.0.0 no longer ships with a Vite config build-in. โ”‚ โ”‚ Please add a vite.config.js file to your project root. โ”‚ โ”‚ โ”‚ โ”‚ You can find more information on how to do this here: โ”‚ โ”‚ https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#framework-specific-vite-plugins-have-to-be-expli โ”‚ โ”‚ citly-added โ”‚ โ”‚ โ”‚ โ”‚ This change was necessary to support newer versions of Vite. โ”‚ โ”‚ โ”‚ โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ ? Do you want to run the 'viteConfigFile' migration on your project? ยป (Y/n)โˆš Do you want to run the 'viteConfigFile' migration on your project? ... yes โŒ error when running viteConfigFile migration Error: Invariant failed: run method should be available in fix. at invariant (C:\Users\User\AppData\Local\npm-cache\_npx\eb8bf615e50a412a\node_modules\tiny-invariant\dist\tiny-invariant.cjs.js:14:11) at runFixes (C:\Users\User\AppData\Local\npm-cache\_npx\eb8bf615e50a412a\node_modules\@storybook\cli\dist\generate.js:544:1595) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async automigrate (C:\Users\User\AppData\Local\npm-cache\_npx\eb8bf615e50a412a\node_modules\@storybook\cli\dist\generate.js:542:1403) at async doUpgrade (C:\Users\User\AppData\Local\npm-cache\_npx\eb8bf615e50a412a\node_modules\@storybook\cli\dist\generate.js:577:1646) at async withTelemetry (C:\Users\User\AppData\Local\npm-cache\_npx\eb8bf615e50a412a\node_modules\@storybook\core-server\dist\index.js:28:3579) at async upgrade (C:\Users\User\AppData\Local\npm-cache\_npx\eb8bf615e50a412a\node_modules\@storybook\cli\dist\generate.js:577:2042) Unable to find .eslintrc config file, skipping ๐Ÿ”Ž found a 'remove-argtypes-regex' migration: โ•ญ Manual migration detected โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”‚ โ”‚ โ”‚ Attention: We've detected that you're using argTypesRegex: โ”‚ โ”‚ โ”‚ โ”‚ .storybook\preview.ts โ”‚ โ”‚ 3 | const preview: Preview = { โ”‚ โ”‚ 4 | parameters: { โ”‚ โ”‚ > 5 | actions: { argTypesRegex: '^on[A-Z].*' }, โ”‚ โ”‚ | ^^^^^^^^^^^^^ โ”‚ โ”‚ 6 | controls: { โ”‚ โ”‚ 7 | matchers: { โ”‚ โ”‚ 8 | color: /(background|color)$/i, โ”‚ โ”‚ โ”‚ โ”‚ In Storybook 8, we recommend removing this regex. โ”‚ โ”‚ Assign explicit spies with the fn function instead: โ”‚ โ”‚ โ”‚ โ”‚ 1 | import { fn } from '@storybook/test'; โ”‚ โ”‚ 2 | export default { โ”‚ โ”‚ > 3 | args: { onClick: fn() }, // will log to the action panel when clicked โ”‚ โ”‚ | ^^ โ”‚ โ”‚ 4 | }; โ”‚ โ”‚ โ”‚ โ”‚ The above pattern is needed when using spies in the play function, even if you keep using argTypesRegex. โ”‚ โ”‚ Implicit spies (based on a combination of argTypesRegex and docgen) is not supported in Storybook 8. โ”‚ โ”‚ โ”‚ โ”‚ Use the following command to check for spy usages in your play functions: โ”‚ โ”‚ npx storybook migrate find-implicit-spies --glob="**/*.stories.@(js|jsx|ts|tsx)" โ”‚ โ”‚ โ”‚ โ”‚ Make sure to assign an explicit fn to your args for those usages. โ”‚ โ”‚ โ”‚ โ”‚ For more information please visit our migration guide: https://github.com/storybookjs/storybook/blob/next/MIGRAT โ”‚ โ”‚ ION.md#implicit-actions-can-not-be-used-during-rendering-for-example-in-the-play-function โ”‚ โ”‚ โ”‚ โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ ? Select continue once you have made the required changes, or quit to exit the migration process ยป quit / continueโˆš Select continue once you have made the required changes, or quit to exit the migration process ... quit / continue โ•ญ Migration check ran with failures โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”‚ โ”‚ โ”‚ Failed migrations: โ”‚ โ”‚ โ”‚ โ”‚ viteConfigFile: โ”‚ โ”‚ Invariant failed: run method should be available in fix. โ”‚ โ”‚ โ”‚ โ”‚ You can find the full logs in C:\TY\Projects\ff-library\migration-storybook.log โ”‚ โ”‚ โ”‚ โ”‚ Manual migrations: โ”‚ โ”‚ โ”‚ โ”‚ remove-argtypes-regex โ”‚ โ”‚ โ”‚ โ”‚ โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ โ”‚ โ”‚ โ”‚ โ”‚ If you'd like to run the migrations again, you can do so by running 'npx storybook@next automigrate' โ”‚ โ”‚ โ”‚ โ”‚ The automigrations try to migrate common patterns in your project, but might not contain everything needed to โ”‚ โ”‚ migrate to the latest version of Storybook. โ”‚ โ”‚ โ”‚ โ”‚ Please check the changelog and migration guide for manual migrations and more information: โ”‚ โ”‚ https://storybook.js.org/migration-guides/7.0 โ”‚ โ”‚ And reach out on Discord if you need help: https://discord.gg/storybook โ”‚ โ”‚ โ”‚ โ”‚ โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€ โ”‚ โ”‚ โ”‚ โ”‚ Critical: The following dependencies are duplicated and WILL cause unexpected behavior: โ”‚ โ”‚ โ”‚ โ”‚ @storybook/core-common: โ”‚ โ”‚ 8.0.0-beta.5, 7.6.17 โ”‚ โ”‚ โ”‚ โ”‚ @storybook/core-events: โ”‚ โ”‚ 8.0.0-beta.5, 7.6.17 โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ Attention: The following dependencies are duplicated which might cause unexpected behavior: โ”‚ โ”‚ โ”‚ โ”‚ @storybook/telemetry: โ”‚ โ”‚ 8.0.0-beta.5, 7.6.17 โ”‚ โ”‚ โ”‚ โ”‚ @storybook/csf-tools: โ”‚ โ”‚ 8.0.0-beta.5, 7.6.17 โ”‚ โ”‚ โ”‚ โ”‚ @storybook/node-logger: โ”‚ โ”‚ 8.0.0-beta.5, 7.6.17 โ”‚ โ”‚ โ”‚ โ”‚ @storybook/types: โ”‚ โ”‚ 8.0.0-beta.5, 7.6.17 โ”‚ โ”‚ โ”‚ โ”‚ @storybook/channels: โ”‚ โ”‚ 8.0.0-beta.5, 7.6.17 โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ You can find more information for a given dependency by running yarn why โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ โ”‚ Please try de-duplicating these dependencies by running yarn dedupe โ”‚ โ”‚ โ”‚ โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ