Conversation
… and npmrc configuration
Review Summary by QodoAdd Node.js versions 25.8.0, 24.14.0, and 22.22.1 with configurations
WalkthroughsDescription• Add Node.js versions 25.8.0, 24.14.0, and 22.22.1 • Create launch scripts and configuration files for new versions • Update release properties with download URLs for new versions • Update bundle release date to 2026.3.7 Diagramflowchart LR
A["New Node.js Versions<br/>25.8.0, 24.14.0, 22.22.1"] --> B["Launch Scripts<br/>launch.bat"]
A --> C["Configuration Files<br/>bearsampp.conf, npmrc"]
B --> D["Environment Setup<br/>npm config"]
C --> E["npm Paths & Cache<br/>etc/npmrc"]
F["releases.properties"] --> G["Download URLs<br/>2026.3.7 release"]
H["build.properties"] --> I["Bundle Date Update<br/>2026.3.7"]
File Changes1. bin/nodejs22.22.1/launch.bat
|
Code Review by Qodo
1. Unquoted npmrc redirection
|
| ECHO prefix = %BEARSAMPP_NODEJS_PATH%>%BEARSAMPP_NODEJS_CONFIG_PATH% | ||
|
|
||
| "%BEARSAMPP_NODEJS_PATH%\nodevars.bat" & "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global |
There was a problem hiding this comment.
1. Unquoted npmrc redirection 🐞 Bug ⛯ Reliability
Newly added launch.bat files write npmrc via unquoted output redirection, which will break when the install path contains spaces (common on Windows), causing npm prefix/globalconfig setup to fail.
Agent Prompt
## Issue description
`launch.bat` writes to `%BEARSAMPP_NODEJS_CONFIG_PATH%` using an unquoted redirection target. This can fail when the Bearsampp install path contains spaces.
## Issue Context
This PR adds new `launch.bat` files for Node.js 22.22.1 / 24.14.0 / 25.8.0. The same repo already contains a safer quoted redirection pattern in `bin/archived/nodejs20.19.5/launch.bat`.
## Fix Focus Areas
- bin/nodejs22.22.1/launch.bat[4-11]
- bin/nodejs24.14.0/launch.bat[4-11]
- bin/nodejs25.8.0/launch.bat[4-11]
ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools
No description provided.