Maximilian Antoni

What is the status here? What is left to do in mochify.js?

Hmm. Can’t think of a good reason right now. I might have been lazy 😄

There is one problem with having two output streams: The output is buffered partially to detect stack traces and map them back to the original source location using sourcemaps. Therefore...

The one stream might be flushed while the other is still buffered. This could mean that you see a stack trace in the wrong place.

Sure. Care to look into how Mocha does it and come up with a suggestion on how to make it work?

@sankho Sorry for the late reply. The issue seems to be that `--path` returns a string while the internal `paths` option must be an array. PR #132 was implemented mainly...

Here is a suggestion how we could continue to release with `@studio/changes`: https://github.com/javascript-studio/studio-changes/pull/40 What do you think @m90?

I'm currently doing releases with ``` cd cli npm version patch cd .. npm install ``` The `version` script of each module would be `changes -w`.

We can also do ``` npm version patch -w cli ``` which has pretty much the same effect as the above, afaict. The npm status bar messes up the console...

Here is my view of what is good and bad about the "release very package workflow": ## Good It would be easier to generate the changelog on the top level...