Suggestion

🔍 Search Terms

✅ Viability Checklist

My suggestion meets these guidelines:

• 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 feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion

Currently, ts treat import url as path, not url (remove search / hash and decodeURIComponent firstly).

Is it possible to support decodeURIComponent for import url, at least for "moduleResolution": "NodeNext" / "bundler", or url in format with scheme like http://example.com/%3F.js?version or file:./path%25, because that's the standard behaviour of Node.js / browser?

📃 Motivating Example

import './path%25.mjs';// actually expect './path%.mjs', not './path%25.mjs'

💻 Use Cases

import filename including \ % ? #.