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

Wrong package.json workspace: prefix behavior #2938

Open
iam-medvedev opened this issue May 18, 2023 · 1 comment
Open

Wrong package.json workspace: prefix behavior #2938

iam-medvedev opened this issue May 18, 2023 · 1 comment
Labels
bug Something isn't working npm Something that relates to the npm-compatible client

Comments

@iam-medvedev
Copy link

What version of Bun is running?

0.6.2

What platform is your computer?

Darwin 22.3.0 arm64 arm

What steps can reproduce the bug?

Bun cannot install linked packages with the yarn workspace prefix.

package.json:

{
  "name": "@scope/package",
  "workspaces": ["demo"]
}

demo/package.json:

{
  "name": "demo",
  "private": true,
  "dependencies": {
    "@scope/package": "workspace:^"
  }
}

bun install gives the following error:

➜ bun install
bun install v0.6.2 (8d90d795)


error: package "@scope/package" is not linked

To install a linked package:
   bun link my-pkg-name-from-package-json

Tip: the package name is from package.json, which can differ from the folder name.

bun link @scope/package also gives the same error.

What is the expected behavior?

No response

What do you see instead?

No response

Additional information

No response

@iam-medvedev iam-medvedev added the bug Something isn't working label May 18, 2023
@Electroid Electroid added the npm Something that relates to the npm-compatible client label May 18, 2023
@Electroid
Copy link
Contributor

Using Bun v1.0.7, it now shows a different error.

❯ bun install
bun install v1.0.7 (6a2768f2)

error: workspace dependency "@scope/package" not found

Searched in "./demo/^"

Workspace documentation: https://bun.sh/docs/install/workspaces

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working npm Something that relates to the npm-compatible client
Projects
None yet
Development

No branches or pull requests

2 participants