You can either use require to bypass typescript special import.

The rule is written @forward "<url>". It loads the module at the given URL just like @use, but it makes the public members of the loaded module available to users of your module as though they were defined directly in your module. Those members aren’t available in your module, though—if you want that, you’ll need to write a @use rule as well.

Now only the defined subpath in "exports" can be imported by a consumer:

Even though it works much like a function, import() is an operator

The module specifier is always fixed. That is, you can’t change what you import depending on a condition. And you can’t assemble a specifier dynamically.

There is a new specification which is called a dynamic import for ES modules.