deepseek-ai/awesome-deepseek-agent

Fork 0

mirror of https://github.com/deepseek-ai/awesome-deepseek-agent.git synced 2026-11-05 01:07:37 +00:00

[PR #424] docs(qwen_code): the npm install path needs Node 22, not 20 #422

New issue

Open

opened 2026-10-26 09:49:04 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-26 09:49:04 +00:00

Owner

📋 Pull Request Information

Original PR: https://github.com/deepseek-ai/awesome-deepseek-agent/pull/424
Author: @PerryLink
Created: 9/23/2026
Status: 🔄 Open

Base: main ← Head: docs-qwen-node22

📝 Commits (1)

39e9fba docs(qwen_code): the npm install path needs Node 22, not 20

📊 Changes

2 files changed (+2 additions, -2 deletions)

View changed files

📝 docs/qwen_code.md (+1 -1)
📝 docs/qwen_code.zh-CN.md (+1 -1)

📄 Description

What

The guide's first prerequisite, on line 12 of both halves, says "Install Node.js 20 or later", and the next line installs @qwen-code/qwen-code@latest. That package's latest release refuses to install on Node 20:

$ npm view @qwen-code/qwen-code@latest engines
{ node: '>=22.0.0' }

So a reader who follows the guide literally hits an EBADENGINE refusal on the very next command.

Change

20 → 22 on line 12 of docs/qwen_code.md and docs/qwen_code.zh-CN.md. One line per file, nothing else changed.

Why 22 and not something else

@qwen-code/qwen-code@0.24.4 is latest and declares "node": ">=22.0.0". The upstream README agrees — its badge reads node-%3E%3D22.0.0 and line 53 says "NPM (requires Node.js 22+)".

Scoped to the npm path on purpose

Upstream scopes it the same way: its README line 53 reads "NPM (requires Node.js 22+)", attaching the requirement to the npm route only, while this guide's other routes are the quick-install script and brew install qwen-code. If you would rather the bullet carry that qualification explicitly, I am happy to reword it instead.

On the "20" being there in the first place

It was correct when written: the requirement moved to >=22.0.0 relatively recently — 434 of the 656 published versions still declare >=20. That is why I checked latest rather than assuming the number was a typo.

Verification

npm view @qwen-code/qwen-code@latest engines → { node: '>=22.0.0' }, and the upstream README states Node.js 22+ for the npm install.
The diff is exactly 2 files changed, 2 insertions(+), 2 deletions(-), one line per file.
No collision with the open queue: the only open PR touching these files is #418, whose qwen_code hunks cover lines 57–69, while this change is line 12 — different hunks, so the two do not conflict. (I checked the hunk ranges of every open PR touching qwen_code.md and qwen_code.zh-CN.md.)

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/deepseek-ai/awesome-deepseek-agent/pull/424 **Author:** [@PerryLink](https://github.com/PerryLink) **Created:** 9/23/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `docs-qwen-node22` --- ### 📝 Commits (1) - [`39e9fba`](https://github.com/deepseek-ai/awesome-deepseek-agent/commit/39e9fbaf8c5a966624aceda40300aab13aac14d2) docs(qwen_code): the npm install path needs Node 22, not 20 ### 📊 Changes **2 files changed** (+2 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `docs/qwen_code.md` (+1 -1) 📝 `docs/qwen_code.zh-CN.md` (+1 -1) </details> ### 📄 Description ## What The guide's first prerequisite, on line 12 of both halves, says *"Install Node.js 20 or later"*, and the next line installs `@qwen-code/qwen-code@latest`. That package's latest release refuses to install on Node 20: ``` $ npm view @qwen-code/qwen-code@latest engines { node: '>=22.0.0' } ``` So a reader who follows the guide literally hits an `EBADENGINE` refusal on the very next command. ## Change `20` → `22` on line 12 of `docs/qwen_code.md` and `docs/qwen_code.zh-CN.md`. One line per file, nothing else changed. ## Why 22 and not something else `@qwen-code/qwen-code@0.24.4` is `latest` and declares `"node": ">=22.0.0"`. The upstream README agrees — its badge reads `node-%3E%3D22.0.0` and line 53 says *"**NPM** (requires Node.js 22+)"*. ## Scoped to the npm path on purpose Upstream scopes it the same way: its README line 53 reads *"**NPM** (requires [Node.js 22+](https://nodejs.org/))"*, attaching the requirement to the npm route only, while this guide's other routes are the quick-install script and `brew install qwen-code`. If you would rather the bullet carry that qualification explicitly, I am happy to reword it instead. ## On the "20" being there in the first place It was correct when written: the requirement moved to `>=22.0.0` relatively recently — 434 of the 656 published versions still declare `>=20`. That is why I checked `latest` rather than assuming the number was a typo. ## Verification - `npm view @qwen-code/qwen-code@latest engines` → `{ node: '>=22.0.0' }`, and the upstream README states Node.js 22+ for the npm install. - The diff is exactly `2 files changed, 2 insertions(+), 2 deletions(-)`, one line per file. - No collision with the open queue: the only open PR touching these files is #418, whose `qwen_code` hunks cover lines 57–69, while this change is line 12 — different hunks, so the two do not conflict. (I checked the hunk ranges of every open PR touching `qwen_code.md` and `qwen_code.zh-CN.md`.) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

bsakaguchi added the

pull-request

label

2026-10-26 09:49:04 +00:00

No labels

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

deepseek-ai/awesome-deepseek-agent#422

No description provided.

Rows
Columns