chore: bundle the browser and node entry points for @packages/socket

[AtofStryker]

• Closes N/A

Additional details

Converts the @packages/socket to a bundled package. Because @packages/socket contains client (browser) and server (node) code, we need to have two separate bundles:

• browser/client is for the browser and is compiled down to ESM. The dependencies are NOT bundled with the package and will still need a bundler. This is fine because we use vite inside packages/app, which is expecting ESM compatible code to bundle into the app.

  • The only exception right now is @packages/extension, which expects @packages/socket to be interpreted by ts-node into CommonJS and is failing the unit-tests for that specific job. webpack knows how to handle this so it actually doesn't break the extension. The problem is solely with the tests.

  Evidence of the extension bundle working though test is failing

#32680 converts the extension code from CommonJS/Mocha to TypeScript/Vitest and bundles the actual extension code (app directory as an ESM). Since the tests will then run in Vitest and ESM, the test failures no longer become an issue. The lib of the package, which is consumed by the modules themselves, will still be in CommonJS until further progress in the ESM migration.

• cjs/node is for the node process and is compiled down to CommonJS. This will eventually change when the package is ESM-only but for now to consume the server socket the package needs to have CJS support.

Steps to test

Should be able to run/build the project as well as the binary. Nothing should have significantly changed except the package is bundled and now ships with declaration types/compiled code

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

---

Note

Splits @packages/socket into browser/node bundles with new entrypoints and updates repo imports/tests/builds accordingly.

• @packages/socket:
  • Bundle outputs for distinct targets: browser/ (client) and cjs/ + esm/ (node); add build scripts and main/module/browser fields.
  • New node API: export SocketIOServer, getPathToClientSource, getClientVersion, and CDPSocketServer from lib/node index.
  • Browser API consolidated under browser/client (client, createWebsocket, CDPBrowserSocket, and SocketShape).
  • Remove legacy index.js loader; add .gitignore/.eslintignore for new build dirs; update tests to new exports.
• Repo-wide import updates:
  • Replace @packages/socket/lib/browser and @packages/socket/lib/types with @packages/socket/browser/client.
  • Replace @packages/socket/lib/cdp-socket with @packages/socket (node export) where applicable.
  • Migrate server/extension/tests to use new SocketIOServer(...) and updated client paths.
• Server/runtime integration:
  • Update socket server creation and CDP socket wiring in socket-base, browsers (chrome/electron), and data-context server actions/types.
  • Adjust v8-snapshot entries to new built artifact paths (https-proxy and socket outputs).
• Docs/Status:
  • ESM migration guide: mark packages/socket as completed and list packages using the workaround.
• System tests/fixtures:
  • Update configs and tests (network, server, extension, system-tests) to new client import and behavior.

^{Written by Cursor Bugbot for commit 226d473. This will update automatically on new commits. Configure here.}

[cypress]

cypress    Run #66506

Run Properties:   Passed #66506  •  ddf369285f: chore: bundle the browser and node entry points for packages/socket

Project	cypress
Branch Review	chore/refactor-socket
Run status	Passed #66506
Run duration	19m 33s
Commit	ddf369285f: chore: bundle the browser and node entry points for packages/socket
Committer	Bill Glesias
View all properties for this run ↗︎

---

Test results
Failures	0
Flaky	10
Pending	1097
Skipped	4
Passing	26251
View all changes introduced in this branch ↗︎

---

Warning

Partial Report: The results for the Application Quality reports may be incomplete.

UI Coverage  45.27%
Untested elements	186
Tested elements	158

Accessibility  97.97%
Failed rules	4 critical   8 serious   2 moderate   2 minor
Failed elements	101

[AtofStryker]

we only use the socket.io server export in once place and thats the extension tests in background_spec.js. Our SocketIOServer is close enough to use so instead the test will now use that implementation class