-
Notifications
You must be signed in to change notification settings - Fork 565
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
No default export (v2.5.1) #357
Comments
I suspect #301 might be the cause of this, but I am not sure. Can you share the minimal code needed to reproduce this? This includes bundler configuration and version information. Is there a specific version where this started breaking? |
I might have found the cause. A dependency used v2.3.2, while the project uses v2.5.1. |
Ok, sound like things work as expected in newer versions, so I will consider this resolved. |
Correct, caused a bit of a headache. But at least if someone runs into this issue, they'll know :) |
I don't know if this is a problem with my configuration only but I've made sure I'm running 2.5.1 via the yarn lockfile and manual check in node_modules. I'm using rollup (with only module support no commonjs) and i get this error message when i try to build, and it's pointing at the import of the classnames default export:
My rollup config (rollup.config.mjs)
Any ideas to what could cause this? Or if anything else is needed to reproduce this issue? My workaround for now is including a commonjs plugin for rollup and that solves the issue. But i feel like this is something others could encounter. This other issue #358 seems related. |
The latest version (v2.5.1) does not export the function classNames as default anymore.
TypeError: (0 , classnames__WEBPACK_IMPORTED_MODULE_1__.default) is not a function
It does seem to be fixed in the master, but there has not yet been a release created after this fix.
If you were planning on using named-exports, the docs need to be updated
The text was updated successfully, but these errors were encountered: