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, as my work build has currently progressed forward into a monorepo build using lerna + pnpm, I had to migrate forward to the latest versions of the @mdx-js libraries to enable some cross-libraries' functions.
Tentatively, I have managed to somehow "fixed" most of the "constantly-breaking" issues, but the main issue that I can't seem to fix is still having the default StorybookJS theme being properly displayed, and the UI issues I'm facing right now are similar to the ones I have previously reported #18383.
To Reproduce
[This is a work-related build, thus I will not be able to showcase all the info]
Please bear in mind that this issue relates to a monorepo build just to clear any potential confusion in the file structure.
The key point to also note is that this build is running on MDX2.
These are the main related dependencies I'm using:
TL;DR: Running the npm run storybook command works, but the default theme is just not loading.
Due to the upgrade to Storybook v7.0.0-alpha.34, the new npm run storybook script command is now sb dev instead of the previous start-storybook (Ref link of migration to v7.0).
Sometimes, the dev command doesn't work all the time and randomly throws out a various series of different types of errors from time-to-time like:
[a] WARN Force closed manager build:
/node_modules/.pnpm/[email protected]/node_modules/webpack/lib/NormalModule.js:758
const error = new ModuleBuildError(err, {
^
ModuleBuildError: Module build failed (from ../../node_modules/.pnpm/[email protected]_wfdvla2jorjoj23kkavho2upde/node_modules/babel-loader/lib/index.js):
/node_modules/.pnpm/@[email protected]/node_modules/@babel/core/lib/config/config-descriptors.js:224
throw new Error([`Duplicate plugin/preset detected.`, `If you'd like to use two separate instances of a plugin,`, `they need separate names, e.g.`, ``, ` plugins: [`, ` ['some-plugin', {}],`, ` ['some-plugin', {}, 'some unique name'],`, ` ]`, ``, `Duplicates detected are:`, `${JSON.stringify(conflicts, null, 2)}`].join("\n"));
^
Error: Duplicate plugin/preset detected.
If you'd like to use two separate instances of a plugin,
they need separate names, e.g.
plugins: [
['some-plugin', {}],
['some-plugin', {}, 'some unique name'],
]
Duplicates detected are:
[
{
"alias": "/node_modules/.pnpm/[email protected]/node_modules/babel-plugin-add-react-displayname/index.js",
"dirname": "/modules/docs",
"ownPass": false,
"file": {
"request": "/node_modules/.pnpm/[email protected]/node_modules/babel-plugin-add-react-displayname/index.js",
"resolved": "/node_modules/.pnpm/[email protected]/node_modules/babel-plugin-add-react-displayname/index.js"
}
},
{
"alias": "/node_modules/.pnpm/[email protected]/node_modules/babel-plugin-add-react-displayname/index.js",
"dirname": "/modules/docs",
"ownPass": false,
"file": {
"request": "/node_modules/.pnpm/[email protected]/node_modules/babel-plugin-add-react-displayname/index.js",
"resolved": "/node_modules/.pnpm/[email protected]/node_modules/babel-plugin-add-react-displayname/index.js"
}
}
]
[b] Endless Cycles of WARN Failed to load preset
I hope the above will help provide some context on the issue I'm facing, though I do understand that due to the alpha release, there will still be a lot of issues to iron out before it becomes stable.
Hope to seek some guidance on the above.
Thank you!
The text was updated successfully, but these errors were encountered:
Describe the bug
I had a
partially-working
copy (Ref: #18383), after downgrading some@mdx-js
libraries to a previous version1.6.22
as follows:However, as my work build has currently progressed forward into a
monorepo
build usinglerna
+pnpm
, I had to migrate forward to the latest versions of the@mdx-js
libraries to enable some cross-libraries' functions.Tentatively, I have managed to somehow "fixed" most of the "constantly-breaking" issues, but the main issue that I can't seem to fix is still having the default StorybookJS theme being properly displayed, and the UI issues I'm facing right now are similar to the ones I have previously reported #18383.
To Reproduce
[This is a work-related build, thus I will not be able to showcase all the info]
Please bear in mind that this issue relates to a
monorepo
build just to clear any potential confusion in the file structure.The key point to also note is that this build is running on
MDX2
.These are the main related dependencies I'm using:
System
Please paste the results of
npx sb@next info
here.Additional context
npm run storybook
command works, but the default theme is just not loading.Storybook v7.0.0-alpha.34
, the newnpm run storybook
script command is nowsb dev
instead of the previousstart-storybook
(Ref link of migration to v7.0).WARN Force closed manager build
:WARN Failed to load preset
I hope the above will help provide some context on the issue I'm facing, though I do understand that due to the
alpha
release, there will still be a lot of issues to iron out before it becomes stable.Hope to seek some guidance on the above.
Thank you!
The text was updated successfully, but these errors were encountered: