selected unified package manager

This commit is contained in:
Dmitri 2026-07-07 08:53:18 +02:00
parent 49917e6406
commit d081be19a1
4 changed files with 9 additions and 4 deletions

View File

@ -2,6 +2,7 @@
"name": "tourbuilderplatform", "name": "tourbuilderplatform",
"description": "Tour Builder Platform - template backend", "description": "Tour Builder Platform - template backend",
"type": "module", "type": "module",
"packageManager": "npm@11.9.0",
"scripts": { "scripts": {
"start": "npm run db:migrate && npm run db:seed && npm run watch", "start": "npm run db:migrate && npm run db:seed && npm run watch",
"start-dev": "LOG_PRETTY=true npm run start", "start-dev": "LOG_PRETTY=true npm run start",

View File

@ -46,13 +46,15 @@ TODO:
### Package manager ### Package manager
Сейчас есть смешение lockfiles/scripts. Решение: для root/frontend/backend используется только `npm`.
Источник истины для dependency graph: `package-lock.json` в `frontend/` и `backend/`.
Команды установки/deploy остаются на `npm ci` / `npm install` и `npm run ...`.
TODO: TODO:
- Выбрать один package manager для frontend/backend. - [x] Выбрать один package manager для frontend/backend: `npm`.
- Удалить лишний lockfile после проверки install/build. - [x] Удалить лишний lockfile после проверки: лишних `yarn.lock` / `pnpm-lock.yaml` нет, остаются только `package-lock.json`.
- Обновить docs/deployment commands. - [x] Обновить docs/deployment commands: текущие docs уже используют `npm`.
### Dependencies LTS alignment и obsolete package replacement ### Dependencies LTS alignment и obsolete package replacement

View File

@ -1,5 +1,6 @@
{ {
"private": true, "private": true,
"packageManager": "npm@11.9.0",
"scripts": { "scripts": {
"dev": "next dev -p ${FRONT_PORT:-3001}", "dev": "next dev -p ${FRONT_PORT:-3001}",
"dev:turbo": "next dev --turbopack -p ${FRONT_PORT:-3001}", "dev:turbo": "next dev --turbopack -p ${FRONT_PORT:-3001}",

View File

@ -1,6 +1,7 @@
{ {
"name": "app", "name": "app",
"version": "0.0.1", "version": "0.0.1",
"packageManager": "npm@11.9.0",
"scripts": { "scripts": {
"build:production": "cd ./frontend && npm ci && npm run build && cd ../backend && npm ci && npm run build", "build:production": "cd ./frontend && npm ci && npm run build && cd ../backend && npm ci && npm run build",
"start:production": "cd ./backend && npm run start" "start:production": "cd ./backend && npm run start"