0ecfcc2881
Commit desktop bundles can bake environment defaults/clears (--bundle-unset HERMES_DESKTOP_USER_DATA_DIR, HERMES_HOME=null) that stomp the smoke driver's --home/--user-data pin, so every native smoke threw "Desktop did not honor the isolated home and userData directories". Instead of pinning, the driver replays the bundle env over its launch env through the same resolver the app runs, seeds the predicted home (bailing rather than wiping when it is not empty), and verifies the app landed there via a new hermesHome report on the version bridge. The --user-data equality check now applies only when the artifact bakes no env. - Extract the pure path resolver into electron/data-paths.mjs (data-paths.ts is now a typed re-export) so Node's type-stripped driver can import it. - Add applyBundleEnvironment/validateBundleEnvironment as the pure twin of the bundle banner, pinned by a lockstep test. - Record bundleEnv in the install stamp and add readBundledBundleEnv. - Report hermesHome from hermes:version and assert it equals the predicted home.
7 lines
464 B
TypeScript
7 lines
464 B
TypeScript
// data-paths.ts — typed re-export of the shared pure resolver in data-paths.mjs.
|
|
// The app imports these names here (extensionless, for the tsc/esbuild build);
|
|
// the CI smoke driver imports the .mjs directly because Node's type-stripping
|
|
// cannot resolve extensionless TypeScript imports.
|
|
export { platformDefaultHermesHome, resolveDesktopHermesHome, resolveDesktopUserData } from './data-paths.mjs'
|
|
export type { HermesHomeOptions } from './data-paths.mjs'
|