v12.0.0 seems to have the wrong binary version
- Dominant language
- JavaScript
- Stars
- 2.1k
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
I started seeing odd problems when I tried upgrading from v11.0.0 to v12.0.0.
For example the binary version is as expected when pulling in c8 v11.0.0:
```
$ rm -rf node_modules
$ cat package.json | jq '.devDependencies.c8'
"^11.0.0"
$ npm install
$ npm list c8
xxxx@1.0.0 /x/x/xxxx
└── c8@11.0.0
$./node_modules/.bin/c8 --version
11.0.0
```
All of this looks good. But if update the package.json to pull in c8 v12.0.0, and repeat the above steps, I somehow end up pulling in version 1.0.0 of the binary:
```
$ rm -rf node_modules
$ cat package.json | jq '.devDependencies.c8'
"^12.0.0"
$ npm install
$ npm list c8
xxxx@1.0.0 /x/x/xxxx
└── c8@12.0.0
./node_modules/.bin/c8 --version
1.0.0
```
Contributor guide
Research direction
Reproduce the report using package.json, npm install, npm list c8, and ./node_modules/.bin/c8 --version for c8 v11.0.0 and v12.0.0. Inspect how the v12.0.0 package exposes its installed binary; done means the v12.0.0 command reports 12.0.0 rather than 1.0.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100