summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHyteq <DerpsDer.es@gmail.com>2025-06-23 13:39:38 +0300
committerHyteq <DerpsDer.es@gmail.com>2025-06-23 13:39:38 +0300
commitfd7ac5fd42e21dc963d9cc0477665e5fc574dac7 (patch)
treea85e80305647f260e17bdd911395125e7ea176b5
parenta71ca538b1d310d19d13f5b55c0b7614928bebb0 (diff)
downloadopencut-fd7ac5fd42e21dc963d9cc0477665e5fc574dac7.tar.gz
fix: mentions of npm
-rw-r--r--.github/CONTRIBUTING.md7
-rw-r--r--apps/web/package.json1
2 files changed, 5 insertions, 3 deletions
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
index 61ca59ec..51893058 100644
--- a/.github/CONTRIBUTING.md
+++ b/.github/CONTRIBUTING.md
@@ -13,6 +13,7 @@ Thank you for your interest in contributing to OpenCut! This document provides g
### Prerequisites
- Node.js 18+
+- Bun (latest version)
- Docker (for local database)
### Local Development
@@ -37,15 +38,15 @@ Thank you for your interest in contributing to OpenCut! This document provides g
1. Create a new branch: `git checkout -b feature/your-feature-name`
2. Make your changes
3. Write tests for new functionality
-4. Ensure all tests pass: `npm test`
-5. Run the linter: `npm run lint`
+4. Ensure all tests pass: `bun test`
+5. Run the linter: `bun run lint`
6. Commit your changes with a descriptive message
7. Push to your fork and create a pull request
## Code Style
- We use Biome for code formatting and linting
-- Run `npm run format` before committing
+- Run `bun run format` before committing
- Follow the existing code patterns
## Pull Request Process
diff --git a/apps/web/package.json b/apps/web/package.json
index d3d59e61..581aa023 100644
--- a/apps/web/package.json
+++ b/apps/web/package.json
@@ -2,6 +2,7 @@
"name": "next-template",
"version": "0.1.0",
"private": true,
+ "packageManager": "bun@1.2.2",
"scripts": {
"dev": "next dev --turbopack",
"build": "next build",