suggestion: simplify internal module specifiers #24294
Labels
deno_core
Changes in "deno_core" crate are needed
suggestion
suggestions for new features (yet to be agreed)
The internal import map for this codebase is defined in
tools/core_import_map.json
. Currently, each import corresponds to an individual script. This means a new entry is needed for every new script, and when one entry is missing, VSCode IntelliSense doesn't work for symbols from that script.I suggest replacing these single-script imports with directory imports and changing the prefix used in internal module specifiers. This change would automatically cover almost all internal imports with near-zero maintenance. @bartlomieju told me this would require considerable changes to this repo and
deno_core
code and, therefore, likely best done after Deno 2.Please excuse me if I've overlooked some obvious drawbacks to this approach. I have little context on why internal module specifiers were done this way in the first place.
Currently
deno/tools/core_import_map.json
Lines 55 to 60 in 88e3f46
deno/ext/node/polyfills/_brotli.js
Lines 29 to 32 in 88e3f46
Suggestion
The text was updated successfully, but these errors were encountered: