Install / run failed - feedback Hy3

[p2pfiat]

App

Build / packaging

Version and OS

Windows 11 - ARM

What happened?

Make npm run dev cross-platform — replace the inline VAR=... npm run prefix with cross-env (add it to devDependencies). Don't rely on the user's shell being POSIX.
Don't depend on script-shell in a project .npmrc — npm ignores it for security, so it can't fix the Windows shell issue. cross-env is the real fix.
Pin @univerjs/preset-sheets-drawing consistently — the app imports preset-sheets-drawing/locales/*, which only exists in the 0.25.x line, not 0.5.0. Add a test or exports-map check so a wrong version fails fast in CI instead of at runtime.
Add a Windows CI lane (or at least a smoke test of npm run dev) so POSIX-only scripts get caught before release.
Document the ARM64/Windows setup in CONTRIBUTING (git-bash requirement, Rust toolchain for the sheets sidecar) so the next Windows user isn't debugging the same thing.

Logs / screenshots

No response

[p2pfiat]

The dev script uses POSIX shell syntax (VAR=... npm run), which works on macOS/Linux and on Windows only if npm is invoked from a POSIX shell (git-bash). Your terminal ran npm through cmd.exe, so the env-var prefix blew up. The ^0.5.0 sheets dependency was a local edit on your machine — that version lacks the /locales/* subpaths the code imports, so it crashed only for you. ARM64 was a red herring; Electron 43 and the Rust sidecar run fine under emulation.