refactor(cli): share banner gate via napi binding

Expose `shouldPrintVitePlusHeader()` from the NAPI binding so the Node
CLI's `printHeader()` helper can defer to the same Rust predicate used
by the Rust CLI. Removes the `process.stdout.isTTY` + `GIT_INDEX_FILE`
checks that were duplicated on the JS side; future changes to the gate
(e.g. lefthook detection) now only need to touch `vite_shared::header`.

Regenerates the NAPI type definitions.

Author: fengmk2

packages/cli/binding/index.cjs

@@ -775,4 +775,5 @@ module.exports.rewritePrettier = nativeBinding.rewritePrettier;
 module.exports.rewriteScripts = nativeBinding.rewriteScripts;
 module.exports.run = nativeBinding.run;
 module.exports.runCommand = nativeBinding.runCommand;
+module.exports.shouldPrintVitePlusHeader = nativeBinding.shouldPrintVitePlusHeader;
 module.exports.vitePlusHeader = nativeBinding.vitePlusHeader;

packages/cli/binding/index.d.cts

@@ -369,5 +369,13 @@ export interface RunCommandResult {
   pathAccesses: Record<string, PathAccess>;
 }
 
+/**
+ * Whether the Vite+ banner should be emitted in the current environment.
+ *
+ * Mirrors `vite_shared::header::should_print_header` so both CLIs apply
+ * the same TTY + git-hook gating without duplicating the rules in JS.
+ */
+export declare function shouldPrintVitePlusHeader(): boolean;
+
 /** Render the Vite+ header using the Rust implementation. */
 export declare function vitePlusHeader(): string;

packages/cli/binding/src/lib.rs

@@ -215,3 +215,12 @@ pub async fn run(options: CliOptions) -> Result<i32> {
 pub fn vite_plus_header() -> String {
     vite_shared::header::vite_plus_header()
 }
+
+/// Whether the Vite+ banner should be emitted in the current environment.
+///
+/// Mirrors `vite_shared::header::should_print_header` so both CLIs apply
+/// the same TTY + git-hook gating without duplicating the rules in JS.
+#[napi]
+pub fn should_print_vite_plus_header() -> bool {
+    vite_shared::header::should_print_header()
+}

packages/cli/src/utils/terminal.ts

@@ -1,6 +1,6 @@
 import { styleText } from 'node:util';
 
-import { vitePlusHeader } from '../../binding/index.js';
+import { shouldPrintVitePlusHeader, vitePlusHeader } from '../../binding/index.js';
 
 export function log(message: string) {
   /* oxlint-disable-next-line no-console */
@@ -9,19 +9,11 @@ export function log(message: string) {
 
 /**
  * Emit the Vite+ banner (header line + trailing blank line) to stdout.
- *
- * Silent when:
- * - stdout is piped or redirected (lefthook/husky, `execSync`, CI, pagers) —
- *   the banner's ANSI styling renders inconsistently there.
- * - a git commit-flow hook is running. Direct shell hooks inherit the
- *   terminal for stdout, so the TTY check alone doesn't catch them; git
- *   sets `GIT_INDEX_FILE` for pre-commit / commit-msg / prepare-commit-msg.
+ * Gating (non-TTY, git hooks) lives in `shouldPrintVitePlusHeader` on the
+ * Rust side so both CLIs stay in sync.
  */
 export function printHeader() {
-  if (!process.stdout.isTTY) {
-    return;
-  }
-  if (process.env.GIT_INDEX_FILE) {
+  if (!shouldPrintVitePlusHeader()) {
     return;
   }
   log(vitePlusHeader());