Huseyn Guliyev

It exports Nuxt specific hooks and also vuex-class for convenience. But it would be very useful to mention key differences between this and nuxt-property-decorator. I wonder why the two can't...

@qm3ster see my suggestion [here](https://github.com/nuxt-community/nuxt-property-decorator/issues/25) about consolidating efforts and merging nuxt-class-component with nuxt-property-decorator (under new name potentially). Will be nice to see your opinions there.

With latest release of [nuxt-property-decorator](https://github.com/nuxt-community/nuxt-property-decorator/) I don't see any reason for using this library, plus it seems that this is not maintained anymore. _Nuxt-property-decorator_ currently covers everything this library is...

This is a very valid question. Any suggestion or better merge request will be welcome. As for Hooks autocomplete, I agree @scscgit and even was planning to add type safe...

@wiktor-obrebski can you mention problems you faced. We can solve them if we know and understand what is going on.

Thanks @wiktor-obrebski, indeed we need to sort this out. If anyone has any suggestions, please.

Here we mainly add decorators specific to core nuxt features e.g. router, vuex, vue-meta. Decorators for other libraries can easily be added separately. @marcin-stasiak I suggest to add that separtely....

I strongly recommend using [nuxt-property-decorator](https://github.com/nuxt-community/nuxt-property-decorator/) which has all this functionality and more

@MoronixProduct3 can I ask you to check something for me? Add this to one your client side plugins (preferably, those called earlier) ``` import "nuxt-property-decorator" ``` Does it get resolved...

Thanks @pi0 , I will be looking forward. Before even starting to change anything, we need to just get some ideas about how it will look in v3. For that...