-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
fix(cli): use CliNodeResolver::resolve() for managed node_modules #23902
fix(cli): use CliNodeResolver::resolve() for managed node_modules #23902
Conversation
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.
Looks good once a test case is added.
assert_eq!( | ||
json!(diagnostics.all()), | ||
json!([ | ||
{ |
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.
Verified that this fails on main
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
Fixes #23895.
Fixes #23878.
This was a regression in #23764 caused by removing this code block: https://github.com/denoland/deno/pull/23764/files#diff-5edc220fbc0fc6aebb443d977875a955bcb1304beb56fefbebae42925824d49aL1111-L1121. I supposed this was handled by the
CliGraphResolver
. This patch ensuresCliNodeResolver::node_resolve()
is called inCliGraphResolver::resolve()
.Maybe this was broken inNot sure how to test this.deno check
as well but no errors are surfaced because it produces a bunch ofany
types.