Skip to content

fix: expose store node_modules via NODE_PATH for linked-strategy install scripts#9578

Merged
owlstronaut merged 1 commit into
release/v11from
backport/v11/9551
Jun 18, 2026
Merged

fix: expose store node_modules via NODE_PATH for linked-strategy install scripts#9578
owlstronaut merged 1 commit into
release/v11from
backport/v11/9551

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Backport of #9551 to release/v11.

…ategy install scripts (#9551)

In continuation of our exploration of using `install-strategy=linked` in
the [Gutenberg
monorepo](WordPress/gutenberg#75814), which
powers the WordPress Block Editor.

Under `install-strategy=linked`, a package whose install script invokes
a separate helper bin to locate a native binding fails (e.g.
`unrs-resolver` via `napi-postinstall`, and the wider `napi-postinstall`
family). The helper bin is reached via a `.bin` symlink, so Node
resolves it to its own realpath in its own store dir, from which it
can't `require.resolve` the host's binding — so it declares it missing
and re-downloads (fatal on a restricted registry/proxy). Hoisted works
because the binding is hoisted onto the helper's resolution path.

## How

When running a store node's lifecycle script, set `NODE_PATH` to the
host package's store `node_modules` so a script-invoked bin can resolve
the host's sibling deps:

```js
if (isInStore) {
  const storeNodeModules = resolve(path, ...name.split('/').map(() => '..'))
  env.NODE_PATH = [storeNodeModules, process.env.NODE_PATH].filter(Boolean).join(delimiter)
}
```

`NODE_PATH` is fallback-only (can't shadow working resolution), added
only to the script's env (never `process.env`), and scoped to the
store-local `node_modules` — install-time only, runtime isolation
untouched.

## References

Fixes #9549

(cherry picked from commit afce424)
@owlstronaut owlstronaut changed the title fix(arborist): expose store node_modules via NODE_PATH for linked-strategy install scripts fix: expose store node_modules via NODE_PATH for linked-strategy install scripts Jun 18, 2026
@owlstronaut owlstronaut merged commit aaeb2f1 into release/v11 Jun 18, 2026
33 of 34 checks passed
@owlstronaut owlstronaut deleted the backport/v11/9551 branch June 18, 2026 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants