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

[turborepo] ERR_PNPM_CANNOT_RESOLVE_WORKSPACE_PROTOCOL #5031

Closed
vaynevayne opened this issue May 19, 2023 · 2 comments · Fixed by #5884
Closed

[turborepo] ERR_PNPM_CANNOT_RESOLVE_WORKSPACE_PROTOCOL #5031

vaynevayne opened this issue May 19, 2023 · 2 comments · Fixed by #5884
Labels
kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage

Comments

@vaynevayne
Copy link

What version of Turborepo are you using?

latest

What package manager are you using / does the bug impact?

pnpm

What operating system are you using?

Mac

Describe the Bug

pnpm run release localily
ERR_PNPM_CANNOT_RESOLVE_WORKSPACE_PROTOCOL
image

Expected Behavior

work well

To Reproduce

download example/design-system
pnpm i
git commit -m 'first'
pnpm changeset -> all none none
pnpm install
pnpm release
get error

Reproduction Repo

No response

@vaynevayne vaynevayne added area: turborepo kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage labels May 19, 2023
@mehulkar
Copy link
Contributor

Hey @vaynevayne, couple things:

  • If you're starting from one of our examples, you'll have to rename the package names to something other than their defaults to be able to publish. The example repos we provide will not be publishable out of the box
  • I tried to follow your steps and got an error on publish (which is expected, since publishing shouldn't work out of box), but I got the expected 404 error on publishing @acme/core. The ERR_PNPM_CANNOT_RESOLVE_WORKSPACE_PROTOCOL error you reference seems different. What version of pnpm are you using? Is this what you're trying to solve with Update package.json  #5048?

@vaynevayne
Copy link
Author

@mehulkar hello

I released the package for the first time using changetset and monorepo+ pnpm
I have a lot of comments on my operation, and now I can't remember the specific reason. The other pr is because when I want to publish soul-eslint-config to npm, it prevents me from releasing it, so I just change it to *.
I have changed the pnpm version several times, from pnpm 7 to 8

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working needs: triage New issues get this label. Remove it after triage
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants