Skip to content
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.

Sign up for GitHub

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

Jump to bottom

B: package-lock.json is out of sync with package.json #58

Closed
kenrick95 opened this issue Aug 4, 2019 · 1 comment
Closed

B: package-lock.json is out of sync with package.json #58

kenrick95 opened this issue Aug 4, 2019 · 1 comment
Assignees
@xinbenlv
Labels
bug Something isn't working
Milestone
v1.0.0-beta

Comments

@kenrick95
Copy link

After freshly cloning this repository, I run the command npm ci to cleanly install packages as specified in package-lock.json, but it failed because package.json and package-lock.json are "not in sync".

The full error log are:

npm ERR! cipm can only install packages when your package.json and package-lock.json or npm-shrinkwrap.json are in sync. Please update your lock file with `npm install` before continuing.
npm ERR!
npm ERR!
npm ERR! Missing: @dicebear/avatars@^3.1.3
npm ERR! Missing: @dicebear/avatars-male-sprites@^2.1.3
npm ERR!

npm ERR! A complete log of this run can be found in:
npm ERR!     [redacted]\npm-cache\_logs\2019-08-04T15_00_02_922Z-debug.log

To fix this, I run npm install command, and indeed the package-lock.json file is updated. Please update package-lock.json. (I can send a PR if you don't mind 😁)

Thanks
@xinbenlv xinbenlv self-assigned this Aug 6, 2019
@xinbenlv xinbenlv changed the title package-lock.json is out of sync with package.json B: package-lock.json is out of sync with package.json Aug 6, 2019
@xinbenlv
Copy link
Contributor

xinbenlv commented Aug 6, 2019

Thank you for reporting. I will address this soon

@xinbenlv xinbenlv added the bug Something isn't working label Aug 6, 2019
@xinbenlv xinbenlv added this to the v1.0.0-beta milestone Aug 7, 2019
xinbenlv added a commit that referenced this issue Aug 7, 2019
@xinbenlv
Mega commit, contains fix #60, #59, #58, #57"
0e5c6ec 
> - #57, when multiple commits were conducted by the same user, the revert url redirect to history page so the reviewer can have a better overview.
>   we will further improve this with ROLLBACK feature or ADMIN notice feature in future release when we are granted Oauth
> - #58, package-lock.json rescyned by running `npm i`
> - #59, added template.env
> - #60, the error is caused by when ORES score is not available for an individual revision. We ignore them in this case.
@xinbenlv xinbenlv closed this as completed Aug 7, 2019
@HashTalmiz HashTalmiz mentioned this issue Apr 28, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xinbenlv xinbenlv

Labels
bug Something isn't working
Projects
None yet
Milestone
v1.0.0-beta
Development

No branches or pull requests
2 participants
@xinbenlv @kenrick95