babel-core@^7.0.0-0 should be babel-core@^7.0.0-bridge.0

[quisido]

The package name is incorrect in this documentation, as well as in the jest documentation.

There is no package tagged 7.0.0-0, and the 7.0.0-beta packages are incompatible. Installing 7.0.0-0 will simply prompt the user for which package they want (at least in yarn), and bridge.0 is the only valid package for this use case.

[loganfsmyth]

The package name is incorrect

What name, and which documentation?

There is no package tagged 7.0.0-0.

^7.0.0-0 is a semver version range that includes babel-core@7.0.0-bridge.0 as the most recent version.

[quisido]

My PR updates the documentation in question.
The semvar does not accurately find the bridge package.
I ran into this while trying to install jest with Babel 7.

I incorrectly chose a beta version thinking that any 7.0.0 would work. They do not work. When I chose bridge.0, however, the problem was resolved. More accurately, yarn add --dev babel-core@^7.0.0-bridge.0 finds the package and installs it correctly.

[loganfsmyth]

Hmm, that seems like a Yarn bug. That's frustrating.

[loganfsmyth]

Actually I guess bug isn't the right descriptor. Just an unfortunate side-effect of their behavior of displaying options.

[quisido]

Is this PR not an accurate fix?

As mentioned, the 7.0.0-beta# builds do not fix this issues that -bridge.0 does, so it seems like the semvar should include bridge.

[stern-shawn]

+1 for accepting the update.

The team I'm working on is a stickler for having exact versions in package.json instead of semver ranges, and the only non-breaking way of listing the package version (at least with Yarn, untested with npm) is "babel-core": "7.0.0-bridge.0".

[quisido]

This has been open for a while, with a PR as well. Any news on it being merged? @loganfsmyth @hulkish

[tricoder42]

This seems to be yarn issue. I'm using 1.9.2 and it works fine:

$ yarn add --dev babel-core@^7.0.0-0   
                                                                                                                                   
yarn add v1.9.2
info No lockfile found.
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning " > babel-core@7.0.0-bridge.0" has unmet peer dependency "@babel/core@^7.0.0-0".
[4/4] 📃  Building fresh packages...
success Saved lockfile.
success Saved 1 new dependency.
info Direct dependencies
└─ babel-core@7.0.0-bridge.0
info All dependencies
└─ babel-core@7.0.0-bridge.0
   Done in 0.58s.

This warning is weird, though:

warning " > babel-core@7.0.0-bridge.0" has unmet peer dependency "@babel/core@^7.0.0-0".

[quisido]

The Jest devs believe it to be a Windows issue. Not sure the cause, but it's an issue nonetheless. I don't see a benefit of leaving it as-is.

[tricoder42]

I'm on Mac. I have no problem installing package, but I can't get rid of warning. I'm just reporting how it works for me. I never use prereleases with semver so I don't know how the version range works in this case.