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
Should source maps somehow help us represent the module specifiers used to refer to things, which may indirectly reference the original source via import maps or other mechanisms? How can we differentiate between multiple candidate specifiers when they point to the same source? (This question came up at the Igalia Web Engines Hackfest.)
The text was updated successfully, but these errors were encountered:
This sounds somewhat related to challenges with VS Code's "Go To Implementation". In the IDE when not debugging, and you right-click on an imported library method, and choose "Go To Implementation", where should the IDE navigate the user? (This gets even more complicated when libraries have a CJS, ESM, and UMD entry points in addition to import maps.)
Should source maps somehow help us represent the module specifiers used to refer to things, which may indirectly reference the original source via import maps or other mechanisms? How can we differentiate between multiple candidate specifiers when they point to the same source? (This question came up at the Igalia Web Engines Hackfest.)
The text was updated successfully, but these errors were encountered: