npm ERR! code EUNSUPPORTEDPROTOCOL when using yarn's "workspace:"

See original GitHub issue

I am using yarn workspaces, and in order to depend one package to another in my monorepo I am using yarn’s workspace protocol (https://yarnpkg.com/features/workspaces#publishing-workspaces) However when trying to run multi-semantic-release it errors with the following:

npm ERR! code EUNSUPPORTEDPROTOCOL
npm ERR! Unsupported URL Type "workspace:": workspace:packages/dashboard

Reference: https://github.com/taskforcesh/nandu/runs/8274785071?check_suite_focus=true#step:5:91

Issue Analytics

State:
Created a year ago
Comments:7

Top GitHub Comments

1reaction

manastcommented, Sep 12, 2022

So last three days I spent trying to make the release to no avail… tried everything I could came up with. In the last iteration I changed to pnpm instead of yarn. Interestingly it works to make a dry releae locally, but not on github actions…

https://github.com/taskforcesh/nandu/actions/runs/3040480203/jobs/4896572401

By using custom semantic-release/npm with a never version of npm I manage to go a step further but then got stuck with another error impossible to understand: npm ERR! Cannot read properties of null (reading 'matches')\n"

https://github.com/taskforcesh/nandu/actions/runs/3040464168/jobs/4896538148

I do not expect to get any help at this point, but certainly if you read this and are considering to use monorepos and semantic-release, you may also spend several days like I did to no avail…

0reactions

antongolubcommented, Sep 18, 2022

@aarne,

Thanks for the digging. We use yarn for our monorepos, so we have never faced with this kind of npm features. Could you pls update the readme.md troubleshooting section?

UPD I forgot that there is already such a mention. )))

npm v8.5+: npm ERR! notarget No matching version found for… When releasing a monorepo you may get a npm ERR! code ETARGET error. This is caused by npm version creating a reify update on packages with future dependency versions MSR has not updated yet. The simplest work around is to set workspaces-update to false either in your .npmrc or manually by running npm config set workspaces-update false