Benoît Rouleau
Benoît Rouleau
Ok, got it @michaldudak. Closing this issue then, thank you for the explanation!
This would be super useful.
@atomiks – I finally got to test this and it's more than I could ask for, thank you so much! 🫶 Only issue is the docs don't specify the default:...
Potentially related: - https://github.com/vercel/next.js/issues/61715 - https://github.com/vercel/next.js/issues/63540
Ok so I believe this can be fixed by using the `.mjs` extension for the ESM exports, and making sure that all `import`s in ESM include the file's extension. Basically...
No @rolandjitsu, same issue.
@rolandjitsu – I did provide a CodeSandbox in my OP, but I just updated it to use the latest version. You can see that the error still occurs (at least...
Thanks for the workarounds @rolandjitsu, really appreciate you looking into this. For my use case though, I have a (private) component library that uses the main `Dropzone` component, and that...
I don't think it has to do with the fact that it's a JSX element, but rather that it's the default export, which sounds related to ESM vs CJS to...
This seems fixed in the latest version, I believe by https://github.com/react-dropzone/react-dropzone/commit/201687900724b45ec98d26cde3626a1c6687c9e1. Thank you!