Vuex-module-decorators: Linting Error after vuex and vuex-module-decorators upgraded

[kisonay]

After upgrading vuex to 3.1.0 I am receiving the following linting error even though node_modules is excluded and no other node module reports any warnings or error:

ERROR in .../node_modules/vuex-module-decorators/dist/types/vuexmodule.d.ts
2:46 Type parameter defaults can only reference previously declared type parameters.
    1 | import { ActionTree, GetterTree, Module as Mod, ModuleTree, MutationTree, Store, ActionContext } from 'vuex';
  > 2 | export declare class VuexModule<S = ThisType<S>, R = any> implements Mod<S, R> {
      |                                              ^
    3 |     static namespaced?: boolean;
    4 |     static state?: any | (() => any);
    5 |     static getters?: GetterTree<any, any>;

Any ideas why this would happend out of nowhere?

::EDIT::
Looks unrelated to the upgrade. Downgrading doesn’t remove the error. Looks to be related to my usage of it. I’ll continue to debug. Just strange since it is an exclude directory.

[MantasPauliukonis]

I've started to get this error after upgrading typescript from 3.2.4 to 3.3.1. Currently reading the changelog, it doesn't seem to indicate any changes in generics. Possibly it was one of the bugfixes.

[championswimmer]

I'll have to take a look at it with Typescript 3.3 then

On Mon 4 Feb, 2019, 12:03 PM MantasPauliukonis <[email protected]
wrote:

I've started to get this error after upgrading typescript from 3.2.4 to
3.3.1. Currently reading the changelog, it doesn't seem to indicate any
changes in generics. Possibly it was one of the bugfixes.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/championswimmer/vuex-module-decorators/issues/90#issuecomment-460144258,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABQ_yhZ9syGgkGP4-HTGmS2FiClPszdXks5vJ9QegaJpZM4afmnG
.

[kisonay]

@MantasPauliukonis @championswimmer thank you both. I knew it had something to do with an upgrade, didn't even dawn on me to check if typescript was updated.

[newink]

Did not update anything, typescript 3.0.0 this error just appeared from nowhere, did you manage to solve it?

[kisonay]

@newink. Not yet on my end.

[holwech]

The error is related to the Typescript package, downgrade to 3.2.4 and the error disappears. For anyone who needs a temporary fix, run npm install [email protected].

[Saravanan-Duraisamy]

Facing the same issue. Followed @holwech advice.
Downgraded Typescript from 3.3.1 to 3.2.4 and that solved the problem for now.

[championswimmer]

v0.9.8 is compatible with latest Tyescript :) please upgrade