You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using tsx with execa, I see an error Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in ./node_modules/unicorn-magic/package.json (see reproducer)
To be honest, I am not sure if this is an issue of tsx or execa (or unicorn-magic). So please let me know, if I should report it to execa instead. 👍
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
The text was updated successfully, but these errors were encountered:
The problem is happening because the import gets converted to require under the hood, so it doesn't actually get the import condition. But you can just pass that in yourself:
tsx -C import ./file
bluwy
added a commit
to vitejs/vite-plugin-basic-ssl
that referenced
this issue
Nov 27, 2024
Acknowledgements
Minimal reproduction URL
https://github.com/ansf/tsx-execa
Problem & expected behavior (under 200 words)
When using tsx with execa, I see an error
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in ./node_modules/unicorn-magic/package.json
(see reproducer)To be honest, I am not sure if this is an issue of tsx or execa (or unicorn-magic). So please let me know, if I should report it to execa instead. 👍
Bugs are expected to be fixed by those affected by it
Compensating engineering work will speed up resolution and support the project
The text was updated successfully, but these errors were encountered: