feat: use Bun in the code-check GitHub Action (#1568)

.github/workflows/code-check.yml

@@ -19,11 +19,9 @@ jobs:
     steps:
       - name: Checkout repository
         uses: actions/checkout@v3
-      - name: Set up Node.js
-        uses: actions/setup-node@v3
-        with:
-          node-version: 20
+      - name: Set up Bun
+        uses: oven-sh/setup-bun@v2
       - name: Install dependencies
-        run: npm install
+        run: bun install
       - name: Run TypeScript compiler
-        run: npm run type-check
+        run: bun run type-check

.husky/pre-commit

@@ -1,5 +1,5 @@
 #!/bin/sh
 . "$(dirname "$0")/_/husky.sh"
 
-npx lint-staged
-npm run type-check -- --incremental true
+bunx lint-staged
+bun run type-check -- --incremental true

README.md

@@ -36,16 +36,16 @@ Open source interface for Guild.xyz -- a tool for platformless membership manage
 
 ### Running the interface locally
 
-1. `npm i`
-2. `npm run dev`
+1. `bun i`
+2. `bun run dev`
 3. If you don't have the secret environment variables, copy the `.env.example` as `.env.local`.
 
 Open [http://localhost:3000](http://localhost:3000) in your browser to see the result.
 
 ### Getting secret environment variables (for core team members):
 
 1. Get added to the team on Vercel
-1. `npm i vercel@latest -g`
+1. `bun i vercel@latest -g`
 1. `vercel link`
 1. `vercel env pull .env.local`
 

package.json

@@ -8,7 +8,7 @@
     "build": "next build",
     "start": "next start",
     "type-check": "tsc --pretty --noEmit --incremental false",
-    "write-check": "npx @biomejs/biome check --write --unsafe .",
+    "write-check": "bunx @biomejs/biome check --write --unsafe .",
     "storybook": "storybook dev -p 6006 --no-open",
     "build-storybook": "storybook build"
   },