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.

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

npm error Invalid: lock file's dayjs@1.11.12 does not satisfy dayjs@1.11.13 #30524

Closed
3 tasks done
kalyan540 opened this issue Oct 5, 2024 · 3 comments
Closed
3 tasks done

Comments

@kalyan540
Copy link

kalyan540 commented Oct 5, 2024

Bug description

when tried to build the Apache superset Non development version , caught this error " npm error Invalid: lock file's dayjs@1.11.12 does not satisfy dayjs@1.11.13"

Screenshots/recordings

image

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Copy link

dosubot bot commented Oct 5, 2024

To resolve the npm error "Invalid: lock file's dayjs@1.11.12 does not satisfy dayjs@1.11.13", you should update your package-lock.json file to match the version specified in package.json. Here are the steps you can follow:

  1. Delete the existing package-lock.json file.
  2. Run npm install to regenerate the package-lock.json file with the correct version of dayjs.

This will ensure that the lock file is consistent with the package.json dependencies [1].

To continue talking to Dosu, mention @dosu.

@hainenber
Copy link
Contributor

This is fixed in #30493. Please help pulling from latest master branch :D

@kalyan540
Copy link
Author

Thanks @hainenber

@kalyan540 kalyan540 reopened this Oct 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants