-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
loading from node import throws error #3849
Comments
This is already fixed in our 2.0 beta releases - the latest is https:/reduxjs/redux-toolkit/releases/tag/v2.0.0-beta.4. Please try them out and let us know how they work! Also see:
FYI we're hoping to release 2.0 final within the next month or so, and there's only a couple of items left to finish up - see https:/reduxjs/redux-toolkit/milestone/8 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've been using this package for a while & it works great for us. we're currently looking at switching our projects build tasks in an attempt to get off of babel. Our old test script basically converted all of our import/export syntax back to commonjs before running our tests. Now that we're leaving those, we get errors consuming this package. here's a simplified example.
if i have this file
& i run
node index.mjs
, I get the following error:I can get around that by doing what the error message says but looking at your package.json file, you already have an esm version of the script prepared exposed thru the "module" field but that's not understood by node. Have you considered adding exports to the package.json file? That allows me to get around around this error if I update your package.json to expose your
dist/redux-toolkit.esm.js
thru the package.json exports field & switch it's extension to.mjs
.so:
The text was updated successfully, but these errors were encountered: