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
This issue appears to be related to both #28662 and #29098.
Given an import map entry like:
{
"imports": {
"$src/": "./src/"
}
}
And a folder structure such as:
src/
├── a.ts
└── b.ts
Inside a.ts, the editor currently only suggests the relative import path ./b.ts when attempting to import b.ts. It does not suggest the import map alias $src/b.ts.
This behavior differs from previous versions (prior to Deno 2.3.x), where the alias-based path was also suggested. I believe we should consider either restoring this behavior or providing a configuration option to prioritize import map aliases over relative paths in import suggestions.
Let me know if there's any more context I can provide!
The text was updated successfully, but these errors were encountered:
Version: Deno 2.3.3
This issue appears to be related to both #28662 and #29098.
Given an import map entry like:
And a folder structure such as:
Inside a.ts, the editor currently only suggests the relative import path ./b.ts when attempting to import b.ts. It does not suggest the import map alias $src/b.ts.
This behavior differs from previous versions (prior to Deno 2.3.x), where the alias-based path was also suggested. I believe we should consider either restoring this behavior or providing a configuration option to prioritize import map aliases over relative paths in import suggestions.
Let me know if there's any more context I can provide!
The text was updated successfully, but these errors were encountered: