I'm maintaining a project that is still relying on Karma 0.9 – many of its modules is still strictly relying on 0.9 or is at least not compatible with Karma 0.11 that this module now requires as of b0992606925e200d2bde1ff01d46d17cf3a05c6f.
While it of course isn't an issue in itself that a new version of this modules requires a newer version of Karma it is an issue that the latest version of Karma 0.9 doesn't specify any specific version of this module causing Karma 0.9 to depend on 0.2.0 of this module that in turns requires karma to be 0.11 (I guess it's due to https://github.com/karma-runner/karma/blob/8c38782c015f5d6e9d891771ff07f83423b22377/package.json#L107)
I'm not sure where the error is to be found here – if it is Karma 0.9 that should have specified its version better, if its this module that should have done something in another way or if its my project that should have specified some more elaborate dependencies. Anyhow – since it's the release of 0.2.0 that caused this I thought this would be a good place for a first report of it.
Below is the full error from npm when trying a fresh install of my project:
I'm maintaining a project that is still relying on Karma 0.9 – many of its modules is still strictly relying on 0.9 or is at least not compatible with Karma 0.11 that this module now requires as of b0992606925e200d2bde1ff01d46d17cf3a05c6f.
While it of course isn't an issue in itself that a new version of this modules requires a newer version of Karma it is an issue that the latest version of Karma 0.9 doesn't specify any specific version of this module causing Karma 0.9 to depend on 0.2.0 of this module that in turns requires karma to be 0.11 (I guess it's due to https://github.com/karma-runner/karma/blob/8c38782c015f5d6e9d891771ff07f83423b22377/package.json#L107)
I'm not sure where the error is to be found here – if it is Karma 0.9 that should have specified its version better, if its this module that should have done something in another way or if its my project that should have specified some more elaborate dependencies. Anyhow – since it's the release of 0.2.0 that caused this I thought this would be a good place for a first report of it.
Below is the full error from npm when trying a fresh install of my project: