So, this is kind of becoming a personal mission of mine, but what would you think about declaring a v1? The traditional criteria (stated if not practiced) has been if it's being used in production it's v1+. Coupled with npm's new ^ behavior, it would be great to be able to specify "rework-npm": "^1.0.0" and know any new, non-breaking hotness would be fetched on future installs.
Definitely should do this, but I think we need to wait for the css-parse to release v2.0.0, since the current version breaks with css-parse master.
Ah OK, cool. Will that cause the API of rework-npm to change?
Not sure yet, although it could be possible.
Should also get #10 taken care of before a 1.0.
OK, after moving to the reworkcss org and some breaking changes, I think this is ready to go.
Please test and provide feedback! /cc @bclinkinbeard @necolas
Looks good to me! A couple of quick tests behaved as I expected.