Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/babel/babel-bridge
A placeholder package that bridges babel-core to @babel/core.
https://github.com/babel/babel-bridge
Last synced: 4 months ago
JSON representation
A placeholder package that bridges babel-core to @babel/core.
- Host: GitHub
- URL: https://github.com/babel/babel-bridge
- Owner: babel
- Created: 2017-11-10T05:19:14.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2018-08-25T22:55:16.000Z (over 6 years ago)
- Last Synced: 2024-04-14T02:34:15.138Z (10 months ago)
- Language: JavaScript
- Size: 3.91 KB
- Stars: 94
- Watchers: 12
- Forks: 12
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
## babel-bridge
This repo holds what we're calling a "bridge" package that is meant to ease the
transition for libraries that use "babel-core" as a peer dependency for Babel 6.The issue with Babel 7's transition to scopes is that if a package depends on
Babel 6, they may want to add support for Babel 7 alongside. Because Babel 7
will be released as `@babel/core` instead of `babel-core`, maintainers have
no way to do that transition without making a breaking change. e.g.```js
peerDependencies: {
"babel-core": "6.x"
}
```
cannot change to```js
peerDependencies: {
"@babel/core": "6.x"
}
```without it being a breaking change.
### Solution
To address this, we're releasing this bridge package, to allow users to do
```js
peerDependencies: {
"babel-core": "6.x || ^7.0.0-bridge.0"
}
```then where users of this package would originally have done
```sh
npm i some-package babel-core
```to install Babel 6, they could now do
```sh
npm i some-package babel-core@^7.0.0-bridge.0 @babel/core
```to install the bridge package, and install Babel 7's core.