Storybook error in console after upgrade to 14.3.6
See original GitHub issuebootstrap:27 Uncaught ReferenceError: exports is not defined
at ./apps/test/.storybook/preview.js
main.js
core: {},
stories: [
'../src/**/*.stories.mdx',
'../src/**/*.stories.@(js|jsx|ts|tsx)',
],
addons: ['@storybook/addon-essentials', '@nrwl/react/plugins/storybook'],
webpackFinal: async (config) => {
const tsPaths = new TsconfigPathsPlugin({
configFile: './tsconfig.base.json',
});
return merge(config, {
resolve: {
plugins: [tsPaths],
},
});
},
test/main.js
module.exports = {
...rootMain,
core: { ...rootMain.core, builder: 'webpack5' }, // This needs to be here and not in rootMain, otherwise nx throws false positive error that it's missing.
staticDirs: ['../src'],
};
Issue Analytics
- State:
- Created a year ago
- Comments:25 (23 by maintainers)
Top Results From Across the Web
Upgrading Storybook
This upgrades all of the Storybook packages in your project to the latest stable version, perform confidence checks of your package versions, and...
Read more >Error during 14.0.12 > 14.3.6 upgrade - How to Use GitLab
The migrations had not finished in the previous upgrade - My second attempt at this upgrade worked ok after reverting to pre-upgrade snapshot....
Read more >J Troubleshooting Oracle Audit Vault and Database Firewall
Solution - 1. The symptom indicates that the Audit Vault Agent has failed to auto upgrade during the Audit Vault Server upgrade. Execute...
Read more >"Failed to connect to the server" or "Error 1069" after upgrade ...
Open the Local Group Policy Editor Management Console. · In the left pane, under Computer Configuration, click Windows Settings > Security ...
Read more >The OpenVMS Frequently Asked Questions(FAQ) - Digiater.nl
Update the SCSNODE in MODPARAMS.DAT, and then run AUTOGEN as far as the SETPARAMS phase. (Do not reboot yet.) Modify the DECnet node...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@mandarini Solved by adding
unambiguous
inbabel.config.js
. As we are using ES6 together with Common JS in our app, there was an issue with exports / imports. More about that in official documentation of Babel: https://babeljs.io/docs/en/options#misc-options. Thanks for the support on the way. It was really a pleasure to see the effort 😃Hi Katerina, I’m still struggling with that. Unfortunately, I didn’t have time last week to stay focused on that.