Migrate to babel@7.0.0-beta

[Hypnosphi]

Work summary

• move all apps to babel beta
• Use loadPartialConfig for custom babel configs resolution. Should fix Support for .babelrc.js #2582 Cannot find relative presets defined in .babelrc #2771 Storybook does not process .babelrc extends correctly #2610 babel config in package.json #754 Babelrc resolving to wrong location #2635 Disable loading custom .babelrc #2758

Who to contact

Me

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!

[osdevisnot]

It seems this is needed for CRA and getstorybook integration when react-scripts@2.0 is ready (referenced in facebook/create-react-app#3815). Currently, we run into incompatible versions for babel since react-scripts@2.0 is on Babel 7 and Storybook is on Babel 6.

[Hypnosphi]

You may try just adding your own babel-loader@8 in your custom webpack config (at least that worked for my own app)

[Hypnosphi]

move @babel/core to direct dependencies again

Ok looks like we can't do that. Actually we must declare all the peer dependencies of the server-side packages we use as our own. Imagine the following situation:

— We depend on A@2 which has a peer dependency on B@3
— We add a direct dependency on B@3 to satisfy that
— User app has a direct dependency on B@2 and doesn't have any dependency on A
— npm hoists A@2 to root node_modules, but leaves B@3 under @storybook/*/node_modules to avoid clashing with B@2
— inside A@2, import 'B' resolves to B@2 instead of the expected B@3, which leads to an error

webpack's resolve.alias can solve this issue for client-side dependencies but not for server-side ones