You can clone with
HTTPS or Subversion.
I think it's safe to say Rework is being used in production quite a bit, so between that and the new ^ behavior of npm I am thinking a 1.0.0 release makes sense.
Would you guys be open to that once we break out the plugins?
yup, need css-parse and css-stringify v2. basically we just need to revert reworkcss/css-parse@190ba98 and make sure source maps work flawlessly with https://github.com/mozilla/source-map
@conradz has done a great job with sourcemaps reworkcss/css-parse#74
the following tasks are what I believe are necessary for rework v1 and css-parse/css-stringify v2.
since rework itself will be very small with all the plugins in separate repos, it would be nice to cleanup the readme and point to respective repos for docs. i.e. point to css-parse for the AST and errors, rework-visit, and each specific plugin.
Closing as question was answered.
We might be better off doing a RC so plugin authors have a bit of time to migrate and surface any issues. Especially since we're using parse/stringify directly now, and there are some features in parse that aren't yet supported in stringify.
I think we can avoid a RC since we are changing the major version. Anyone following semver will need to manually update the version they depend on, and anyone not following semver deserves the headache. :)
Well, I think RC gives us time to find issues and have more plugins migrated by the time the final release is out.