Can't `yarn start` the project after `yarn upgrade` (Module not found: Can't resolve '@babel/runtime/helpers/builtin/extends' in '/Users/alberto.iglesias/Coding/iteisa/projects/cam/node_modules/yup/lib')

Hi,

I have a project created with create-react-app that is using yup. Today I have to run a yarn upgrade, and after that I can’t start the project. I get this error:

Module not found: Can’t resolve ‘@babel/runtime/helpers/builtin/extends’ in ‘/Users/alberto.iglesias/Coding/iteisa/projects/cam/node_modules/yup/lib’

Watching other issues, I’ve seen the babel beta.56 directory problem, so I’ve finally forced to add the babel beta.55 version, and is starting again. I think is valid as a temporary patch, but maybe there’s other packages installed by react-scripts that depends of beta.56, so I’m not sure if it’s going to generate other problems.

[klimashkin]

If you use webpack, you can add an alias until yup is updated

resolve: {
  ...
  alias: {
    '@babel/runtime/helpers/builtin': path.resolve('./node_modules/@babel/runtime/helpers'),
    ...

[ctrlplusb]

This babel problem is giving me a world of pain. It’s affected a bunch of libs that I am using. I understand babel v7 is in beta, and breaking changes can be expected between versions, but it’s a pain when transitive dependencies cause your apps to fail. I’ve been trying to wrap my head around the babel v6 -> v7 movement, and why so many lib authors have moved so quickly onto depending on v7.

Can confirm that forcing an install of previous version of @babel/runtime sorts the problem.