René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Relax package.json#imports prefix","articleBody":"### What is the problem this feature will solve?\r\n\r\nTools such as rspack, bun, typescript, remix, and turbo are all looking at using tsconfig.json#compilerOptions.paths . This is in part due to constraints on package.json#imports and it lacking the ability to fully alias the entire import space. These also seem to have differing constraints and some are doing something outside the standard TS behavior on purpose.\r\n\r\n### What is the feature you are proposing to solve the problem?\r\n\r\nThe `package.json#imports` field seems sufficient from reading some twitter threads involving a few maintainers from remix or rspack except for the prefix `#` constraint. I propose getting feedback from these tools on removing the constraint if that would be sufficient for their users’ general needs. If it is sufficient we could encourage people to use a single way of doing this allowing tooling to avoid divergence and interop woes.\r\n\r\nThis would not cover global aliasing which already can be covered with policy redirects but likely is not desirable/sufficient for some subset of users. My hope is that subset is small enough to avoid the issue blocking this entirely.\r\n\r\n### What alternatives have you considered?\r\n\r\nSupporting tsconfig.json in a limited subset to alleviate the user needs.\r\n\r\ncc @nodejs/loaders @nodejs/modules ","author":{"url":"https://github.com/bmeck","@type":"Person","name":"bmeck"},"datePublished":"2023-08-15T14:53:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":35},"url":"https://github.com/49182/node/issues/49182"}