From eb55c31e7c27ec62b4eb1e5fad67c0d7a583bb19 Mon Sep 17 00:00:00 2001 From: sidgaikwad Date: Fri, 4 Sep 2026 12:06:37 +0530 Subject: [PATCH] chore: gitignore lockfiles from other package managers MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit npm is clearly the intended package manager — both package-lock.json files are committed and CI runs `npm ci` — but nothing stopped a stray lockfile from another resolver being committed. Running `bun install` on a fresh clone leaves bun.lock and demo/bun.lock untracked and rewrites demo/package-lock.json in place, with nothing in the repo signalling that is wrong. Two lockfiles in the tree is exactly the state that makes `npm ci` fail confusingly for the next person. Ignore bun/pnpm/yarn lockfiles and state the supported package manager in CONTRIBUTING. --- .gitignore | 9 +++++++++ CONTRIBUTING.md | 1 + 2 files changed, 10 insertions(+) diff --git a/.gitignore b/.gitignore index 3aaba98..ef4aa30 100644 --- a/.gitignore +++ b/.gitignore @@ -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 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 701755e..53047ef 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -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.