fix: initialize configured auth in production builds
Quality / quality (ubuntu-latest) (push) Failing after 9m54s
Quality / quality (windows-latest) (push) Canceled after 0s

This commit is contained in:
2026-08-22 23:36:31 +05:30
parent 37439188ca
commit 9332522614
5 changed files with 18 additions and 4 deletions
+1 -1
View File
@@ -1,6 +1,6 @@
{
"name": "@wrnexus/cli",
"version": "0.8.50",
"version": "0.8.51",
"type": "module",
"main": "src/index.ts",
"exports": {
+9
View File
@@ -702,6 +702,15 @@ applyAuthzManifestEarly([${authzSetupEntries}]);
imports.push(`import "./.authz-setup.ts";`);
}
// Runtime plugin state (notably the configured auth engine and OAuth
// providers) is established by evaluating the application config. The build
// process runs in a different process, so its globals cannot serve the
// generated production server.
const runtimeConfigPath = ["wrnexus.config.ts", "wrnexus.config.js", "wrnexus.config.mjs"]
.map((name) => join(appRoot, name))
.find(existsSync);
if (runtimeConfigPath) imports.push(`import ${JSON.stringify(fwd(runtimeConfigPath))};`);
const manifestRoutes = (routes: Route[]): string => {
const parts = routes.map((r) => {
const v = `m${counter++}`;