From 5223954976fc0a853ce94f4efb067a7de416a7a8 Mon Sep 17 00:00:00 2001 From: MickLesk Date: Tue, 21 Jul 2026 23:00:43 +0200 Subject: [PATCH] Apply --include=dev to fresh installs too, for parity with update fix Couldn't confirm within this repo why devDependencies would only be omitted on update and not on a fresh install - create_backup/ restore_backup are plain file copies and nothing in tools.func sets NODE_ENV or writes an .npmrc. Since npm ci runs before .env is sourced in both scripts, apply the same explicit --include=dev to the installer as defense-in-depth against the same class of failure. --- install/nametag-install.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/install/nametag-install.sh b/install/nametag-install.sh index 8f952153b..4c285a2cf 100644 --- a/install/nametag-install.sh +++ b/install/nametag-install.sh @@ -20,7 +20,7 @@ fetch_and_deploy_gh_release "nametag" "mattogodoy/nametag" "tarball" "latest" "/ msg_info "Setting up Application" cd /opt/nametag -$STD npm ci +$STD npm ci --include=dev DATABASE_URL="postgresql://${PG_DB_USER}:${PG_DB_PASS}@127.0.0.1:5432/${PG_DB_NAME}" $STD npx prisma generate DATABASE_URL="postgresql://${PG_DB_USER}:${PG_DB_PASS}@127.0.0.1:5432/${PG_DB_NAME}" $STD npx prisma migrate deploy msg_ok "Set up Application"