Joe Pea

I want to write simple classes like these, which work great standalone with syntax we all are familiar with: ```js class Size { x = 1 y = 2 log...

If we had a feature like the previous comment, with rules around property access priority, then the properties and implied namespaces would be statically analyzable.

Because I know someone is going to ask, here are thoughts on how namespacing might work at a very high level: Based on how JavaScript works, where all properties are...

I have a basic implementation with tests here: - https://github.com/trusktr/lowclass/blob/master/src/multiple.ts - https://github.com/trusktr/lowclass/blob/master/src/multiple.test.ts ``` npm i npm test ``` The syntax is of course not native, so it is like ```js...

Another good reason to remove all the webpack stuff, and instead document it, is because all those dependencies add platform-specific build processes that might be unnecessary if the end user...

What we can do next is make a react-famous-webpack repo showing how to use react with Webpack, react-famous-browserify, react-famous-jspm, etc.

Sounds good. So it seems like one of the first things we need to do is move a bunch of the dependencies that you use for development into the `devDependencies`...

`peerDependencies` is deprecated now (https://github.com/pilwon/react-famous/blob/master/tools/publish/cjs/package.json#L21) so that's basically the `dependencies`.

I see you had separated the publish package.json into it's separate folder in tools/publish/cjs. An alternative would be to just put `prepublish` scripts in a single package.json, the `devDependencies` in...

JSPM and Webpack users, can then have more flexibility to choose how to process ES6 files, for example. JSPM users can specify that `src` is the project root, and when...