Invalid: lock file's luxon@3.4.4 does not satisfy luxon@3.5.0
dimoha opened this issue · 2 comments
Bug description
Hi.
I have error when install 4.1.0 (docker, through docker-compose-non-dev.yml )
24.49 npm error Invalid: lock file's luxon@3.4.4 does not satisfy luxon@3.5.0
i think that fix here https://github.com/apache/superset/pull/30859/files
But this fix is not in tag 4.1.0
Screenshots/recordings
No response
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.
Hello, @dimoha! I'm here to help you with your Superset issue. I can assist with bug fixes, answer questions, and guide you on becoming a contributor. Let's tackle this together while we wait for a human maintainer.
The error you're encountering is due to a mismatch between the luxon package versions specified in the package-lock.json file and the package.json file. The package-lock.json file has luxon@3.4.4, while the package.json file specifies luxon@3.5.0 for Superset version 4.1.0 [1].
The fix you mentioned in pull request #30859 is not included in the 4.1.0 tag. To resolve this issue, you can manually update the package-lock.json file to match the luxon version specified in the package.json file, or you can wait for a new release that includes this fix. Alternatively, you can try using the latest version from the master branch if it includes the necessary updates.
Thank you for your quick and clear answer!