-
Notifications
You must be signed in to change notification settings - Fork 1
/
migration-storybook.log
202 lines (185 loc) · 28.7 KB
/
migration-storybook.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
🔎 checking possible migrations..
🔎 found a 'eslintPlugin' migration:
╭ Automigration detected ──────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ We've detected you are not using our eslint-plugin. │
│ │
│ In order to have the best experience with Storybook and follow best practices, we advise you to install eslint-plugin-storybook. │
│ │
│ More info: https://github.com/storybookjs/eslint-plugin-storybook#readme │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? Do you want to run the 'eslintPlugin' migration on your project? › (Y/n)✔ Do you want to run the 'eslintPlugin' migration on your project? … yes
✅ Adding dependencies: eslint-plugin-storybook
Configuring Storybook ESLint plugin at .eslintrc.json
✅ ran eslintPlugin migration
🔎 found a 'storybook-binary' migration:
╭ Automigration detected ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ We've detected you are using Storybook 7.0.12 without Storybook's storybook binary. Starting in Storybook 7.0, it has to be installed. │
│ │
│ │
│ More info: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#start-storybook--build-storybook-binaries-removed │
│ │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? Do you want to run the 'storybook-binary' migration on your project? › (Y/n)✔ Do you want to run the 'storybook-binary' migration on your project? … yes
✅ Adding 'storybook' as dev dependency
✅ ran storybook-binary migration
🔎 found a 'sb-scripts' migration:
╭ Automigration detected ───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ We've detected you are using Storybook 7.0.12 with scripts from previous versions of Storybook. │
│ Starting in Storybook 7, the start-storybook and build-storybook binaries have changed to storybook dev and storybook build respectively. │
│ In order to work with Storybook 7.0.12, your storybook scripts have to be adjusted to use the binary. We can adjust them for you: │
│ │
│ storybook │
│ from: │
│ start-storybook -p 6006 │
│ to: │
│ storybook dev -p 6006 │
│ │
│ storybook:build │
│ from: │
│ build-storybook -c .storybook │
│ to: │
│ storybook build -c .storybook │
│ │
│ snapshot │
│ from: │
│ build-storybook -c .storybook && percy storybook ./storybook-static │
│ to: │
│ storybook build -c .storybook && percy storybook ./storybook-static │
│ │
│ In case this migration did not cover all of your scripts, or you'd like more info: │
│ https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#start-storybook--build-storybook-binaries-removed │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? Do you want to run the 'sb-scripts' migration on your project? › (Y/n)✔ Do you want to run the 'sb-scripts' migration on your project? … yes
✅ Updating scripts in package.json
✅ ran sb-scripts migration
🔎 found a 'new-frameworks' migration:
╭ Automigration detected ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ We've detected your project is not fully setup with Storybook's 7 new framework format. │
│ │
│ Storybook 7 introduced the concept of frameworks, which abstracts configuration for renderers (e.g. React, Vue), builders (e.g. Webpack, Vite) and defaults to make │
│ integrations easier. │
│ │
│ Your project should be updated to use Storybook's framework: @storybook/react-webpack5. We can attempt to do this for you automatically. │
│ │
│ Here are the steps this migration will do to migrate your project: │
│ - Add the following dependencies: │
│ - * @storybook/react-webpack5 │
│ - Update or specify the framework field in .storybook/main.js with the value of "@storybook/react-webpack5". │
│ │
│ │
│ To learn more about the new framework format, see: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#new-framework-api │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? Do you want to run the 'new-frameworks' migration on your project? › (Y/n)✔ Do you want to run the 'new-frameworks' migration on your project? … no
🔎 found a 'incompatible-addons' migration:
╭ Manual migration detected ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Attention: We've detected that you're using the following addons in versions which are known to be incompatible with Storybook 7: │
│ │
│ - [email protected] │
│ │
│ Please be aware they might not work in Storybook 7. Reach out to their maintainers for updates and check the following Github issue for more information: │
│ https://github.com/storybookjs/storybook/issues/20529 │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? 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
🔎 found a 'mdx1to2' migration:
╭ Automigration detected ──────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ We've found 7 '.stories.mdx' files in your project. │
│ │
│ Storybook has upgraded to MDX2 (https://mdxjs.com/blog/v2/), which contains breaking changes from MDX1. │
│ We can try to automatically upgrade your MDX files to MDX2 format using some common patterns. │
│ │
│ After this install completes, and before you start Storybook, we strongly recommend reading the MDX2 section │
│ of the 7.0 migration guide. It contains useful tools for detecting and fixing any remaining issues. │
│ │
│ https://storybook.js.org/migration-guides/7.0 │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? Do you want to run the 'mdx1to2' migration on your project? › (Y/n)✔ Do you want to run the 'mdx1to2' migration on your project? … yes
🆗 Unmodified DesignTokens.stories.mdx
🆗 Unmodified Box.stories.mdx
🆗 Unmodified Flex.stories.mdx
🆗 Unmodified Grid.stories.mdx
🆗 Unmodified Welcome.stories.mdx
🆗 Unmodified index.stories.mdx
🆗 Unmodified Spacing.stories.mdx
✅ ran mdx1to2 migration
🔎 found a 'github-flavored-markdown-mdx' migration:
╭ Automigration detected ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ In MDX1 you had the option of using GitHub flavored markdown. │
│ │
│ Storybook 7.0 uses MDX2 for compiling MDX, and thus no longer supports GFM out of the box. │
│ Because of this you need to explicitly add the GFM plugin in the addon-docs options: │
│ https://storybook.js.org/docs/react/writing-docs/mdx#lack-of-github-flavored-markdown-gfm │
│ │
│ We recommend you follow the guide on the link above, however we can add a temporary storybook addon that helps make this migration easier. │
│ We'll install the addon and add it to your storybook config. │
│ │
╰────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
? Do you want to run the 'github-flavored-markdown-mdx' migration on your project? › (Y/n)✔ Do you want to run the 'github-flavored-markdown-mdx' migration on your project? … no
🔎 found a 'autodocsTrue' migration:
╭ Automigration detected ────────────────────────────────────────────────────────────────────────────╮
│ │
│ We've changed the configuration of autodocs (previous docsPage), so now the value: │
│ - docs.autodocs: true -- means automatically create docs for every CSF file │
│ - docs.autodocs: 'tag' -- means only create autodocs for CSF files with the 'autodocs' tag │
│ - docs.autodocs: false -- means never create autodocs │
│ │
│ Based on your prior configuration, we can set the `docs.autodocs` to keep your old behaviour: │
│ │
│ docs: { autodocs: true } │
│ │
│ More info: https://github.com/storybookjs/storybook/blob/next/MIGRATION.md#autodocs-changes │
│ │
╰────────────────────────────────────────────────────────────────────────────────────────────────────╯
? Do you want to run the 'autodocsTrue' migration on your project? › (Y/n)✔ Do you want to run the 'autodocsTrue' migration on your project? … yes
✅ Setting 'docs.autodocs' to true in main.js
✅ ran autodocsTrue migration
⚠️ failed to check fix missing-babelrc
TypeError: Cannot read properties of undefined (reading 'name')
at Object.check (/Users/vskupien/.npm/_npx/bc7e1e37fcb46ffc/node_modules/@storybook/cli/dist/generate.js:292:763)
at async runFixes (/Users/vskupien/.npm/_npx/bc7e1e37fcb46ffc/node_modules/@storybook/cli/dist/generate.js:352:1154)
at async automigrate (/Users/vskupien/.npm/_npx/bc7e1e37fcb46ffc/node_modules/@storybook/cli/dist/generate.js:349:676)
at async doUpgrade (/Users/vskupien/.npm/_npx/bc7e1e37fcb46ffc/node_modules/@storybook/cli/dist/generate.js:381:2905)
at async withTelemetry (/Users/vskupien/.npm/_npx/bc7e1e37fcb46ffc/node_modules/@storybook/core-server/dist/index.js:35:3422)
at async upgrade (/Users/vskupien/.npm/_npx/bc7e1e37fcb46ffc/node_modules/@storybook/cli/dist/generate.js:381:3351)
╭ Migration check ran with failures ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ │
│ Successful migrations: │
│ │
│ eslintPlugin, storybook-binary, sb-scripts, mdx1to2, autodocsTrue │
│ │
│ Failed migrations: │
│ │
│ missing-babelrc: │
│ Cannot read properties of undefined (reading 'name') │
│ │
│ You can find the full logs in /Users/vskupien/Documents/GitHub/phoenix-components/migration-storybook.log │
│ │
│ Manual migrations: │
│ │
│ incompatible-addons │
│ │
│ Skipped migrations: │
│ │
│ new-frameworks, github-flavored-markdown-mdx │
│ │
│ ───────────────────────────────────────────────── │
│ │
│ 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 │
│ │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