guest271314

// Copyright (c) 2019-2021 Robert Rypuła - https://github.com/robertrypula

/*
  +--------------------------------------------------+
  | Binary broadcast WebSocket server in pure NodeJs |
  +--------------------------------------------------+

  Based on great article created by Srushtika Neelakantam:
  https://medium.com/hackernoon/implementing-a-websocket-server-with-node-js-d9b78ec5ffa8

guest271314

// response-error.ts
class ResponseError extends Error {
  name;
  response;
  options;
  data;
  constructor(res, data, options) {
    super(`Request failed with status ${res.status}`);
    this.data = data;
    this.name = "ResponseError";

guest271314

Today we will be using the Web browser (Google Chrome for Testing 125) as a local HTTP over TCP socket server.

WICG Direct Sockets specifies an API that provides TCPSocket, UDPSocket, and TCPServerSocket.

In Chromium based browsers, for example Chrome, this capability is exposed in an Isolated Web Apps (IWA).

Previously we have created an IWA that we launch from arbitrary Web sites with open(),

guest271314

guest271314

// vendor/esm.sh/v135/signal-polyfill@0.1.0/denonext/signal-polyfill.mjs
var $ = function(e, o) {
  return Object.is(e, o);
};
var N = function(e) {
  let o = i;
  return i = e, o;
};
var ce = function() {
  return i;

guest271314

An issue filed in Bun I find interesting, Bun runtime plugin onResolve doesn't filter non-file: protocol imports #9863.

The gist is handling Ecmascript static import and dynamic import() that are arbitrary specifiers and setting arbitrary content. Something like

import demo1 from '1.demo';

console.log('demo 1', demo1);

import demo2 from 'demo:2';

guest271314

Why I use node, deno, bun, qjs, tjs at the same time.

Winds up being a (not the) rather comprehensive JavaScript toolbox. The idea being for the modern JavaScript programmer can use all of the tools available for a given requirement, task or job, without preference for any. No external bundlers or compilers are needed. No frameworks are needed. I can use qjs or tjs for systems with minimal RAM and disk space; and when I want to use Web API's deno makes an effort to provide those interfaces. In some cases I can run the exact same code in bun, deno, and node, which provides a means to perform 1:1 testing as to performance.

There's probably a few things I am unintentionally omitting below. These are just a brief synposis. I'll update accordingly.

guest271314

Node.js' fetch() implementation depends on Undici. Undici's fetch() does not support fetching file: protocol. See

• Isomorphic local file fetching #45798
• fetch: Enable fetch via file URL (under flag) #2751
• Standardize fetch calls to file: URLs

I've been using XMLHttpRequest() and fetch() to get file: protocol for quite some time in the browser; both with and without browser extensions, on Chromium-based browsers and Firefox.

guest271314

TypeError: fetch failed
    at fetch (/node_modules/undici/index.js:109:13) {
  [cause]: TypeError: Invalid URL
      at new URL (node:internal/url:804:36)
      at parseURL (/node_modules/undici/lib/core/util.js:51:11)
      at Object.parseOrigin (/node_modules/undici/lib/core/util.js:117:9)
      at new Pool (/node_modules/undici/lib/dispatcher/pool.js:70:23)
      at Agent.defaultFactory (/node_modules/undici/lib/dispatcher/agent.js:22:7)
 at [dispatch] (/node_modules/undici/lib/dispatcher/agent.js:93:34)

guest271314

// node --experimental-default-type=module read_child_process.js
import { spawn } from "node:child_process";
import { Duplex } from "node:stream";

const [command, args] = ["python3", ["./stream.py"]];
const { stdout, stderr } = spawn(command, args);
const { readable, writable } = Duplex.toWeb(stdout);
console.log(readable, writable);
/*
const data = await new Response(readable).text();