Skip to content

Conversation

@fardjad
Copy link
Contributor

@fardjad fardjad commented May 5, 2024

This PR attempts to fix the issue described here: #543

@DASPRiD
Copy link

DASPRiD commented May 5, 2024

Could this also be addressing #541?

@privatenumber
Copy link
Owner

@fardjad Would you mind adding a test?

@fardjad
Copy link
Contributor Author

fardjad commented May 5, 2024

@privatenumber Of course! I updated my PR.

I wasn't sure where the best place to add the test would be. I decided to put it under the register / unregister group as it affects the module resolution after the hook is registered. Do you think the approach and the location for adding the test make sense, or do you have something else in mind?

@privatenumber
Copy link
Owner

That works, but I consolidated it into the smoke test—previously, our tests would take super long from spawning so many processes.

Thanks for your contribution!

@privatenumber privatenumber changed the title fix(tsImport): resolve specifiers that are absolute paths fix(tsImport): resolve absolute paths May 6, 2024
@privatenumber privatenumber changed the title fix(tsImport): resolve absolute paths fix(esm): resolve absolute paths May 6, 2024
@privatenumber privatenumber merged commit 3a0ea18 into privatenumber:master May 6, 2024
@privatenumber
Copy link
Owner

🎉 This issue has been resolved in v4.9.2

If you appreciate this project, please consider supporting this project by sponsoring ❤️ 🙏

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants