Process for publishing package

[jeznag]

Need to figure out how to publish the package. Will it get rolled into lerna mono-repo or kept separate?

[nicojs]

This is a good question. Generally, everything in the mono-repo is "officially maintained", meaning maintained by @simondel and me. Spin-offs like this tape runner, the stryker-lab-runner, stryker-jest-runner are maintained by other people. @simondel and me don't know a lot about them. Better if people actually using those runners maintain them.

So i think it's better if they stay separate. Unless you want it to be part of the monorepo, and we make you a maintainer.

That being said, it can be annoying keeping up with API changes. For example: if we make a breaking change in the reporter api, we are forced to create a new major release (in semver 2.0 every new 0.x release is a major release). When we do that, you are forced to create a new release as well, even though nothing changed on the api for test runners.

We can solve this by pulling out all different api parts into separate npm modules:

• stryker-api-reporter
• stryker-api-runner
• stryker-api-mutator
• etc

This means that people need to install all of that whenever they want to use Stryker. Let's not do that...

Another solution would be for you to add "peerDependencies": { "stryker-api": "0.x" } in your package.json. Downside is that it will break once we actually do change the api of the test runner.

@jeznag what do you think? Any idea's?