-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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] Resolver does not work with alias without range #1816
Labels
Comments
This issue reproduces on master:
|
Ran into this same issue while installing TailwindCSS with Yarn 2 tailwindlabs/tailwindcss#3432
Thanks for the workaround, @ikatyang On Yarn 2.4.0 after specifying the version tag, tailwindCSS works with yarn 2 🙇 |
1 task
Closed
1 task
1 task
This was referenced Nov 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
Resolver does not work with alias without range, alias should work the same way as normal dependencies, i.e.,
yarn add typescript
will be resolved as"typescript": "^X.Y.Z"
, so thatyarn add alias@npm:typescript
should be resolved as"alias": "npm:typescript@^X.Y.Z"
To Reproduce
unscoped:
scoped:
Environment
Additional context
npm install
yarn add alias@npm:typescript@latest
, which brings up another issue:yarn add
docs, "Yarn will resolve this tag to a semver version and use that in the resulting package.json entry (meaning thatyarn add foo@latest
will have exactly the same effect asyarn add foo
."yarn add typescript
is currently resolved as"typescript": "^X.Y.Z"
butyarn add typrscript@latest
is currently resolved as"typescript": "latest"
, which is not consistent with the docs, andyarn add alias@npm:typescript@latest
should be resolved as"alias": "npm:typescript@^X.Y.Z"
, but it actually gets resolved as"alias": "npm:typescript@latest"
The text was updated successfully, but these errors were encountered: