chore(test): remove npm lockfile from crashtracker test#90
Merged
Conversation
The crashtracker test uses yarn (yarn.lock already exists), so the npm package-lock.json is unnecessary.
gyuheon0h
approved these changes
Mar 3, 2026
Overall package sizeSelf size: 37.25 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------|🤖 This report was automatically generated by heaviest-objects-in-the-universe |
tlhunter
pushed a commit
that referenced
this pull request
Mar 19, 2026
The crashtracker test uses yarn (yarn.lock already exists), so the npm package-lock.json is unnecessary.
tlhunter
pushed a commit
that referenced
this pull request
Mar 20, 2026
The crashtracker test uses yarn (yarn.lock already exists), so the npm package-lock.json is unnecessary.
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.
Remove the stale
test/crashtracker/package-lock.jsonfile. The crashtracker test already uses yarn (yarn.lockis present and tracked), so the npm lockfile is unnecessary and could cause confusion about which package manager to use.