Native Web Socket Support
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- typescript
- Domain
- devtools, networking
Research direction
The issue names no files, tests, or entry points. Start by locating the current SocketCluster v14.3.2 integration and its socketcluster-client dependency, then assess the TypeScript type imports and deprecated transitive dependencies. Done means remote DevTools communication works without that third-party library and no longer introduces the reported Node type pollution.
Written by the indexing model from the issue text.
Description
In the current iteration of this library SocketCluster is used, particularly v14.3.2
At runtime this library works beautifully, however at design time I have run into a bit of trouble.
Specifically, socketcluster-client is the source of two warnings in my npm install.
npm WARN deprecated uuid@3.2.1: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
And the types for socketcluster-client import node libraries like consumable-stream and ws which have /// <reference types="node" /> in the files.
This causes any import of those types to pollute the global type space with a bunch of node types.
The first problem is ignorable, and the second problem can be worked around by just making my own types for socketcluster-client.
That said, these problems don't seem like they are going to be resolved any time soon.
It would be nice if I didn't need to use this third party library to interact with the remote dev tools.
My integration could have a lot few dependencies and a lot less design time issues.
- Dominant language
- TypeScript
- Stars
- 14.4k
- Forks
- 1.2k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 20
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.
More from reduxjs/redux-devtools
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
reduxjs/redux-devtools#2091 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
reduxjs/redux-devtools#2075 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
reduxjs/redux-devtools#2053 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
reduxjs/redux-devtools#2006 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
reduxjs/redux-devtools#1993 · 1 reaction ·
All issues in reduxjs/redux-devtools
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·