Jacob Hummer

if im not mistaken, this https://github.com/denoland/deno/blob/a1d823e27d1b605b5658fddc1c9273667f0e9e84/ext/console/01_console.js#L3120-L3127 should be ```js // Format as a floating point value. const value = args[a++]; if (typeof value == "symbol") { formattedArg = "NaN"; }...

I notice that this repo is the first hit on GitHub Actions marketplace but that there's been no commits in more than a year and there are three open Issues....

Static CJS exports not detected - @nodefill/primordials

3

## Failing module - **GitHub**: https://github.com/nodefill/primordials - **npm**: https://npmjs.com/package/@nodefill/primordials ```js import { ArrayPrototypePush } from "https://esm.sh/@nodefill/primordials" ``` ## Error message After `onload` I got this: ``` Uncaught SyntaxError: The requested...

Failed to import - @nodefill/primordials subpaths

1

## Failing module - **GitHub**: https://github.com/nodefill/primordials - **npm**: https://www.npmjs.com/package/@nodefill/primordials ```js // DevTools console on esm.sh let m; m = await import("https://esm.sh/@nodefill/primordials/ArrayIsArray.js"); ``` ## Error message After running ☝ in the...

There appears to be an official Deno polyfill for Node.js going on in https://github.com/denoland/node_shims and there also appears to be an actual https://www.npmjs.com/package/denode package. It might be a good idea...

Use process.stdout.isTTY instead of node:tty

8

> The preferred method of determining whether Node.js is being run within a TTY context is to check that the value of the process.stdout.isTTY property is true: > > ```sh...

Consider reframing this to be a list of awesome *byexample.com websites

1

I notice that this list duplicates much of the content from: - https://github.com/lauragift21/awesome-learning-resources - https://github.com/razum2um/awesome-clojure - https://github.com/sorrycc/awesome-javascript - https://github.com/krispo/awesome-haskell#resources - https://github.com/markets/awesome-ruby - all the more focused "awesome ${thing}" lists imo...

FileHandle#read() panics if the FileHandle is a directory

2

I think it's this `.unwrap()` that's unwrapping the return value of `std::fs::read()` that was stashed in the shared value... https://github.com/PolyMeilex/rfd/blob/25d879a854b606c2236b72c7c085ae776d413837/src/file_handle/native.rs#L52 ...but since https://doc.rust-lang.org/stable/std/fs/fn.read.html returns a `Result`, the `unwrap()` panics.

Is there a dry-run input?

1

Some actions have a `dry-run: true` input that you can set if you just want to do everything _except_ mutate stuff. This is useful for tinkering. Is there an equivalent...

bootstrap: try-catch around potentially failing stream.write() for `node --help`

2

fixes #51448