Skip to content

Native Web Socket Support #957

Open
Open
@wSedlacek

Description

@wSedlacek

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions