Security-relevant behaviour (development tokens, loopback HTTP, inline checkpoints, raw provider keys, optional verification profiles) was keyed off NODE_ENV === 'production', so any deployment that forgot NODE_ENV silently ran with development rules. - @wishforge/contracts exports deploymentMode/isProduction/ requireDeploymentMode. WF_DEPLOYMENT_MODE wins; misspelled values and development combined with NODE_ENV=production are rejected; NODE_ENV remains a fallback only for libraries and tests. - All API, runtime, artifact, Git service and operator-script checks use isProduction. - The API, worker, Git service and Runner refuse to start without an explicit WF_DEPLOYMENT_MODE; the IDE gateway treats anything other than an explicit development mode as production. - The development seed loads .env.local before checking the mode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
18 lines
362 B
JSON
18 lines
362 B
JSON
{
|
|
"name": "@wishforge/artifacts",
|
|
"version": "0.1.0",
|
|
"private": true,
|
|
"type": "module",
|
|
"main": "./src/index.ts",
|
|
"types": "./src/index.ts",
|
|
"exports": "./src/index.ts",
|
|
"scripts": {
|
|
"typecheck": "tsc --noEmit",
|
|
"build": "tsc --noEmit"
|
|
},
|
|
"dependencies": {
|
|
"@aws-sdk/client-s3": "3.1152.0",
|
|
"@wishforge/contracts": "*"
|
|
}
|
|
}
|