src/bin/shared/constants.ts (1)

91-91: Name and placement LGTM; add a brief doc for discoverability.
A short JSDoc helps users know how to populate this env var.

Apply this diff:

-export const KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT = "KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT";
+/** JSON string from `keycloakify print-build-context` used to bypass subprocesses in getBuildContext */
+export const KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT = "KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT";

src/bin/keycloakify/keycloakify.ts (1)

110-117: Make the skip-post-build guidance name the exact env var.
Users see which variable to set without guessing.

Apply this diff:

-            console.log(
-                chalk.yellow(
-                    `⚠️  --skip-post-build passed. Skipping the post build script step. (run postbuild manually with RUN_POST_BUILD_SCRIPT env var)`
-                )
-            );
+            console.log(
+                chalk.yellow(
+                    `⚠️  --skip-post-build passed. Skipping the post-build script. ` +
+                    `You can run it manually by setting ${VITE_PLUGIN_SUB_SCRIPTS_ENV_NAMES.RUN_POST_BUILD_SCRIPT}.`
+                )
+            );

src/bin/main.ts (3)

71-90: Optional: add short aliases and keep option naming consistent

Consider short flags for ergonomics and to align with other options that expose short names (e.g., -p for project). Example: -J for --skip-jar and -B for --skip-post-build. Push both long and short into optionsKeys to keep the unknown-option guard working.

Apply this diff to both options:

 .option({
   key: "skipJar",
-  name: (() => {
-      const name = "skip-jar";
-      optionsKeys.push(name);
-      return name;
-  })(),
+  name: (() => {
+      const long = "skip-jar";
+      const short = "J";
+      optionsKeys.push(long, short);
+      return { long, short };
+  })(),
   description: "Skip output JAR file generation.",
   defaultValue: false
 })
 .option({
   key: "skipPostBuild",
-  name: (() => {
-      const name = "skip-post-build";
-      optionsKeys.push(name);
-      return name;
-  })(),
+  name: (() => {
+      const long = "skip-post-build";
+      const short = "B";
+      optionsKeys.push(long, short);
+      return { long, short };
+  })(),
   description: "Skip post-build steps.",
   defaultValue: false
 })

---

403-403: Nit: polish the help text

Minor grammar/style improvement.

-    description: "print a build context for non npx build runners. pass the result to KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT env variable",
+    description: "Print the build context for non-NPX build runners. Pass the result to the KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT environment variable.",

---

408-410: Ensure JSON-only output and robust serialization

If KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT is set, getBuildContext logs to stdout (“Using predefined build context…”), which will corrupt the JSON stream. Also, buildContext may contain non-serializable/circular values (e.g., getters), risking JSON.stringify failures.

Suggestion: temporarily unset the env var to avoid the extra log and use a safe replacer to drop functions and handle cycles.

-        const buildContext = getBuildContext({ projectDirPath });
-        console.log(JSON.stringify(buildContext))
+        // Avoid stdout noise from env-based short-circuit during printing
+        const ENV_KEY = "KEYCLOAKIFY_PREDEFINED_BUILD_CONTEXT";
+        const prev = process.env[ENV_KEY];
+        if (prev !== undefined) {
+            delete process.env[ENV_KEY];
+        }
+        const buildContext = getBuildContext({ projectDirPath });
+        if (prev !== undefined) {
+            process.env[ENV_KEY] = prev;
+        }
+        // Safe stringify: drop functions and handle circular refs
+        const seen = new WeakSet();
+        const json = JSON.stringify(
+            buildContext,
+            (k, v) => {
+                if (typeof v === "function") return undefined;
+                if (typeof v === "object" && v !== null) {
+                    if (seen.has(v)) return undefined;
+                    seen.add(v);
+                }
+                return v;
+            }
+        );
+        console.log(json);

If you prefer not to change behavior here, alternatively switch the “Using predefined build context…” log in src/bin/shared/buildContext.ts to stderr (console.error) so it won’t break JSON output.

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro