Cannot resolve module 'avoriaz' running the latest version (2.6.3)
See original GitHub issueI have been unit testing using Avoriaz module since I have started Vue testing, and thanks for having a nice library!
However, when I updated the module to the latest version, the Module not found: Error: Cannot resolve module 'avoriaz
error message occurs in every spec file. ( tried in both windows and linux), and there issomebody else also encountering the same issue.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Module not found: Error: Can't resolve 'avoriaz' - Stack Overflow
I have been using Avoriaz for a while, and also have encountered the same issue since the latest update since yesterday.
Read more >[Solved]-Module not found: Error: Can't resolve 'avoriaz'-Vue.js
author of avoriaz here. This was a bug with avoriaz 2.6.3, it's fixed in 2.6.5. The problem was I switched the way the...
Read more >vue/CHANGELOG.md at main · vuejs/vue - GitHub
Note that some APIs exported by the plugin, e.g. createApp , are not ported in 2.7. Update eslint-plugin-vue to latest version (9+) if...
Read more >cannot read properties of undefined (reading 'fallback')
Strict. Open links in a new tab ... Run next info (available from version 12.0.8 and up) ... in the "exports" field module...
Read more >Untitled
Vat 69 1 litre price in kolkata, Aus inv xi v england xi at sydney, ... Match grade 9mm 1911 barrel, Running old...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
±- avoriaz@2.6.5 installed. Big thumbs up for prompt fix! 👍 👍 👍
Hi @Dobbychen , yes I changed the way the module was exported. I tested it and thought it was working - but it’s not.
I’m going to revert to the previous build for v2.6.5, and release the changed export system in a major version.
I’ll update when I’ve reverted.