Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

NVM fails to install node when passed a SemVer range.

Open Beginner friendly
  • Is something wrong?
#42,543 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Shadaan786 is already working on this.

Since Oct 3, 2026.

  • #42544 by @Shadaan786 — open
  • #42548 by @schizophrenicmaniac — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
bash, docker, node.js
Domain
devops, infrastructure

Research direction

Start by reading .devcontainer/Dockerfile and .gitpod/.gitpod.yml, where the issue reports passing engines.node to nvm install; check how the value is read and used. Reproduce the container build or Codespaces setup, and consider the work done when the semantic version range no longer causes shell errors and the container builds successfully.

Written by the indexing model from the issue text.

Description

type: bug
Description:

When a semantic version range such as >=22.22.3 <23 || >=24.15.0 <25 is passed to NVM then NVM fails to install the Node.js because the value of engines.node in package.json is a semantic version range, while development environment needs to pass a concrete Node.js version to nvm install rather than a range of version, also the unquoted command substitution causes bash to interpret the parts of semantic version range as shell operators resulting in errors such as:

3.269 bash: line 1: 23: No such file or directory
3.270 bash: line 1: 25: No such file or directory

Because bash interprets < to take input from a file or can say input redirection operator.

Steps to reproduce:
  1. Start a dev container using .devcontainer/Dockerfile or create a github codespaces.
  2. During the container build, the Node.js version is read from engines.node in package.json.
  3. The resulting semantic version range is passed to nvm install.
  4. Observe the No such file or directory errors as mentioned above.
Expected behavior:

No errors like No such file/directory or not being ended in recovery container, the Dockerfile should be builded successfully.

Actual behavior:
Image

The error logs shows up when buildng the container using node semantic versioning range or in github codespaces, which results in failure to build the container or end up in recovery container in codespaces.

Server Setup Information:
  • Version of Rocket.Chat Server: N/A
  • License Type: N/A
  • Number of Users: N/A
  • Operating System: Ubuntu 22.04.5 LTS
  • Deployment Method: Docker / Dev container / github codespaces
  • Number of Running Instances: N/A
  • DB Replicaset Oplog: N/A
  • NodeJS Version: 24.15.0
  • MongoDB Version: N/A
Additional context

The issue was reproduced locally by passing the value of engines.node to nvm install in .gitpod/.gitpod.yml and .devcontainer/Dockerfile

Relevant logs:
bash: line 1: 23: No such file or directory
bash: line 1: 25: No such file or directory
Dominant language
TypeScript
Stars
46.3k
Forks
14k
Avg merge
2d 12h
Merged PRs (30d)
271

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RocketChat/Rocket.Chat

All issues in RocketChat/Rocket.Chat

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.