Dave Mo

+1

Thanks @bsoulier This worked for me: ``` allDiagnostics.map( function (err) { console.error(colors.red(err.file.fileName + ':' + err.messageText)); }); ``` "awesome-typescript-loader": "^3.1.2", "typescript": "^2.2.2", "webpack": "^2.4.1",

Problem still remains, exactly as described by @Izhaki . Bandaid fix by @rikkertkoppes works for me. ``` import { Bezier } from 'bezier-js'; let BezierClass: typeof Bezier = require('bezier-js'); ```

It's really simple, and the guide is here https://storybook.js.org/basics/guide-vue/ Basically: 1. install storybook globally: `npm i -g storybook` 2. in the project directory run `getstorybook`, which should detect vue and...

just looking in the codebase, basically you are using a Vue vm as a store, correct? if so, quality should be high, no?

problems with Vuex: 1) way too much boilerplate. most of which seems to serve no purpose other than to comply with data binding abstractions de jeur (Flux, Elm, etc.). 2)...

Probably the next step i'd take is to enumerate all of the reactive data-binding models and frameworks of relevance, see what's out there.

@egoist very nice, with one suggestion - see my comment in that issue. David

@egoist Very nice, and very simple, just two decorations `@store` and `@computed`, I like it! One issue: I question the pattern (or anti-pattern) of adding the store to the root...

@egoist @Jack85 I have given this a bit more thought. Here is my proposal: a) Introduce a **single** new concept, a Store, using either `@store` decorator, or alternatively, a VueStore...