Sergii Lavrin

Are there any hopes for an update for JSPM 2? I do not imagine how development even possible with JSPM 2 and without HRM, since it doesn't even have a...

Right. Then can we hope for SystemJS 2.0 support update? :D

Thanks for the instructions! Btw, `import { AppContainer } from 'react-hot-loader'` no longer works in SystemJS 0.20.0. So we need to do this instead: ```js import rhl from 'react-hot-loader' const...

I'm not sure there is a way to do this natively, without writing an extension. In case of `node-sass` (`libsass`) you can use [`importer`](https://github.com/sass/node-sass#importer--v200---experimental) method to override the behaviour of...

In regular Vue templates it would be ```js import MyComponent from "./components/MyComponent.vue"; export default { name: "App", components: { MyComponent }, methods: { log () { console.log('hi from created') }...

`onCreatedHook` seems the most legit, but confusing that it's reversed `hook:created`. Though, `hook:` here looks like a namespace. Another one: `hookOnCreated` to namespace hook-events

Not sure it worth it. `onHookCreated` sounds not bad too and follows the generic idea of making all standard Vue events into just `on` versions.

Same way as it knows that `onSomething` should be `@something` and not `v-bind:onSomething` (which, by the way, has same not that fun implications when you're accidentally naming prop for accepting...

> alpha:beta I thought `hook:` is the only namespace. Then it might make sense. But following the logic of other JSX events, should it be ``?

I tend to agree with @chriseppstein Currently we already have very blurred mixins and functions, and out-of-place usage of mixins to make side effects. Mixins originally had to produce styles,...