Flow-Launcher/Flow.Launcher

End-of-life version of NodeJS

Open

#3100 opened on Nov 27, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (14,678 stars) (598 forks)batch import
bughelp wantedkeep-fresh

Description

Checks

  • I have checked that this issue has not already been reported.
  • I am using the latest version of Flow Launcher.

Problem Description

When installing a Node plugin, Flow Launcher v1.19.4 downloads Node v16. Node v16 reached end-of-life status in September 2023, so the version Flow downloads should be updated. I propose to skip v18 as it'll reach EOL status very soon, in April 2025. Current LTS versions are v20 (EOL in April 2026) and v22 (EOL in April 2027). More info on Node versions is available here.

Flow Launcher Version

1.19.4

Contributor guide

Tech stack
nodejs
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
The issue is straightforward: update the Node.js version downloaded by Flow Launcher for Node plugins. The current version is Node v16, which is end of life. The reporter suggests skipping v18 and using v20 or v22. To resolve, locate where the Node.js download URL or version is configured in the codebase (likely in a script or configuration file, e.g., a download step in the plugin installer). Check the repository's code, possibly in a file related to plugin installation or Node.js management. Update the version to v20 or v22, ensuring the download URL is correct. Also consider the release schedule provided in the issue: https://github.com/nodejs/release#release schedule.