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
We use this to hide the fact that these paths are in a /node_modules/ folder because tsc wasn't giving auto-import suggestions from them. Did this have a knockback effect on performance? Could we only apply this to direct dependencies? How does node/tsc give these suggestions?
The text was updated successfully, but these errors were encountered:
it's checking if the import is in the top level node_modules. For an npm style node_modules layout, this works fine (example below from a project at /home/node-modules-completion:
The reason the current workaround works is that we effectively force toNodeModules=undefined and toNodeModulesParent=undefined, which makes isImportablePath just always return true.
https://github.com/nayeemrmn/deno/blob/9dbb99a83cb599028aef662b23e13faf2df15297/cli/lsp/tsc.rs#L4315-L4317
We use this to hide the fact that these paths are in a
/node_modules/
folder because tsc wasn't giving auto-import suggestions from them. Did this have a knockback effect on performance? Could we only apply this to direct dependencies? How does node/tsc give these suggestions?The text was updated successfully, but these errors were encountered: