Update npmrc prefix configuration for Node.js 26.3.0

[N6REJ]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Update npm prefix configuration for Node.js 26.3.0

✨ Enhancement

Walkthroughs

Description

• Update npm prefix path from Node.js 25.9.0 to 26.3.0
• Synchronize configuration across npmrc files

Diagram

flowchart LR
  old["nodejs25.9.0 prefix path"]
  new["nodejs26.3.0 prefix path"]
  npmrc["npmrc files"]
  old -- "update version" --> new
  new -- "applied to" --> npmrc

Loading

File Changes

1. bin/nodejs26.3.0/node_modules/npm/npmrc ⚙️ Configuration changes +1/-1

Update npm prefix to Node.js 26.3.0

• Updated npm prefix path from nodejs25.9.0 to nodejs26.3.0
• Maintains placeholder variable ~BEARSAMPP_WIN_PATH~ for dynamic path resolution

bin/nodejs26.3.0/node_modules/npm/npmrc

---

2. bin/nodejs26.3.0/node_modules/npm/npmrc.ber ⚙️ Configuration changes +1/-1

Update npm prefix to Node.js 26.3.0

• Updated npm prefix path from nodejs25.9.0 to nodejs26.3.0
• Maintains placeholder variable ~BEARSAMPP_WIN_PATH~ for dynamic path resolution

bin/nodejs26.3.0/node_modules/npm/npmrc.ber

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 🔗 Cross-repo conflicts (0)

1. npmrc overwritten at runtime 🐞 Bug ≡ Correctness

Description

bin/nodejs26.3.0/launch.bat truncates and rewrites node_modules/npm/npmrc with a computed prefix
each time it runs, so the hardcoded prefix updated in this PR will not be the effective
configuration when using the launcher. If the intent is to change runtime prefix behavior, the
change must be applied to the launcher (or the launcher must stop overwriting npmrc).

Code

bin/nodejs26.3.0/node_modules/npm/npmrc[1]

Evidence

The updated npmrc prefix line from the PR is overwritten by the launcher: launch.bat writes a new
prefix = ... line into the same node_modules/npm/npmrc file using > redirection, which
truncates/overwrites the file content.

bin/nodejs26.3.0/node_modules/npm/npmrc[1-1]
bin/nodejs26.3.0/launch.bat[4-10]
bin/nodejs26.3.0/bearsampp.conf[1-7]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
The PR updates the hardcoded `prefix` in `node_modules/npm/npmrc`, but `bin/nodejs26.3.0/launch.bat` overwrites that file on each run (`>` redirection). As a result, the PR’s change may not impact the effective npm prefix when Node/npm is started via the launcher.

### Issue Context
- `launch.bat` computes `BEARSAMPP_NODEJS_PATH` from `%~dp0` and writes `prefix = <computed>` into `node_modules/npm/npmrc`.
- `bearsampp.conf` indicates the Node.js bundle references `launch.bat` and `node_modules/npm/npmrc`.

### Fix Focus Areas
- bin/nodejs26.3.0/launch.bat[4-10]
- bin/nodejs26.3.0/node_modules/npm/npmrc[1-1]
- bin/nodejs26.3.0/bearsampp.conf[1-7]

### Suggested fix approaches (choose one)
1) **Single source of truth = launcher**: keep the launcher overwrite behavior, and adjust packaging/docs so updating the checked-in `npmrc` is not treated as the runtime mechanism (optionally remove the hardcoded prefix from the checked-in npmrc to avoid drift).
2) **Single source of truth = checked-in npmrc**: change `launch.bat` to stop overwriting `npmrc` (or only write it if missing) so the committed prefix is actually used at runtime.
3) If both `npmrc` and `npmrc.ber` are intended to be used, ensure the launcher updates both consistently (currently it only writes `npmrc`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---