1.0.31 bun install fails to resolve packages in devDependencies about bun HOT 5 CLOSED

Not able to reproduce on macOS or an EC2 VM. Does the gitlab workflow happen to be public?

from bun.

Here is a repo reproducing the issue : https://github.com/Leni-Vienne/bun_dev_dependencies_issue
I've tried to narrow it down more but it gets quite unpredictable with the bun.lockb file in the way and I had to add some production dependencies to reproduce the bug

from bun.

Confirming I'm able to reproduce the issue locally.

Minimal reproduction:

Put this into package.json:

{
  "devDependencies": {
    "underscore": "1.9.1",
    "lodash": "4.17.21"
  }
}

Then run bun install.

It installs successfully:

❯ bun install
bun install v1.0.32 (7c9f0763)

 + lodash@4.17.21
 + underscore@1.9.1 (v1.13.6 available)

 2 packages installed [183.00ms]

Then, manually edit your package.json to look like this:

{
  "devDependencies": {
    "underscore": "1.9.1",
    "lodash": "4.17.21"
  },
  "dependencies": {
    "lodash": "4.17.21"
  }
}

Note the "dependencies" there.

Then run bun install --production:

❯ bun install --production
bun install v1.0.32 (7c9f0763)
4 |     "lodash": "4.17.21"
        ^
warn: Duplicate dependency: "lodash" specified in package.json
   at /Users/jarred/Desktop/reproo/package.json:4:5

7 |     "lodash": "4.17.21"
                  ^
note: "lodash" originally specified here
   at /Users/jarred/Desktop/reproo/package.json:7:15

Checked 1 install across 3 packages (no changes) [2.00ms]

It has a warning but overall installs successfully.

Now run bun install, without the --production flag:

~/Desktop/reproo 
❯ bun install
bun install v1.0.32 (7c9f0763)
4 |     "lodash": "4.17.21"
        ^
warn: Duplicate dependency: "lodash" specified in package.json
   at /Users/jarred/Desktop/reproo/package.json:4:5

7 |     "lodash": "^4.17.21"
                  ^
note: "lodash" originally specified here
   at /Users/jarred/Desktop/reproo/package.json:7:15
error: lodash@4.17.21 failed to resolve
error: underscore@1.9.1 failed to resolve

It reports that devDependencies failed to resolve.

Part of the problem is when --production is in use, we should never save the lockfile to disk.

from bun.

@Leni-Vienne are you using bun install --production?

from bun.

Yes i am indeed, but not sure yet if it's strictly necessary for the error to occur. Take a look at my repo above your last comment, it might help

from bun.