Joe Pea
Joe Pea
You'll notice in the infamous package.json the [prepublish](https://github.com/infamous/infamous/blob/master/package.json#L12) script that build CommonJS for publishing to npm. I also included the build-\* scripts in case anyone else wants a different format....
Another advantage of having the root of the github repo be the root of the react-famous package is that when people want to install your package from git, using npm,...
Another thing you could do, if you want to keep a higher-level folder for react-famous, for development, would be to create a separate repo, react-famous-dev, then you can import react-famous...
Well, anyways, this weekend or after I'll propose a format to make the package as consumable as possible, via bower, npm, jspm, with webpack, browserify, jspm, etc. If you could...
@jpdesigndev Yep, I'm working on the mixed-mode branch in my fork. PRs soon. :)
Aha, I found the immediate solution for my case, I just pass the `_famousParent`: ``` jsx class Card extends React.Component { render() { let card = this.props.context return ( //
Maybe we can add some additional logic somewhere to do this automatically?
If there is no immediate `_famousParent`, we can search up the tree for one. I think that's what `FamousUtil.getFamousParent(this)` is supposed to do? If so, maybe I found a bug?
We can achieve this with the `zeromq` package.
Yeah, perhaps a toggle would do it. let me see if I can circle back to this.