chore: add gitignore and update lockfile #1
Conversation
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
1 participant
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.
Description
This PR introduces two small but important housekeeping improvements aimed at keeping the repository clean and easier to maintain.
🔧 Changes Included
Added a proper .gitignore to prevent node_modules, build artifacts, and other generated files from being tracked.
Regenerated and updated package-lock.json after installing dependencies with a clean environment.
🎯 Why These Changes Matter
Ensures that unnecessary and heavy directories (like node_modules) are never committed, reducing repo size and avoiding accidental noise in future PRs.
Guarantees consistency in dependency resolution across environments thanks to the updated lockfile.
Improves contributor experience by preventing thousands of unwanted file changes from appearing in version control.
🧪 How to Test
Pull the branch:
git checkout chore/review-repo
Install dependencies:
npm install
Verify that:
No node_modules files appear in git status.
The project runs normally:
npm run dev
📌 Notes
No functional code was modified.
This PR prepares the project for cleaner upcoming contributions and refactors.