Skip to content

NodeJS 25.8.0, 24.14.0, and 22.22.1 #34

Merged
N6REJ merged 1 commit intomainfrom
march
Mar 8, 2026
Merged

NodeJS 25.8.0, 24.14.0, and 22.22.1 #34
N6REJ merged 1 commit intomainfrom
march

Conversation

@jwaisner
Copy link
Contributor

@jwaisner jwaisner commented Mar 8, 2026

No description provided.

@jwaisner jwaisner requested a review from N6REJ as a code owner March 8, 2026 06:04
@jwaisner jwaisner added the enhancement ✨ Improve program label Mar 8, 2026
@qodo-code-review
Copy link
Contributor

Review Summary by Qodo

Add Node.js versions 25.8.0, 24.14.0, and 22.22.1 with configurations

✨ Enhancement

Grey Divider

Walkthroughs

Description
• 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
Diagram
flowchart 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"]
Loading

Grey Divider

File Changes

1. bin/nodejs22.22.1/launch.bat ⚙️ Configuration changes +12/-0

Windows launch script for Node.js 22.22.1

bin/nodejs22.22.1/launch.bat


2. bin/nodejs24.14.0/launch.bat ⚙️ Configuration changes +12/-0

Windows launch script for Node.js 24.14.0

bin/nodejs24.14.0/launch.bat


3. bin/nodejs25.8.0/launch.bat ⚙️ Configuration changes +12/-0

Windows launch script for Node.js 25.8.0

bin/nodejs25.8.0/launch.bat


View more (23)
4. bin/nodejs22.22.1/bearsampp.conf ⚙️ Configuration changes +8/-0

Bearsampp configuration for Node.js 22.22.1

bin/nodejs22.22.1/bearsampp.conf


5. bin/nodejs22.22.1/etc/npmrc ⚙️ Configuration changes +4/-0

npm configuration for Node.js 22.22.1

bin/nodejs22.22.1/etc/npmrc


6. bin/nodejs22.22.1/etc/npmrc.ber ⚙️ Configuration changes +4/-0

npm template configuration for Node.js 22.22.1

bin/nodejs22.22.1/etc/npmrc.ber


7. bin/nodejs22.22.1/node_modules/npm/npmrc ⚙️ Configuration changes +1/-0

npm prefix configuration for Node.js 22.22.1

bin/nodejs22.22.1/node_modules/npm/npmrc


8. bin/nodejs22.22.1/node_modules/npm/npmrc.ber ⚙️ Configuration changes +1/-0

npm prefix template for Node.js 22.22.1

bin/nodejs22.22.1/node_modules/npm/npmrc.ber


9. bin/nodejs24.14.0/bearsampp.conf ⚙️ Configuration changes +8/-0

Bearsampp configuration for Node.js 24.14.0

bin/nodejs24.14.0/bearsampp.conf


10. bin/nodejs24.14.0/etc/npmrc ⚙️ Configuration changes +4/-0

npm configuration for Node.js 24.14.0

bin/nodejs24.14.0/etc/npmrc


11. bin/nodejs24.14.0/etc/npmrc.ber ⚙️ Configuration changes +4/-0

npm template configuration for Node.js 24.14.0

bin/nodejs24.14.0/etc/npmrc.ber


12. bin/nodejs24.14.0/node_modules/npm/npmrc ⚙️ Configuration changes +1/-0

npm prefix configuration for Node.js 24.14.0

bin/nodejs24.14.0/node_modules/npm/npmrc


13. bin/nodejs24.14.0/node_modules/npm/npmrc.ber ⚙️ Configuration changes +1/-0

npm prefix template for Node.js 24.14.0

bin/nodejs24.14.0/node_modules/npm/npmrc.ber


14. bin/nodejs25.8.0/bearsampp.conf ⚙️ Configuration changes +8/-0

Bearsampp configuration for Node.js 25.8.0

bin/nodejs25.8.0/bearsampp.conf


15. bin/nodejs25.8.0/etc/npmrc ⚙️ Configuration changes +4/-0

npm configuration for Node.js 25.8.0

bin/nodejs25.8.0/etc/npmrc


16. bin/nodejs25.8.0/etc/npmrc.ber ⚙️ Configuration changes +4/-0

npm template configuration for Node.js 25.8.0

bin/nodejs25.8.0/etc/npmrc.ber


17. bin/nodejs25.8.0/node_modules/npm/npmrc ⚙️ Configuration changes +1/-0

npm prefix configuration for Node.js 25.8.0

bin/nodejs25.8.0/node_modules/npm/npmrc


18. bin/nodejs25.8.0/node_modules/npm/npmrc.ber ⚙️ Configuration changes +1/-0

npm prefix template for Node.js 25.8.0

bin/nodejs25.8.0/node_modules/npm/npmrc.ber


19. bin/nodejs20.19.5/node_modules/npm/npmrc ⚙️ Configuration changes +1/-0

npm prefix configuration for Node.js 20.19.5

bin/nodejs20.19.5/node_modules/npm/npmrc


20. bin/nodejs20.19.5/node_modules/npm/npmrc.ber ⚙️ Configuration changes +1/-0

npm prefix template for Node.js 20.19.5

bin/nodejs20.19.5/node_modules/npm/npmrc.ber


21. bin/nodejs24.11.1/node_modules/npm/npmrc ⚙️ Configuration changes +1/-0

npm prefix configuration for Node.js 24.11.1

bin/nodejs24.11.1/node_modules/npm/npmrc


22. bin/nodejs24.11.1/node_modules/npm/npmrc.ber ⚙️ Configuration changes +1/-0

npm prefix template for Node.js 24.11.1

bin/nodejs24.11.1/node_modules/npm/npmrc.ber


