Evan Davis

This has nothing to do with `children`. Read that error message again: > [your component type] was reduced to 'never' because property 'type' has conflicting types in some constituents `type`...

I'm having the same issue with a pretty simple webpack config: ``` javascript const path = require('path'); const webpack = require('webpack'); const ExtractTextPlugin = require('extract-text-webpack-plugin'); const isPROD = process.env.NODE_ENV ===...

This is the same issue as #43; Webpack processes files individually, so the sprite contains only the _last_ file.

The category is added automatically, but I'm stuck trying to get the name of the current project into the category filter from the agenda dispatcher. Writing it out, I think...

What I mean is this: 1. I'm editing a file in a known project, `my-project`. 2. From that buffer, I do `C-c a` to bring up the agenda dispatcher. 3....

I think it's because this package assumes that you have your scripts injected declaratively via `content_scripts` in the manifest. If your content script is injected programmatically (or if you don't...

> a component should always render, regardless of data. I agree with this and follow this practice. I think the example you should show is my guard example, rather than...

:+1: I've been a fan of this guide for a while; really happy to see it evolving.