Remove package-lock.json files and add to .gitignore #57
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.
This PR removes package-lock.json files from git tracking and adds them to .gitignore to prevent them from being tracked in the future.\n\nThis 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:\n\n- It allows consumers to resolve dependencies based on their own environment\n- It prevents potential conflicts with consumers' dependency trees\n- It provides more flexibility with dependency version resolution\n- It aligns with npm's official recommendations for published packages\n\nThe changes include:\n1. Adding package-lock.json to .gitignore\n2. Removing existing package-lock.json files from git tracking