Error: WebSocket is not found. Please use Lynx >= 2.16 or consider using a polyfill.

Open

#9 opened on Nov 22, 2025 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language: Kotlin
Stars: 56
Forks: 3
PR merge metrics: No merged PRs in 30d

Description

Is anybody got this error:
```text
[7411436D8690:ERROR:lynx_console.cc(358)] "Error: WebSocket is not found. Please use Lynx >= 2.16 or consider using a polyfill. (Ask Gemini)
at WebSocketImpl (/.rspeedy/index/background.js:14837:120)
at WebSocket (/.rspeedy/index/background.js:14683:218)
at WebSocketClient (/.rspeedy/index/background.js:14087:41)
at initSocket (/.rspeedy/index/background.js:14436:24)
at (react:background)/./node_modules/.pnpm/@lynx-js+webpack-dev-transport@0.2.0/node_modules/@lynx-js/webpack-dev-transport/lib/client/index.js?hostname=172.31.32.1&port=3000&pathname=%2Frsbuild-hmr&hot=true&live-reload=true&protocol=ws&token=8bb4083c742ae1b2 (/.rspeedy/index/background.js:14305:102)
at call (native)
at (/.rspeedy/index/background.js:16288:78)
at call (native)
at __webpack_require__ (/.rspeedy/index/background.js:15779:86)
at (/.rspeedy/index/background.js:16807:280)
at (/.rspeedy/index/background.js:16812:5)
at require (/lynx_core.js:7:37281)
at __init_card_bundle__ (/.rspeedy/index/background.js:16814:39)
at _$executeInit (/lynx_core.js:7:35013)
at requireModule (/lynx_core.js:7:35561)
at (/lynx_core.js:7:6672)
at (/app-service.js:1:252)
at require (/lynx_core.js:7:37281)
at n (/app-service.js:1:292)
at _$executeInit (/lynx_core.js:7:35013)
at requireModule (/lynx_core.js:7:35561)
at (/lynx_core.js:7:6672)
at Vt (/lynx_core.js:7:43137)
"
```

Contributor guide

No contributing guide indexed for this repository

First steps

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

Research direction

Reproduce the error in the Lynx CLI setup and verify the Lynx version. Trace the WebSocketClient and initSocket path in @lynx-js/webpack-dev-transport, then determine whether the issue is resolved by requiring Lynx >= 2.16 or by using a polyfill; done means the development transport starts without this error.

Written by the indexing model from the issue text.

Assessment

Tech stack: javascript, webpack
Domain: cli, devtools
Issue type: Bug
Difficulty: 4/5
Estimated time: 3-5 days
Activity status: Stale
Clarity: Needs clarification
Newbie friendliness: 25/100