-
Notifications
You must be signed in to change notification settings - Fork 30
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
[0.11.x] Fix conflicting npm dependencies and bump typescript 4 to 5 - Fixes #1182 #1241
Conversation
fc3adf3
to
d05a9ab
Compare
@johnaohara We need to regenerate steps
|
yeah, package-lock is becoming a massive pain point for us, I need to think about ways of handling it so we are not being constantly affected by conflicts and having to rebuild |
d05a9ab
to
18b796c
Compare
Ci failure look a npm issue-https://github.com/Hyperfoil/Horreum/actions/runs/7764614586/job/21178269891?pr=1241#step:6:619 see discussions and solution on the issue-npm/cli#4828 (comment)
we have to stop dependabot for |
I have not access of this otherwise i can try to fix it in my env |
I don't think dependabot is the cause of this issue, I built the package-lock.json on my Mac, which is currently using npm 9.5.0 I think a lot of our problems are coming from different versions of node/npm in different environments. I think we need to consider using a consistent env (possibly CI) to build package-lock.json for us |
Yeah, It is.
Then let's keep current node/npm versions which is used by horreum, in local as well so I have this already and I think you have to follow this. |
Could you explain why you think dependabot is the issue? |
@shivam-sharma7 I think we should take the package-lock.json chat to a discussion |
as @jesperpedersen said-#587 (comment) |
18b796c
to
41d21f7
Compare
Backport: #1224
Fixes Issue #1182
Changes proposed
Check List (Check all the applicable boxes)