socket.io-client on the browser

Describe the bug
I want to be able to import the client version without having to use a bundler / using the serveClient option on the server. Can you just provide an ES2020 module that I can just directly import?

This is when I use the npm package instead of a http import (so I get typescript support).

Expected behavior

// client.ts (bundled for browser)
import { io } from 'socket.io-client/browser';
// ...

What I am currently doing
copying the esm output to a local directory

// client.ts (bundled for browser)
// @ts-types="npm:socket.io-client"
import { io } from './socket.io.esm.min.js';

deno bundle client.ts -o client.js

Platform:

Runtime: Deno 2.4.5
OS: Windows 10

maybe by adding a new tsconfig like tsconfig.esm.json called tsconfig.browser.esm.json

but make it ES2020 and use bundler, instead of node module resolution

I think exposing the browser ESM bundle through a dedicated subpath makes sense. We could add a socket.io-client/browser export pointing to dist/socket.io.esm.min.js with the existing ESM declarations, so Deno users can import io directly from the npm package without copying the generated file locally:

{
  "exports": {
    "./browser": {
      "types": "./build/esm/index.d.ts",
      "default": "./dist/socket.io.esm.min.js"
    }
    // ...
  }
}

and then import { io } from 'socket.io-client/browser';

What do you think?

yep makes sense. that should work

Navigation Menu

Repository navigation

`socket.io-client` on the browser #5383

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

socket.io-client on the browser #5383

Description

Activity

sakgoyal commented on Aug 28, 2025

darrachequesne commented on Sep 29, 2026

sakgoyal commented on Sep 29, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

`socket.io-client` on the browser #5383