update Vuex types inside node_modules
See original GitHub issueReproduction Steps
-Update to vue.js 2.5
- This might be because "Previously, we already recommend using ES-style imports (import Vue from ‘vue’) everywhere with “allowSyntheticDefaultImports”: true in tsconfig.json. The new typings will officially move to ES-style import/export syntax, so that config is no longer necessary, and users are required to use ES-style imports in all cases. " - from https://goo.gl/pPJeiD
Error
in ‘project/node_modules/vuex-persist/node_modules/vuex/types/vue.d.ts’
(9,40): error TS2304: Cannot find name 'Vue'.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Can't resolve 'node_modules/vuex/types/index' #2076 - GitHub
In a nodejs app open app.js with VSCode and type "import create"; Select "createStore / node_modules/vuex/types/index" and press enter ...
Read more >Mutations | Vuex
The only way to actually change state in a Vuex store is by committing a mutation. Vuex mutations are very similar to events:...
Read more >Vuex in vue .net core application - Stack Overflow
thanks. that seems to have fixed most of it but I am still getting a couple of errors: ERROR in [at-loader] ./node_modules/vuex/types/helpers.d.
Read more >vuex - npm
state management for Vue.js. Latest version: 4.1.0, last published: 2 months ago. Start using vuex in your project by running `npm i vuex`....
Read more >How To Manage State in a Vue.js Application with Vuex
A mutation is a method that mutates or updates the store property with the value provided. Getters are methods that can modify or...
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
fixed
Same thing happened for me, deleting node_modules in the package indeed does fix this. However,
node_modules
is not checked into our repository so on CI or production the error returns as we runyarn install
there.