-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[email protected] on npm does not match 1.7.1 source on GitHub #2827
Comments
Yes, the npm distribution is somehow messed up. The github source package.json How can we fix this? |
I think the problem here is that the 1.7.1 branch is not merged into HEAD |
I renamed this issue to make it more general, as there are other issues caused by this failed deployment. |
karma 1.7.1 is correct on npm. 1.7.1 was released with "old" lodash@3 because moving to 4 is breaking change. |
@dignifiedquire can you clean up the fact there are multiple tags for 1.7.1 then - and not containing the same source code - v1.7.1...1.7.1 Also can you update the changelog https://github.com/karma-runner/karma/blob/master/CHANGELOG.md#171-2017-08-25 to reflect what you said above :) |
@wilsonge thank you for pointing that out, should be fixed now and tags correct |
Thanks :) |
Expected behaviour
npm install [email protected] using https://registry.npmjs.org/ should have the same package.json dependencies as the karma-1.71.zip.
Actual behaviour
$ npm view [email protected] dist.tarball
https://registry.npmjs.org/karma/-/karma-1.7.1.tgz
$ curl -o karma-1.7.1-npm.com.tgz https://registry.npmjs.org/karma/-/karma-1.7.1.tgz
And then inspecting the tgz file it shows package.json dependencies with lodash: ^3.8.0 instead of ^4.x.y.
Environment Details
$ node --version
v6.11.1
$ npm --version
3.10.10
Steps to reproduce the behaviour
As above.
Is this a problem in publishing to registry.npmjs.org?
The text was updated successfully, but these errors were encountered: