Select content mapper at import level thanks to the with keyword #65404

🔍 Search Terms

content mappers

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Extensions filter are too limitative for content mappers. I think that we should be able to use with keyword when importing module to select the right content mapper.

📃 Motivating Example

For example, with this content mapper : https://github.com/nfroidure/json-schema-content-mapper I have to import .jsonchema files but what I would like to do is to import schemas by URLs and I cannot change their extension.

Something like:

import type Alert from "https://schemas.sourcemeta.com/nasa/gcn/v4.2.0/notices/core/alert.json" with { type: "jsonschema" };

would be cool.

💻 Use Cases

1. What do you want to use this for?
   To be able to use URLs to import modules since we cannot change extensions of it
2. What shortcomings exist with current approaches?
   Copy URL content locally with the right extension.
3. What workarounds are you using in the meantime?
   None atm, no real use since TS7.1 is still in beta, just experiments.