Module not found: Error: Can't resolve 'Vue'
See original GitHub issueERROR in ./~/vue-loading-overlay/dist/vue-loading.min.js
Module not found: Error: Can't resolve 'Vue' in ./node_modules/vue-loading-overlay/dist'
@ ./~/vue-loading-overlay/dist/vue-loading.min.js 1:82-96
@ ./vue-source/src/main.js
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Module not found: Error: Can't resolve vue, path not correct
I have my webpack.config.js and node_modules in a subfolder. If I trying to execute: npm run build I get the error: ERROR in...
Read more >Can't resolve 'vue' - Get Help
Webpack (which you are trying to run via npm run dev ) is trying to compile your index.js entry point. As such, it...
Read more >Module not found: Error: Can't resolve ' Vuejs - Laracasts
Hi... In the router section, we want to route the pages through Nested Routes, but there is a problem, it does not recognize...
Read more >Module 'vue' can't resolved in app.js · Issue #2717 - GitHub
My webpack.mix.js look like this: let mix = require('laravel-mix'), path = require('path'); mix.alias({ 'vue$': 'vue/dist/vue.esm.js', '@': path ...
Read more >Can't resolve 'vue-class-component' - Syncfusion
A colleague of mine created this issue: https://github.com/syncfusion/ej2-vue-ui-components/issues/86.
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 FreeTop 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
Top GitHub Comments
@mazurva What’s in your
package.json
? Check to make sure thatvue
is in your list of dependencies. vue-loading-overlay makes the assumption that the consuming app/package will also reference vue.@mazurva Thanks for reporting. This issue has been fixed in v2.0.3.