23. build.properties ⚙️ Configuration changes +1/-1

Update bundle release date to 2026.3.7

build.properties


24. releases.properties ⚙️ Configuration changes +3/-0

Add download URLs for three new Node.js versions

releases.properties


25. bin/nodejs22.21.1/node_modules/npm/npmrc Additional files +1/-0

...

bin/nodejs22.21.1/node_modules/npm/npmrc


26. bin/nodejs22.21.1/node_modules/npm/npmrc.ber Additional files +1/-0

...

bin/nodejs22.21.1/node_modules/npm/npmrc.ber


Grey Divider

Qodo Logo

@qodo-code-review
Copy link
Contributor

qodo-code-review bot commented Mar 8, 2026

Code Review by Qodo

🐞 Bugs (3) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider


Action required

1. Unquoted npmrc redirection 🐞 Bug ⛯ Reliability
Description
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.
Code

bin/nodejs25.8.0/launch.bat[R8-10]

+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
Evidence
The launcher writes to %BEARSAMPP_NODEJS_CONFIG_PATH% using > without quoting the destination
path. If Bearsampp is installed under a path with spaces, cmd redirection can mis-parse the target
file path. The repo already contains an example of a safer quoted redirection pattern in an archived
version, indicating this is a known robustness requirement.

bin/nodejs25.8.0/launch.bat[4-12]
bin/nodejs24.14.0/launch.bat[4-11]
bin/nodejs22.22.1/launch.bat[4-11]
bin/archived/nodejs20.19.5/launch.bat[6-10]

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

## 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



Remediation recommended

2. Inconsistent npm entrypoint 🐞 Bug ✓ Correctness
Description
bearsampp.conf declares npm.cmd, but launch.bat invokes an explicit path to npm (no extension).
This inconsistency increases the chance of environment-specific failures and makes the bundle
behavior harder to reason about.
Code

bin/nodejs25.8.0/launch.bat[10]

+"%BEARSAMPP_NODEJS_PATH%\nodevars.bat" & "%BEARSAMPP_NODEJS_PATH%\npm" config set globalconfig "%BEARSAMPP_NODEJS_CONFIG_PATH%" --global
Evidence
Within the same version overlay, configuration says the npm executable is npm.cmd while the
launcher calls ...\npm. The packaging docs explicitly distinguish npm vs npm.cmd (Windows
command), so it’s clearer/safer to be consistent and call npm.cmd from the batch file (or update
config if the intent is otherwise).

bin/nodejs25.8.0/bearsampp.conf[1-6]
bin/nodejs25.8.0/launch.bat[8-10]
.gradle-docs/PACKAGING.md[14-20]

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

## Issue description
`bearsampp.conf` and `launch.bat` disagree on the npm entrypoint (`npm.cmd` vs `npm`). Even if it works in many environments, it’s inconsistent and can lead to environment-specific failures.

## Issue Context
Packaging docs explicitly list `npm` and `npm.cmd` separately, where `npm.cmd` is the Windows command.

## Fix Focus Areas
- bin/nodejs22.22.1/launch.bat[8-10]
- bin/nodejs24.14.0/launch.bat[8-10]
- bin/nodejs25.8.0/launch.bat[8-10]
- bin/nodejs22.22.1/bearsampp.conf[1-6]
- bin/nodejs24.14.0/bearsampp.conf[1-6]
- bin/nodejs25.8.0/bearsampp.conf[1-6]

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


3. Bin overrides archived overlay 🐞 Bug ⛯ Reliability
Description
This PR adds files under bin/ for versions that also exist under bin/archived/ (20.19.5, 22.21.1).
The Gradle release task always prefers bin/ when both exist, so the archived overlay may be silently
ignored, producing inconsistent artifacts for those versions.
Code

bin/nodejs20.19.5/node_modules/npm/npmrc[1]

+prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs20.19.5\
Evidence
The release task resolves bundlePath from bin/ first and only falls back to bin/archived if the bin/
directory doesn’t exist. After this PR, these versions clearly have content in bin/ (new npmrc)
while archived contains their module overlay config (bearsampp.conf, launch.bat, etc). That means
the release build will deterministically select the bin/ variant even if archived is the intended
overlay for that version.

build.gradle[441-448]
bin/nodejs20.19.5/node_modules/npm/npmrc[1-1]
bin/archived/nodejs20.19.5/bearsampp.conf[1-6]
bin/nodejs22.21.1/node_modules/npm/npmrc[1-1]
bin/archived/nodejs22.21.1/bearsampp.conf[1-6]

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

## Issue description
Versions 20.19.5 and 22.21.1 have overlay content in both `bin/` and `bin/archived/`, and the build always prefers `bin/`. This can lead to inconsistent artifacts and silently ignore the archived overlay.

## Issue Context
This PR adds npmrc templates into `bin/nodejs20.19.5` and `bin/nodejs22.21.1`, while `bin/archived/...` already contains the version’s `bearsampp.conf` (and likely other overlay files).

## Fix Focus Areas
- build.gradle[441-448]
- bin/nodejs20.19.5/node_modules/npm/npmrc[1-1]
- bin/nodejs22.21.1/node_modules/npm/npmrc[1-1]
- bin/archived/nodejs20.19.5/bearsampp.conf[1-8]
- bin/archived/nodejs22.21.1/bearsampp.conf[1-8]

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


Grey Divider

ⓘ The new review experience is currently in Beta. Learn more

Grey Divider

Qodo Logo

Comment on lines +8 to +10
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
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

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

@N6REJ N6REJ merged commit aa0ffb2 into main Mar 8, 2026
4 checks passed
@N6REJ N6REJ deleted the march branch March 8, 2026 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement ✨ Improve program

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants