Flow-Launcher/Flow.Launcher

End-of-life version of NodeJS

Open

#3,100 创建于 2024年11月27日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)C# (14,678 star) (598 fork)batch import
bughelp wantedkeep-fresh

描述

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

贡献者指南

技术栈
nodejs
领域
backend
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
under 1 hour
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
active
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
无
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
85
研究方向
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.
End-of-life version of NodeJS · Flow-Launcher/Flow.Launcher#3100 | Good First Issue