Printable idea sheet
extension_host_native_stage
reqlan rq/development/build.rq:46
Katz 0.140
Local F5 and `pnpm run build` / `build:ext` stage the host-matching core engine `.node` into `packages/extension/native/` so activation loads the same layout as a per-target VSIX ( vsix_export, native_host_binary_development ).
The same build copies the `.node` into `packages/analytical-native/<napiSuffix>/` so the workspace optionalDependency matches a production npm install ( rust_binary_distribution ).
The orchestrator builds `cargo build -p reqlan-napi -p reqlan-lsp --release` when needed, then copies `reqlan_napi.node` beside the extension. It is not a separate manual install.
That command writes `reqlan-lsp` into `crates/target` ( language_server_rust ).
Azure compiles the native_targets matrix, then stages those binaries with `prepare-native-packages.mjs --binary-dir` before tests and VSIX packaging. Versions come from git at the `ext/v*` tag. Do not fetch platform packages from npm on Azure ( extension_distribution ).
Implementation: stage-host-native.mjs, ensure-host-native.mjs, build.mjs, azure-pipelines.yml.
- status
- done
Interactive page: extension_host_native_stage