Remove package-lock.json files and update GitHub Actions #58
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 package-lock.json files and update GitHub Actions
Summary
This PR makes several improvements to the repository:
Rationale
Removing package-lock.json follows best practices for npm packages, as package-lock.json should not be committed to repositories for libraries that will be consumed by other projects. For npm packages like this one:
The GitHub Actions workflows have been updated to use npm install instead of npm ci since npm ci requires a package-lock.json file.
Changes