chore: 패키지 매니저를 bun으로 전환하고 커밋 전 lint/format 검사 훅 추가 - #299
Merged
Conversation
- package-lock.json -> bun.lock, CI/Dockerfile을 bun 기준으로 갱신 - husky + lint-staged 도입 (staged 파일 ESLint --fix + Prettier) - vitest pool을 threads로 고정 (bun 실행 시 기본 forks 풀이 워커를 못 띄우는 문제 회피) - .nvmrc + package.json engines로 Node 20 고정 - .github/dependabot.yml 추가 (bun 의존성 + GitHub Actions 주간 스캔) - README 시작하기/스크립트 섹션을 bun 명령으로 갱신 resolves #297
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
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.
closes #297
변경 사항
package-lock.json→bun.lock전환, 전체 스크립트(dev/build/lint/format/test) bun 기준 동작 확인husky+lint-staged도입 — 커밋 시 staged 파일에 ESLint(--fix) + Prettier 자동 실행ci.yml)를oven-sh/setup-bun기준으로 갱신Dockerfile빌드 스테이지를oven/bun:1-alpine기준으로 갱신.nvmrc+package.json engines로 Node 20 고정.github/dependabot.yml추가 (bun 의존성 + GitHub Actions 주간 스캔)트러블슈팅
bun run test실행 시 vitest 기본forks풀이 워커 프로세스를 못 띄우고 타임아웃나는 문제 발견 (Windows 환경).vite.config.ts의 vitestpool을'threads'로 고정해서 해결 — bun/node 어느 런타임에서 실행해도 동일하게 동작.검증
bunx tsc -b통과bun run lint통과bun run test— 83 files / 438 tests 전부 통과bun run build통과