fix: delete package-lock.json before npm install to prevent stale rule dep resolution#79
Merged
Sandy-at-Tazama merged 1 commit intodevfrom Apr 15, 2026
Merged
Conversation
…e dep resolution Signed-off-by: Justus Ortlepp <jortlepp@contractor.linuxfoundation.org>
Sandy-at-Tazama
approved these changes
Apr 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When \package.json\ is rewritten by \sed\ to replace the rule dependency alias, the existing \package-lock.json\ still has the old
esolved\ URL in its \packages\ section. npm honours the lock over \package.json\ and installs the wrong tarball (e.g.
ule-901\ instead of
ule-011). Deleting the lock before
pm install\ forces a clean resolution from the registry.