-
-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Cannot find module 'entities/dist/decode.js' from 'node_modules/@vue/compiler-core/dist/compiler-core.cjs.js' #11603
Comments
It was updated in ea190f2 and the paths are updated accordingly. The file also can be correctly resolved from |
Thanks for your response. Since I didn't declare the entities in package.json, and Vue is internally using vue/compiler-core which relies on entities, I'm unable to update the path for these dependencies. As a temporary fix, I've set the Vue version to 3.4.27 without the caret (^) to prevent automatic updates. I'm looking for a permanent solution to this issue. Thank you. |
I have the same issue not using Jest but Mocha. |
Did you try the below solution |
No, did not try this but I am sure it works – I am getting the error in a MR for a dependency upgrade, the error is not in our production branch. |
Vue version
3.4.37
Link to minimal reproduction
https://github.com/yashjainyj/vue_Module_Issue
Steps to reproduce
clone my repo
and run below command
yarn run test:unit
What is expected?
all jest test case should be resolved and run successfully
What is actually happening?
My Jest unit tests are failing
It appears that the vue package relies on an external dependency called entities. In the entities package, the decode.js file is missing from the dist folder.
However, the entities package has been updated and now contains two sub-folders, commonjs and esm, within the dist folder,
where decode.js can be found. The https://github.com/VUE package has not yet updated its path to reflect these changes.
System Info
No response
Any additional comments?
No response
The text was updated successfully, but these errors were encountered: