Skip to content

Conversation

@ikalnytskyi
Copy link
Member

@ikalnytskyi ikalnytskyi commented Dec 26, 2017

We need to update package-lock.json to use sha512 algorithm for
integrity checksum in order to get rid of the following warnings:

WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-c+DAyp8LMm2nzSs2uXEuxp4LYGSUYEyHtU3fU57avFChjsnTmmpWmXj2dv0yUxHTEydgVAv5fIzA+4KJwoqWDA== integrity checksum failed when using sha512: wanted sha512-c+DAyp8LMm2nzSs2uXEuxp4LYGSUYEyHtU3fU57avFChjsnTmmpWmXj2dv0yUxHTEydgVAv5fIzA+4KJwoqWDA== but got sha1-r+Y615kgmYk0ixEJtE/rZqokX1c=. (1723 bytes)
WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-exAHB+NeFGxkfQ5dSUD03xl3zYGneeSk2Mw2ldTt/nTvYxuDiuSp3DlxgUBgzbdTFG4fbwPk0WtKWOoTXCmNGg== integrity checksum failed when using sha512: wanted sha512-exAHB+NeFGxkfQ5dSUD03xl3zYGneeSk2Mw2ldTt/nTvYxuDiuSp3DlxgUBgzbdTFG4fbwPk0WtKWOoTXCmNGg== but got sha1-QsnIZ4T2dMFz+yGILKlkMzQCneQ=. (25262 bytes)
WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-yd7CkUughvHQoEahQqcMdrZw6o/6PwUxiRkfZuVDVHCDe77mysD/suoNyk5mK6phTnRW1kyIbPHyCJgxw++LXg== integrity checksum failed when using sha512: wanted sha512-yd7CkUughvHQoEahQqcMdrZw6o/6PwUxiRkfZuVDVHCDe77mysD/suoNyk5mK6phTnRW1kyIbPHyCJgxw++LXg== but got sha1-Rz0CHsxXOizOHAfVtQnVIV9GujU=. (3239 bytes)
WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.

Please note, the following warnings are shown when you run npm install
from scratch (i.e. no dependencies are installed). You probably will
need to run npm cache clear --force on your machine before.

We need to update package-lock.json to use sha512 algorithm for
integrity checksum in order to get rid of the following warnings:

 WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-c+DAyp8LMm2nzSs2uXEuxp4LYGSUYEyHtU3fU57avFChjsnTmmpWmXj2dv0yUxHTEydgVAv5fIzA+4KJwoqWDA== integrity checksum failed when using sha512: wanted sha512-c+DAyp8LMm2nzSs2uXEuxp4LYGSUYEyHtU3fU57avFChjsnTmmpWmXj2dv0yUxHTEydgVAv5fIzA+4KJwoqWDA== but got sha1-r+Y615kgmYk0ixEJtE/rZqokX1c=. (1723 bytes)
 WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
 WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-exAHB+NeFGxkfQ5dSUD03xl3zYGneeSk2Mw2ldTt/nTvYxuDiuSp3DlxgUBgzbdTFG4fbwPk0WtKWOoTXCmNGg== integrity checksum failed when using sha512: wanted sha512-exAHB+NeFGxkfQ5dSUD03xl3zYGneeSk2Mw2ldTt/nTvYxuDiuSp3DlxgUBgzbdTFG4fbwPk0WtKWOoTXCmNGg== but got sha1-QsnIZ4T2dMFz+yGILKlkMzQCneQ=. (25262 bytes)
 WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.
 WARN registry Unexpected warning for https://registry.npmjs.org/: Miscellaneous Warning EINTEGRITY: sha512-yd7CkUughvHQoEahQqcMdrZw6o/6PwUxiRkfZuVDVHCDe77mysD/suoNyk5mK6phTnRW1kyIbPHyCJgxw++LXg== integrity checksum failed when using sha512: wanted sha512-yd7CkUughvHQoEahQqcMdrZw6o/6PwUxiRkfZuVDVHCDe77mysD/suoNyk5mK6phTnRW1kyIbPHyCJgxw++LXg== but got sha1-Rz0CHsxXOizOHAfVtQnVIV9GujU=. (3239 bytes)
 WARN registry Using stale package data from https://registry.npmjs.org/ due to a request error during revalidation.

Please note, the following warnings are shown when you run `npm install`
from scratch (i.e. no dependencies are installed). You probably will
need to run `npm cache clear --force` on your machine before.
@ikalnytskyi ikalnytskyi requested review from lotrien and malor December 26, 2017 19:38
@lotrien lotrien merged commit e089051 into master Dec 26, 2017
@lotrien lotrien deleted the package-lock-no-warnings branch December 26, 2017 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants