-
Notifications
You must be signed in to change notification settings - Fork 18
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
ESM exports issue in 3.7.0 #60
Comments
Thanks for the report @toddheslin! I bet you're right about that build process overhaul. I'll take a look at this and try to get a new version cut soon. |
@toddheslin playing around with some config changes. Could you try pointing your package.json to |
Yep, that works perfectly. Thanks @derrickreimer you've graduated in the world of pain known as cjs/esm for library authors 😂 |
Great! 😅 version 3.7.1 released. |
👋 Hey @derrickreimer thanks for your work on this!
I upgraded to
3.7.0
and had some issues along the lines of:Unfortunately, I haven't been able to figure out exactly why but it's likely due to cd3d70b
For now I've rolled back to

3.6.0
to keep on moving forward. Given there was no one else who reported this, and a good chunk of people are still using3.6.0
, I thought it would be good to stub an issue for anyone else to contribute their findings:I'm using this package in a Remix app using Vite for build, spitting out ESM. The package.json is set
type=module
and I've confirmed that it's outputting ESM. For some reason it looks like it's resolving to thecjs
version instead ofesm
.The text was updated successfully, but these errors were encountered: