-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
fix(workspace): support resolving bare specifiers to npm pkgs within a workspace #24611
fix(workspace): support resolving bare specifiers to npm pkgs within a workspace #24611
Conversation
@@ -1,9 +1,7 @@ | |||
import * as a1 from "@denotest/a"; | |||
import * as a2 from "npm:@denotest/a@1"; | |||
import * as a3 from "npm:@denotest/a@workspace"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The LSP doesn't support npm workspaces yet, so I did not implement this there (I'll add this PR as something to consider for #24505)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…a workspace (#24611) This makes bare specifiers for npm packages work when inside a workspace, which emulates the same behaviour as when there's a node_modules directory. The bare specifier can be overwritten by specifying an import map entry or package.json dependency entry. * denoland/deno_config#88 Closes #24605
This makes bare specifiers for npm packages work when inside a workspace, which emulates the same behaviour as when there's a node_modules directory. The bare specifier can be overwritten by specifying an import map entry or package.json dependency entry.
Closes #24605