fix: remove standalone output mode to match PM2 next-start deploy
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:
parent
bd4ca738c6
commit
9c0964746f
@ -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
4
package-lock.json
generated
@ -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",
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user