zioinfo-mail/app/node_modules/babel-core
DESKTOP-TKLFCPR\ython 11c670f2a0 refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포
- 37개 파일 IP → zioinfo.co.kr 치환 (소스/매뉴얼/설정/하네스)
- Manager DrConsole/NetworkConsole/CsapConsole 빌드 + /var/www/manager/ 배포
- 테스트: Manager HTTP 200, ITSM 신규 API 7개 전체 200

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-05-31 10:09:17 +09:00
..
index.js refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
package.json refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00
README.md refactor: 101.79.17.164 → zioinfo.co.kr 전체 도메인 변환 + Manager UI 배포 2026-05-31 10:09:17 +09:00

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.

peerDependencies: {
  "babel-core": "6.x"
}

cannot change to

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

peerDependencies: {
  "babel-core": "6.x | ^7.0.0-bridge"
}

then where users of this package would originally have done

npm i some-package babel-core

to install Babel 6, they could now do

npm i some-package babel-core@^7.0.0-bridge @babel/core

to install the bridge package, and install Babel 7's core.