Archive Node.js versions 20.19.5 and 22.21.1, add npmrc configuration for 24.11.1

[N6REJ]

User description

fixes missing node_modules config file(s)

---

PR Type

Enhancement, Configuration changes

---

Description

• Add npmrc configuration files for Node.js 24.11.1

• Add npmrc configuration files for Node.js 25.2.1

• Update bundle release version to 2025.12.30

---

Diagram Walkthrough

flowchart LR
  A["Node.js 24.11.1"] --> B["npmrc config files"]
  C["Node.js 25.2.1"] --> D["npmrc config files"]
  E["build.properties"] --> F["Release 2025.12.30"]

Loading

File Walkthrough

	Relevant files
Configuration changes	5 files npmrc Add npmrc configuration for Node.js 24.11.1                            +1/-0      npmrc.ber Add npmrc backup configuration for Node.js 24.11.1              +1/-0      npmrc Add npmrc configuration for Node.js 25.2.1                              +1/-0      npmrc.ber Add npmrc backup configuration for Node.js 25.2.1                +1/-0      build.properties Update bundle release version to 2025.12.30                            +1/-1
Additional files	8 files bearsampp.conf [link]    npmrc [link]    npmrc.ber [link]    launch.bat [link]    bearsampp.conf [link]    npmrc [link]    npmrc.ber [link]    launch.bat [link]

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
🔴	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Misleading prefix path: The added prefix value under bin/nodejs24.11.1/... points to nodejs25.11.1, making the configuration misleading and not self-documenting for the intended Node.js version. Referred Code prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\ Learn more about managing compliance generic rules or creating your own custom rules
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Latest suggestions up to 4a2c5f4

Category	Suggestion	Impact
Possible issue	Align prefix with bundled version Correct the prefix path in npmrc to point to the nodejs24.11.1 directory instead of nodejs25.11.1. bin/nodejs24.11.1/node_modules/npm/npmrc [1] -prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\ +prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs24.11.1\ Apply / Chat Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a critical bug where the npmrc configuration file for nodejs24.11.1 incorrectly points to the nodejs25.11.1 directory, which would lead to incorrect behavior when installing global npm packages.	High
	Keep both configs consistent Correct the prefix path in npmrc.ber to point to the nodejs24.11.1 directory instead of nodejs25.11.1 for consistency. bin/nodejs24.11.1/node_modules/npm/npmrc.ber [1] -prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\ +prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs24.11.1\ Apply / Chat Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a critical bug in the npmrc.ber file, mirroring the issue in the npmrc file. Fixing this ensures consistent and correct behavior for npm package installations across different configurations.	High
More

---

Previous suggestions

Suggestions up to commit 5b6b101

Category	Suggestion	Impact
Possible issue	Correct version in npm configuration Correct the version in the prefix path of the npmrc file from 25.11.1 to 24.11.1 to match its directory. bin/nodejs24.11.1/node_modules/npm/npmrc [1] -prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\ +prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs24.11.1\ Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a critical copy-paste error in the prefix path which would break npm functionality for this Node.js version.	High
	Fix version in .npmrc.ber prefix Correct the version in the prefix path of the npmrc.ber file from 25.11.1 to 24.11.1 to match its directory. bin/nodejs24.11.1/node_modules/npm/npmrc.ber [1] -prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\ +prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs24.11.1\ Suggestion importance[1-10]: 9 __ Why: The suggestion correctly identifies a critical copy-paste error in the prefix path which would break npm functionality for this Node.js version.	High

[qodo-code-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Wrong Path The configured prefix appears to point to a different Node.js version directory than the file’s own versioned path, which may cause npm global installs to be redirected to the wrong runtime folder. prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\ Wrong Path The configured prefix appears to point to a different Node.js version directory than the file’s own versioned path, which may cause npm global installs to be redirected to the wrong runtime folder. prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\ Config Consistency Validate whether the prefix value and trailing backslash formatting are consistent with how other bundles resolve ~BEARSAMPP_WIN_PATH~ and whether escaping/backslash handling is correct for npmrc parsing on Windows. prefix = ~BEARSAMPP_WIN_PATH~\bin\nodejs\nodejs25.11.1\