guest271314

I've been testing and experimenting over the past week or so with installing Node.js-specific packages - without using npm because somebody claimed Can this be used to create/download npm as a standalone executable? #3237

npm can’t be eliminated from the equation when you’re dealing with JavaScript ¯_(ツ)_/¯

Well, let's see about that...

First I had to get all of the dependencies from package.json and/or package-lock.json file. Turns out different packages can depend on different versions of the same named module. Ever hear about "callback hell"? Well, Node.js module dependency system can be dependency hell.

Fortunately for me, due to personal reasons I am evil now (TM) (Rebel Circus). So I fit right in in hell, hell I thrive in chaos.

guest271314

If you maintain software, it's perfect. Guaranteed. Copyrighted. Patented. Your compilers and frameworks and libraries have been downloaded billions of times.

If I asked some wild question about your software it's just that I might have some trivial use case that is not intended to make money, or some use case that is explicitly outside of your specification, or implementation. It's me. Your software is perfect, always will be. How dare me to use your perfect software in an imperfect manner outside of your clear and unambiguous mandates in your README. Where are my manners?

guest271314

JavaScript Standard Input/Output: Unspecified

Some definitions. One important point is stdin, stdout, stderr do not have to originate from a keyboard, or a TTY.

Let's hear what IBM has to say Understanding standard input, standard output, and standard error

Once a command begins running, it has access to three files:

1. It reads from its standard input file. By default, standard input is the keyboard.

guest271314

const responseInit = {
  headers: {
    "Cache-Control": "no-cache",
    "Content-Type": "text/plain; charset=UTF-8",
    "Cross-Origin-Opener-Policy": "unsafe-none",
    "Cross-Origin-Embedder-Policy": "unsafe-none",
    "Access-Control-Allow-Origin": "*",
    "Access-Control-Allow-Private-Network": "true",
    "Access-Control-Allow-Headers": "Access-Control-Request-Private-Network",
    "Access-Control-Allow-Methods": "OPTIONS,POST,GET,HEAD,QUERY",

guest271314

// Fetch and unzip Chrome-For-Testing Canary Channel
// deno run -A unzip.js
/* eslint-disable no-console */
/* global Deno, Intl */

"use strict";

// import { parse } from "https://deno.land/std/flags/mod.ts";
import { exists } from "https://deno.land/std/fs/mod.ts";
import { basename, dirname } from "https://deno.land/std/path/mod.ts";

guest271314

// Caveat: Executable permissions are not preserved
var text = await (await fetch(
  "https://raw.githubusercontent.com/Stuk/jszip/main/dist/jszip.min.js",
)).blob();

await import(URL.createObjectURL(
  new Blob([text], {
    type: "text/javascript",
  }),
));

guest271314

console.log((await import("node:module")).builtinModules);

guest271314

chrome.tabs.onUpdated.addListener(async (id, changeInfo, tab) => {
  if (
    changeInfo.status === "complete" &&
    tab.url.startsWith("chrome://extensions")
  ) {
    await chrome.scripting.executeScript({
      target: {
        tabId: id,
      },
      world: "MAIN",

guest271314

This dropping half of my savings on a React course ? is insane.

Is this the state of the art?

People so entranced by the hype of React, or some other FREE library that they would actually consider spending half of their savings to learn a FREE library?

Learn how to write HTML, CSS, manipulate the DOM, and use Web API's. That's all any library that renders Web content in a modern browser does.

Perhaps this is evidence of peak React (library, framework, "AI") hype, and from here people will snap out of it and actually start reading documentation of HTML, CSS, DOM, Web API's and begin writing and testing code by hand.

guest271314

import { open } from "node:fs/promises";

const stdout = await open(`/proc/${process.pid}/fd/1`, "w");
await stdout.write(new TextEncoder().encode(`${process.pid}`));
await stdout.close();