-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
Description
(Self-assigning as I am happy to take this on)
Currently, we’re using TypeScript’s paths option to handle module imports (which, until recently, was enforced by our linter).
While this setup has worked, it’s created several ongoing hurdles:
• Packages can't import modules with the same selector
• Our test runner needs a TypeScript transpiler that supports these aliases, limiting our ability to adopt faster alternatives
• Extra overhead in maintaining consistency between tsconfig.json in various places
To simplify things, I propose we move to Node.js native import aliases. This would involve changing our current @ prefix to something like #, following the Node convention.
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
✅ Done