fix(vite): build/prepare handling for the bundle

Author: NathanWalker

lib/constants.ts

@@ -17,6 +17,11 @@ export const TNS_CORE_THEME_NAME = "nativescript-theme-core";
 export const SCOPED_TNS_CORE_THEME_NAME = "@nativescript/theme";
 export const WEBPACK_PLUGIN_NAME = "@nativescript/webpack";
 export const RSPACK_PLUGIN_NAME = "@nativescript/rspack";
+// Project-relative directory the Vite bundler writes its build output to
+// before the CLI copies it into the platforms app folder. Mirrors the
+// default value computed in `@nativescript/vite`'s base configuration
+// (`process.env.NS_VITE_DIST_DIR || '.ns-vite-build'`).
+export const VITE_DIST_FOLDER_NAME = ".ns-vite-build";
 export const TNS_CORE_MODULES_WIDGETS_NAME = "tns-core-modules-widgets";
 export const UI_MOBILE_BASE_NAME = "@nativescript/ui-mobile-base";
 export const TNS_ANDROID_RUNTIME_NAME = "tns-android";
@@ -172,9 +177,7 @@ export class ITMSConstants {
 	static altoolExecutableName = "altool";
 }
 
-class ItunesConnectApplicationTypesClass
-	implements IiTunesConnectApplicationType
-{
+class ItunesConnectApplicationTypesClass implements IiTunesConnectApplicationType {
 	public iOS = "iOS App";
 	public Mac = "Mac OS X App";
 }
@@ -409,7 +412,7 @@ export enum IOSNativeTargetTypes {
 	watchApp = "watch_app",
 	watchExtension = "watch_extension",
 	appExtension = "app_extension",
-	application = 'application',
+	application = "application",
 }
 
 const pathToLoggerAppendersDir = join(

lib/services/bundler/bundler-compiler-service.ts

@@ -9,6 +9,7 @@ import {
 	BUNDLER_COMPILATION_COMPLETE,
 	PackageManagers,
 	CONFIG_FILE_NAME_DISPLAY,
+	VITE_DIST_FOLDER_NAME,
 } from "../../constants";
 import {
 	IPackageManager,
@@ -128,7 +129,7 @@ export class BundlerCompilerService
 						// Copy Vite output files directly to platform destination
 						const distOutput = path.join(
 							projectData.projectDir,
-							".ns-vite-build",
+							VITE_DIST_FOLDER_NAME,
 						);
 						const destDir = path.join(
 							platformData.appDestinationDirectoryPath,
@@ -373,6 +374,8 @@ export class BundlerCompilerService
 					reject(err);
 				});
 
+				const isVite = this.getBundler() === "vite";
+
 				childProcess.on("close", async (arg: any) => {
 					await this.$cleanupService.removeKillProcess(
 						childProcess.pid.toString(),
@@ -381,6 +384,34 @@ export class BundlerCompilerService
 					delete this.bundlerProcesses[platformData.platformNameLowerCase];
 					const exitCode = typeof arg === "number" ? arg : arg && arg.code;
 					if (exitCode === 0) {
+						// Non-watch Vite builds spawn the child with stdio:"inherit"
+						// (no IPC channel), so the emittedFiles message handler in
+						// compileWithWatch never fires and the Vite output is never
+						// copied to the platforms app folder. Mirror that copy step
+						// here so release/CI prepare and build flows actually deploy
+						// the freshly built bundle. Without this, the deploy folder
+						// is left empty (or worse, runs stale dev/HMR artifacts from
+						// a previous `ns debug` run) and the runtime crashes on
+						// launch with `Check failed: has_pending_exception()`.
+						if (isVite) {
+							try {
+								const distOutput = path.join(
+									projectData.projectDir,
+									VITE_DIST_FOLDER_NAME,
+								);
+								const destDir = path.join(
+									platformData.appDestinationDirectoryPath,
+									this.$options.hostProjectModuleName,
+								);
+								this.copyViteBundleToNative(distOutput, destDir);
+							} catch (copyErr) {
+								this.$logger.warn(
+									`Failed to copy Vite output to platform destination: ${
+										(copyErr as Error).message
+									}`,
+								);
+							}
+						}
 						resolve();
 					} else {
 						const error: any = new Error(