guest271314

Taking the JavaScript runtime agnostic approach a step further I'm thinking about combining qjs, node, deno, and bun into a single executable (~350 MB, still less than Rust tool chain at ~500 MB) that I can reference as such within JavaScript and/or TypeScript in the same .js and/or .ts script, and do something like this

import { cc } from "bun:ffi";
import ( $ } from "jsr:@david/dax";
std.popen(...);

guest271314

export class FACharacterClasses {
    static unicodeCategories = [
        [
            65,
            90,
            192,
            214,
            216,
            222,
            256,

guest271314

Node.js

node --no-warnings node-strip-types.js https://raw.githubusercontent.com/user/repo/refs/heads/main/file.ts transform

node --no-warnings node-strip-types.js ../path/to/file.ts transform

guest271314

// Fetch non-entrypoint, non-TypeScript files from jsr:,
// write files to local vendor directory containing enttrypoint .ts file
// Usage: deno -A fetch-jsr-files.js @scope mod

const [scope, mod] = Deno.args;

const { latest: version } = (await import(
  `https://jsr.io/${scope}/${mod}/meta.json`,
  {
    with: {

guest271314

// bun build node_modules/amaro/dist/index.js --target=node --outfile=nodejs-amaro-bundle.js 
import { createRequire } from "node:module";
var __commonJS = (cb, mod) => () => (mod || cb((mod = { exports: {} }).exports, mod), mod.exports);
var __require = /* @__PURE__ */ createRequire(import.meta.url);

// node_modules/amaro/dist/index.js
var require_dist = __commonJS((exports, module) => {
  var __create = Object.create;
  var __defProp = Object.defineProperty;
  var __getOwnPropDesc = Object.getOwnPropertyDescriptor;

guest271314

// Transpile TypeScript to JavaScript using Deno built-ins
// Usage: deno -A deno-ts-js-cache.js nm_typescript.ts
// Write Deno's generated cache .ts.js file to stdout and current directory
// ts: Path to .ts script
const [ts] = Deno.args;
const url = new URL(import.meta.resolve(ts));
const { pathname } = url;
const filename = pathname.split("/").at(-1);
const decoder = new TextDecoder();
// Path to generated cache .ts.js script

guest271314

Here's a modest project, just to see what happens: Try to convert npm to an Ecmascript Module and compile npm https://github.com/npm/cli to a single executable with deno compile, bun build, and node --experimental-sea-config combined with postject.

Node.js

npm is written in CommonJS.

node can't even handle compiling npm to a Single executable https://nodejs.org/api/single-executable-applications.html with

cp node npm

guest271314

The specification for MediaStreamTrack is located in W3C Media Capture and Streams.

In pertinent part at 4.3.1.1 Media Flow

The result for the consumer is the same in the sense that whenever MediaStreamTrack is muted or disabled (or both) the consumer gets zero-information-content, which means silence for audio and black frames for video. In other words, media from the source only flows when a MediaStreamTrack object is both unmuted and enabled. For example, a video element sourced by a MediaStream containing only muted or disabled MediaStreamTracks for audio and video, is playing but rendering black video frames in

guest271314

globalThis.Piper = class Piper {
  constructor({
    text,
    voice
  } = {
    text: "Speech synthesis.",
    voice: "male",
  }) {
    // Encoded into Web extension iframe URL
    this.params = new URLSearchParams(Object.entries({

guest271314

// Generate Chrome extension ID from absolute path
// https://stackoverflow.com/a/26058672
// https://stackoverflow.com/a/61448618
// https://gist.github.com/dfkaye/84feac3688b110e698ad3b81713414a9
// generateIdForPath("/home/user/javascript").then(console.log).catch(console.error);
async function generateIdForPath(path) {
  return [
    ...[
      ...new Uint8Array(
        await (globalThis?.webcrypto?.subtle || globalThis?.crypto?.subtle).digest(