bun install resolving to wrong major version of beta packages

[thecrypticace]

What version of Bun is running?

1.0.2+37edd5a6e389265738e89265bcbdf2999cb81a49

What platform is your computer?

Darwin 22.6.0 arm64 arm

What steps can reproduce the bug?

The following package.json resolves to the wrong major version when installing via bun:

{
  "dependencies": {
    "@babel/types": "^7.0.0-beta.54"
  }
}

After installation it'll install 8.0.0-alpha.2 rather than 7.22.19. This also applies to any dependents because it's using 8.x to resolve dependencies.

Quick repro:

git clone https://github.com/thecrypticace/bun-install-issue
cd bun-install-issue
yarn install && grep 'version' yarn.lock
bun install --yarn && grep 'version' yarn.lock

What is the expected behavior?

I would expect bun to resolve the version(s) to 7.22.19 (or at least any 7.x version) rather than 8.x.

What do you see instead?

It resolves the package and its dependents to 8.x versions.

Additional information

I (manually) cleared the bun install cache and did installs using --force as well and the problem persisted so it doesn't appear that this is cache related.

[spiritledsoftware]

I'm also experiencing this

[mmacoveiciuc]

Same happening on Bun 1.0.4 for me with various packages, including packages from our private NPM repo. Installing a package pinned to a specific version and it fetches something from 2 years ago.

Any ideas?

[Jarred-Sumner]

@dylan-conway is working on this

[thecrypticace]

@Jarred-Sumner @dylan-conway I just built bun from source and it looks like this is still a problem — even in the test repo I provided above.

I suspect it's more related to this area of the semver handling which are currently commented out as I believe these aren't handled correctly yet:

bun/src/install/semver.zig

Lines 2277 to 2279 in 4a2e157

	// "1.0.0-rc.1",
	// "1.0.0-rc.2",
	// "1.0.0-rc.3",

[thecrypticace]

Fixed as of v1.0.6