Why doesn't everyone know about this?
I came here because of a note on the Jest page, and have been going a little crazy. Please promote this solution!
It's only really useful for tooling that has a peerDependency on babel-core, but since the majority of tooling has a direct dependency, it's not necessarily useful in the general case. If there are other packages where it has that you run into though, I'd love to hear them though.
I am a team member of the Quasar Framework responsible at the moment for building a new mode for testing where babel and webpack collaborate to run unit-tests before the dev server is started up. Yesterday we moved to Webpack4 and Babel7 - and I was fielding lots of problems across the board. Today someone was trying to get Jest to work in their setup (currently [email protected]) - and we kept on running into the multiple namespacing issue of @babel/core and babel-core. This little module solved the problem.
Next on my list is convincing mocha-webpack to do the same thing, and if it won't, I am going to fork it and make a babel7 compliant version. I was hoping that babel-bridge would save me the trouble.
This isn't mentioned in Upgrade to Babel 7 page.
I found babel-bridge after I read React Native changelog.
If I don't use React Native or Jest, I might not found this bridge.
Please add this on official Babel website. Everyone should know it.
Years later, same thing. If it were'nt to some searches and some stack-overflow answers, I wouldn't know about babel-bridge.
Babel 7 was released more than two years ago, it's quite sad that some packages still expect Babel 6 and thus need babel-bridge :frowning_face:
Used by more than 3 million developers, Babel Bridge is my favorite two lines package ❤
Weekly downloads in npmjs.com

Searched npmjs.com for "babel-bridge" and was very confused when I found https://www.npmjs.com/package/babel-bridge
Could at least add a little clarity to the readme
