Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken dynamic imports. #651

Closed
4 of 6 tasks
psznm opened this issue Sep 11, 2024 · 2 comments · May be fixed by nerdy-tech-com-gitub/ant-design#2 or Jekyle9444/docs#2
Closed
4 of 6 tasks

Broken dynamic imports. #651

psznm opened this issue Sep 11, 2024 · 2 comments · May be fixed by nerdy-tech-com-gitub/ant-design#2 or Jekyle9444/docs#2
Labels

Comments

@psznm
Copy link

psznm commented Sep 11, 2024

Acknowledgements

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

Minimal reproduction URL

https://github.com/psznm/tsx-dynamic-import-bug-repro

Problem & expected behavior (under 200 words)

As described in README of the repro repository. Dynamic imports seem to not respect relative paths and always resolve to the first loaded module with same "name" even if it is actually different modules in different directories.

Bugs are expected to be fixed by those affected by it

  • 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
@psznm psznm added bug Something isn't working pending triage labels Sep 11, 2024
@psznm psznm changed the title Broken dynamic imports. Broken imports. Sep 11, 2024
@psznm psznm changed the title Broken imports. Broken dynamic imports. Sep 11, 2024
@privatenumber
Copy link
Owner

Strange bug! Nice find, and thanks for the minimal reproduction

@privatenumber
Copy link
Owner

This issue is now resolved in v4.19.1.

If you're able to, your sponsorship would be very much appreciated.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
2 participants