Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug in bun install if same package in dependencies and devDependencies and trying to install same package again. #9374

Open
solenopsys opened this issue Mar 12, 2024 · 1 comment
Assignees
Labels
bug Something isn't working crash An issue that could cause a crash npm Something that relates to the npm-compatible client

Comments

@solenopsys
Copy link

What version of Bun is running?

1.0.30+1424a196f

What platform is your computer?

wsl 64

What steps can reproduce the bug?

package.json

{
  "name": "api",
  "module": "index.ts",
  "type": "module",
  "dependencies": {
    "@maverick-js/signals": "maverick-js/signals"
  },
  "devDependencies": {
    "@maverick-js/signals": "maverick-js/signals",
    "@types/bun": "latest"
  },
  "peerDependencies": {
    "typescript": "^5.0.0"
  }
}

bun i
bun i maverick-js/signals

What is the expected behavior?

No error or good error message

What do you see instead?

bun i maverick-js/signals
Segmentation fault

Additional information

No response

@solenopsys solenopsys added the bug Something isn't working label Mar 12, 2024
@Electroid
Copy link
Contributor

Output:

❯ bun install
bun install v1.0.30 (4b0eb471)
9 |     "@maverick-js/signals": "maverick-js/signals",
        ^
warn: Duplicate dependency: "@maverick-js/signals" specified in package.json
   at /Users/ashcon/Desktop/code/bun/test/testing/package.json:9:5

6 |     "@maverick-js/signals": "maverick-js/signals"
                                ^
note: "@maverick-js/signals" originally specified here
   at /Users/ashcon/Desktop/code/bun/test/testing/package.json:6:29

Checked 7 installs across 8 packages (no changes) [7.00ms]
❯ bun i maverick-js/signals
bun add v1.0.30 (4b0eb471)
fish: Job 1, 'bun i maverick-js/signals' terminated by signal SIGSEGV (Address boundary error)

@Electroid Electroid added crash An issue that could cause a crash npm Something that relates to the npm-compatible client labels Mar 12, 2024
@dylan-conway dylan-conway self-assigned this Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working crash An issue that could cause a crash npm Something that relates to the npm-compatible client
Projects
None yet
Development

No branches or pull requests

3 participants