fix(desktop): pin @icons-pack/react-simple-icons below its node>=24 releases

[xxxigm]

Summary

A WSL user (Node v22.22.3) reported a noisy desktop launch:

npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@icons-pack/react-simple-icons@13.13.0',
npm warn EBADENGINE   required: { node: '>=24', pnpm: '>=10' },
npm warn EBADENGINE   current: { node: 'v22.22.3', npm: '10.9.8' }
npm warn EBADENGINE }

apps/desktop/package.json declares it supports Node ^20.19.0 || >=22.12.0, but @icons-pack/react-simple-icons bumped its own engines.node to >=24 starting at 13.11.2 (13.11.1 and earlier have no Node floor). With the old ^13.13.0 range, every install on the project's supported Node 20/22 range prints the EBADENGINE warning — and would hard-fail under engine-strict / npm ci --engine-strict.

Fix

Cap the range at <13.11.2 (">=13.0.0 <13.11.2"), which resolves to 13.11.1 — the last release before the Node-24 floor. The package works fine on Node 22; only its declared engine was over-tightened.

Verified every brand glyph the app imports (platform-icon.tsx: Telegram, Discord, Matrix, Signal, WhatsApp, Apple, Gmail, HomeAssistant, Mattermost, QQ, WeChat, Bilibili) is present in 13.11.1 — icon-identical, no behavior change.

Lockfile diff is minimal: the resolved version moves to 13.11.1 and the old 13.13.0 entry (with engines.node: ">=24") is dropped; no other packages churn.

Test plan

• Confirmed via the npm registry that 13.11.2+ carry engines.node: ">=24" and 13.11.1 does not.
• Confirmed all 12 imported Si* icon modules exist in @icons-pack/react-simple-icons@13.11.1.
• package-lock.json regenerated with npm install --package-lock-only; diff limited to this one dependency.

Note: this clears the EBADENGINE warning from the report. The reporter's separate "can't click the top two left-sidebar options" symptom looks WSL/WSLg-display-specific and is tracked separately.

[alt-glitch]

Duplicate of #40284 — same fix: cap @icons-pack/react-simple-icons below 13.11.2 (resolves to 13.11.1) to clear the EBADENGINE warning, since 13.11.2+ require node>=24 while the desktop app supports Node 20/22. Same files (apps/desktop/package.json, package-lock.json).

[austinpickett]

Verified — correct, minimal, and internally consistent. Approving.

Premise confirmed (via npm view)

• @icons-pack/react-simple-icons 13.11.2, 13.12.0, 13.13.0 all declare engines: { node: ">=24" }; 13.11.1 and earlier do not.
• Desktop app supports node: ^20.19.0 || >=22.12.0 (repo root >=20.0.0), so ^13.13.0 resolves to a node-24-only release — incompatible with the support floor. The pin >=13.0.0 <13.11.2 correctly excludes every node-24 release.

Pin/lockfile consistency ✅

apps/desktop/package.json and the lockfile root both move to >=13.0.0 <13.11.2; a nested entry resolved at 13.11.1 is added and the old hoisted 13.13.0 removed. semver confirms 13.11.1 satisfies the range and 13.13.0 does not. The 13.11.1 entry correctly drops the engines block.

Cross-PR conflict with #44024 — none

#44024 (approved, edits root package-lock.json at the @types/node region ~line 8418+ and the 19659–20084 dedup block) and #44197 (edits lines ~83, 161, 2554–2582) touch completely disjoint ranges. Git's 3-way merge auto-resolves regardless of order; whichever lands second just needs no manual intervention. No blocker.

Minor (non-blocking)

No .npmrc engine-strict=true in the repo, so plain npm install only warns on an unsatisfied engines field rather than hard-failing — so "breaks the build" is slightly stronger than reality for local installs. The pin is still the right defensive fix (stricter CI/electron toolchains do fail, and it prevents silently shipping a node-24-only dep). The hard upper bound <13.11.2 over a caret is intentional and appropriate.

[github-actions]

❌ Lockfile fix failed

See the workflow run for logs.

[teknium1]

Thanks for the focused dependency and lockfile update. This is already implemented on current main.

• Automated hermes-sweeper review verified apps/desktop/package.json:64 pins @icons-pack/react-simple-icons to =13.11.1, which excludes the Node >=24 releases.
• package-lock.json:2781 resolves version 13.11.1 and has no engines.node >=24 constraint.
• Commit 769f307042d22be2c092249c2d8d78f85fea8e37 (fix(npm): lock react-simple-icons to 13.11.1) made the same manifest and lockfile change; it shipped in v2026.6.19.
• This also matches the member's duplicate reference to fix: pin @icons-pack/react-simple-icons to ~13.11.1 to avoid EBADENGINE warning #40284.