profile
viewpoint

iamdustan/arbiter 16

A lightweight html5 history library for ender.js

iamdustan/component-playground-responsive-iframe 10

A responsive iframe renderer for the React component playground.

iamdustan/bonsai-demos 7

Article and demos concerning bonsai for node knockout 2012.

iamdustan/categorizr.js 7

A port of @bjankord’s php script. https://github.com/bjankord/Categorizr

iamdustan/blessed-standup 6

Blessed UI for team standups, recorded in a google spreadsheet

iamdustan/babel-plugin-react-isomorphic 2

Babel plugin to transform react imports to react/lib/ReactIsomorphic

iamdustan/bonsai 1

BonsaiJS is a graphics library and renderer

pull request commentYomguithereal/react-blessed

Fixed devtools

Yeah, that was my intention @Yomguithereal. My intent was to keep them in peerDependencies for consumers. It may make sense to put them in both peerDependencies and devDependencies to serve both audiences (react-blessed contributors and consumers)

lins05

comment created time in a month

pull request commentYomguithereal/react-blessed

Fixed devtools

I had the understanding that peerDependencies was to inform consumers of the library that they would need to install those. Since devDependencies are only installed while working no this library directly users won’t get them or get the peerDep notification that they need to install react-devtools-core to use react-devtools in their apps.

lins05

comment created time in a month

more