Babel Runtime and corejs conflicts with babel 7+ versions

[gaetan-puleo]

Hello I have @babel/runtime installed as a dev dependency and in react-virtualized I can see that babel-runtime is used as a normal dependency.

I have a conflict between my version and yours.

[gunn4r]

Curious why you closed this @gaetan-puleo. I am trying to upgrade my repo to latest babel 7.4.x using corejs 3 and it seems react-virtualized version of babel-runtime is causing issues for me. Did you find a solution that worked well?

[gaetan-puleo]

@gunn4r I reopen it.

I fixed this issue by installing core-js as peer dependencies in my package.json

  "peerDependencies": {
    "core-js": "2.6.5"
  }

[csvan]

We are having issues with this as well when it comes to upgrading to corejs 3 - it inevitably breaks react-virtualized.

Babel 6 has been obsolete for a long time now. It would benefit this project and community at large if an upgrade was made.

[csvan]

@gunn4r I reopen it.

I fixed this issue by installing core-js as peer dependencies in my package.json

  "peerDependencies": {
    "core-js": "2.6.5"
  }

Sadly that is not a solution. Core-js 2 is deprecated and tightly bound to the old way of doing things in Babel 6. People using Babel 7.4+ and core-js 3 will not be able to integrate react-virtualized due to it.

[gaetan-puleo]

@gunn4r I reopen it.
I fixed this issue by installing core-js as peer dependencies in my package.json

  "peerDependencies": {
    "core-js": "2.6.5"
  }

Sadly that is not a solution. Core-js 2 is deprecated and tightly bound to the old way of doing things in Babel 6. People using Babel 7.4+ and core-js 3 will not be able to integrate react-virtualized due to it.

Yes I know, I think the contributors need to update the babel version and corejs.

Maybe I can help if needed.

I will try to do a PR this week end if I have the time to do it.

[jonasantonelli]

I had the same problem with the latest version of core-js@3.1.4
But it worked when I downgraded to version core-js@2.6.5

[jseminck]

Is there any way to have a build of react-virtualized without core-js included?

[betalb]

The common approach seems to be to ship esnext version of code. In case of react-virtualized original source can be used with flow annotations removed (if any)

End consumer will have to do final transpilation and use any version of babel runtime it needs

[bvaughn]

Version 9.22.4 has been published with peer dependencies updated to include React 17 and 18. (No other changes from 9.22.3)

https://github.com/bvaughn/react-virtualized/releases/tag/v9.22.4