Storybook is broken

[Golodhros]

After updating to Webpack 5, Storybook got broken as it wasn't supporting it yet.

Expected Behavior

Storybook should be running in the local dev environment

Possible Solution

They just released experimental support of Webpack 5 (https://storybook.js.org/blog/storybook-for-webpack-5/). There is a Github issue tracking all this (storybookjs/storybook#9216 (comment)).

I started the work in https://github.com/amundsen-io/amundsenfrontendlibrary/tree/WAITING-storybook-webpack-5-issue-fix, happy if anybody can pick it up and take it through the finish line.

Steps to Reproduce

1. Run npm start storybook
2. See the build breaking

[dorianj]

I worked on this for a while and just couldn't get it working, either... I eventually got stuck on an issue where core-js modules wouldn't load:

Did you mean 'keys.js'?
BREAKING CHANGE: The request '../../core-js/object/keys' failed to resolve only because it was resolved as fully specified
(probably because the origin is a '*.mjs' file or a '*.js' file where the package.json contains '"type": "module"').
The extension in the request is mandatory for it to be fully specified.

I wonder if there's anything in our normal build configuration that could be simplified/removed, which would then make this easier?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.