Skip to content

chore: gitignore lockfiles from other package managers #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
sidgaikwad wants to merge 1 commit into from
Closed

chore: gitignore lockfiles from other package managers #53

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,3 +5,12 @@ node_modules
.history
dist
/coverage

# npm is the supported package manager (CI runs `npm ci` and the
# package-lock.json files are committed). Keep a stray lockfile from another
# resolver out of commits — two lockfiles in the tree make `npm ci` fail in
# confusing ways for the next person.
bun.lock
bun.lockb
pnpm-lock.yaml
yarn.lock
1 change: 1 addition & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,7 @@

## Installation

- npm is the supported package manager. CI runs `npm ci`, and both `package-lock.json` files are committed — other resolvers are gitignored so a stray lockfile cannot be committed by accident.
- Running `npm install` in the component's root directory will install everything you need for development.
- Running `npm install` in the `demo` directory will install everything you need to run the demo app locally.

Expand Down