Closed JeanJPNM closed 2 years ago
Hi @JeanJPNM,
Thanks for the PR. All the dependencies have been updated. Please let me know if this issue is solved when using Splitpanes 3.1.3 Please reopen if not solved. :) Cheers.
It still doesn't work, looking at the package.json, I see that the esm imports are using the old name of the es module.
Updating it like this should fix the problem:
{
- "module": "./dist/splitpanes.es.js",
+ "module": "./dist/splitpanes.mjs",
// ...
"exports": {
// ...
".": {
- "import": "./dist/splitpanes.es.js"
+ "import": "./dist/splitpanes.mjs"
}
}
}
Also I can't reopen this issue.
You're right, the .es.js should be there and it was changed to mjs with the latest updates. Now it should be fixed in version 3.1.4. Related to #179
The issue still persists, for vite to know that a javascript file is an es module it looks for a "type": "module"
in the package.json (if it has one it causes all files to be treated as modules) or the file needs to have a .mjs
extension to override the default cjs behavior.
Okay, I will serve it as an ES Module, I think it is time to move on anyway. :) Please try the version 3.1.5 and let me know.
It works now, thanks!
I was testing this package with vitepress 1.0.0-alpha.22 and vue 3.
The package works as expected in dev mode, but during build, vite will not be able to load it:
This is likely related to intlify/vue-i18n-next#1131