You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
Describe the bug
When installing @slidev/cli, I encountered the following error.
$ npm i @slidev/cli
npm error code ETARGET
npm error notarget No matching version found for @shikijs/twoslash@^3.1.2.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
I think that removing @shikijs/twoslash from pnpm-workspace.yaml would be fix this issue(, but I'm not sure that it is the correct patch for this because I don't understand why packages/twoslash/package.json have a dependency to @shikijs/twoslash).
Reproduction
npm init -y && npm i @slidev/cli
Contributes
I am willing to submit a PR to fix this issue
I am willing to submit a PR with failing tests
The text was updated successfully, but these errors were encountered:
Validations
Describe the bug
When installing
@slidev/cli
, I encountered the following error.I looked into this error, and I (maybe) found that
shiki
has incorrect version specification for@shikijs/twoslash
.https://github.com/shikijs/shiki/blob/main/pnpm-workspace.yaml#L22
@shikijs/twoslash
doesn't have that version (3.1.2
), and this issue seemed to be introduced when renamingshiki-twoslash
to@shikijs/twoslash
. I believe this was expressed when the pnpm catalog was introduced.a04b3e2#diff-c82d37826e7a067e8c3ec9b11b7a2e91fce9cdda0f3298f8cfcd6bf3ab5c0a70R64
I think that removing
@shikijs/twoslash
frompnpm-workspace.yaml
would be fix this issue(, but I'm not sure that it is the correct patch for this because I don't understand whypackages/twoslash/package.json
have a dependency to@shikijs/twoslash
).Reproduction
npm init -y && npm i @slidev/cli
Contributes
The text was updated successfully, but these errors were encountered: