Andrew Koidan

@jrconlin thanks a lot for clarifications. That really explained a lot!. As I understand this library provides an API to send push notification to a browser based on this README...

Can we also consider adding compile type check instead of relying on typescript type-safe? Like linter or so. Thus we can add it to vue-loader or smth.

@championswimmer which features make it better than [vue-property-decorator](https://github.com/kaorun343/vue-property-decorator)? I don't want to redeclare types above each action, I'm even lazy to append import for annotation, I guess other folks are...

@championswimmer ok, sorry my bad, I see it allows to describe vuex , looks promising.

@frankshaka any benefict for using `vuex-module-decorators` along with `vuex-class`? I see 2 issues: - what if I accidentally mistype `@foo.State bars: typeof Foo.prototype.oopsbars` - I won't get an exception -...

Any progress? It's been 1.5 year already...

> @akoidan sorry, `@for` is not supported yet Any ETA, cause it seems to be for 1.5 years already. Maybe we can ship the package that just skips fors loops?...

@AleshaOleg still doesn't work. The example above provides this error. Please mind the extension is 'vue' not 'sass' ```text : npm ls |grep postcss-sass │ ├─┬ [email protected] ``` ```text ✖...

@AleshaOleg seems like `@for` works now with freshly-released `stylelint:12.0.0`. Needs more testing though... Example is [here](https://github.com/akoidan/vue-webpack-typescript)

Nah, wrong still crases in [some cases](https://github.com/akoidan/vue-webpack-typescript/blob/dbe6f4295a65d6f4ff14722f6458c3c864325418/src/components/pages/FilteredUsersPage.vue#L47) mind the branch `crash`