Nikhil Verma
Nikhil Verma
Support/Enhancement for other Babel Plugins - Null Coalescing Operator, Optional Chaining and others
Here is a solution if you are using a package manager which supports resolutions in package.json ```json { "resolutions": { "vue-template-es2015-compiler": "npm:[email protected]" } } ```
Support/Enhancement for other Babel Plugins - Null Coalescing Operator, Optional Chaining and others
@souljorje Apologies I meant package manager. so 1. Yarn 2. pnpm 3. npm with https://www.npmjs.com/package/npm-force-resolutions
Support/Enhancement for other Babel Plugins - Null Coalescing Operator, Optional Chaining and others
I've made a PR to fix this issue - https://github.com/underfin/vite-plugin-vue2/pull/179
@yyx990803 Can you please consider this? I think this offers a significant improvement in type safety of `Vue.set`
@negibouze Has a great solution but it didn't work for me because I was using the following ESLint config ``` { parser: require.resolve("vue-eslint-parser"), parserOptions: { parser: "@typescript-eslint/parser" } } ```...
I understand that the Vue 3 internal changes could prevent vee-validate from having the same API. But the new API has almost no resemblance to the previous one. Even the...
Seems like it's using an old dependency for licence checker which doesn't even support --production
Here is a solution if you are using a bundler which supports resolutions in package.json ```json { "resolutions": { "vue-template-es2015-compiler": "npm:[email protected]" } } ```
1. `Mutation` is called with the context of `state` 2. `MutationAction` is called with the context of `store` I agree it's not evident at all, and perhaps the fix can...
I made a PR which documents how to "fix" this issue - https://github.com/championswimmer/vuex-module-decorators/pull/374