fix: remove standalone output mode to match PM2 next-start deploy
Some checks failed
changelog-draft / changelog-draft (push) Failing after 1s
security-scan / secret-scan (push) Successful in 3s

next.config.ts set output:standalone but ecosystem.config.js/deploy-213.sh
run next start against the full checkout, which next start does not
support in standalone mode (warns and skips the standalone server
entrypoint). Also syncs package-lock.json version field to package.json
(0.1.0 -> 0.5.0), which had drifted out of sync.
This commit is contained in:
Rene Fichtmueller 2026-07-18 09:39:39 +02:00
parent bd4ca738c6
commit 9c0964746f
2 changed files with 3 additions and 5 deletions

View File

@ -1,7 +1,5 @@
import type { NextConfig } from 'next'
const config: NextConfig = {
output: 'standalone',
}
const config: NextConfig = {}
export default config

4
package-lock.json generated
View File

@ -1,12 +1,12 @@
{
"name": "@shieldx/core",
"version": "0.1.0",
"version": "0.5.0",
"lockfileVersion": 3,
"requires": true,
"packages": {
"": {
"name": "@shieldx/core",
"version": "0.1.0",
"version": "0.5.0",
"license": "Apache-2.0",
"dependencies": {
"pg": "^8.13.0",