`ERR_UNSUPPORTED_ESM_URL_SCHEME` when running tsx watch on windows and importing using `await import(path)`

TheDogHusky commented 1 month ago

Acknowledgements

[X] I read the documentation and searched existing issues to avoid duplicates
[X] I understand this is a bug tracker and anything other than a proven bug will be closed
[X] I understand this is a free project and relies on community contributions
[X] I read and understood the Contribution guide

Minimal reproduction URL

https://github.com/TheDogHusky/tsx-issue-import

Problem & expected behavior (under 200 words)

The README from the minimal reproduction repo should explain in enough details.

Bugs are expected to be fixed by those affected by it

[X] I'm interested in working on this issue

Compensating engineering work will speed up resolution and support the project

[ ] I'm willing to offer $10 for financial support

TheDogHusky commented 1 month ago

I precedently made an issue (https://github.com/privatenumber/tsx/issues/650) but couldn't figure out the cause of the error, now I figured it out, and am submitting an issue here.

mvarendorff commented 1 week ago

Probable dupe: https://github.com/privatenumber/tsx/issues/345

mvarendorff commented 1 week ago

If others stumble upon this - since the other issue is now closed and locked, I opened a PR in the repro of this issue with two approaches on how to fix this:

https://github.com/TheDogHusky/tsx-issue-import/pull/1

fwiw, this does not appear to be an issue with tsx but node (the same error shows when doing the same setup with node+js).

privatenumber / tsx