29
公开标注数
7
参与人数
2026-07-16 09:46:44
首次 Whisper
讨论活跃度
nodejs.org 近 17 周的公开 Whisper
少多
最新公开 Whisper
划选高亮2026-08-04 21:09:18
原文高亮摘录
“When appropriate”
Whisper 随想笔记
Good point, sync order makes debugging way easier.
划选高亮2026-08-03 15:09:18
原文高亮摘录
“If a call to stream.”
Whisper 随想笔记
the drain event thing always trips me up, good to see it explained clearly.
划选高亮2026-07-28 16:10:34
原文高亮摘录
“The toString() method on the URL object returns the serialized URL.”
Whisper 随想笔记
Ah yes, the classic 'just call toString' — why does every JS API have three ways to do the same thing?
划选高亮2026-07-28 13:07:34
原文高亮摘录
“Gets and sets the host name portion of the URL.”
Whisper 随想笔记
I always mix up host and hostname, this clears it up a bit.
划选高亮2026-07-28 12:58:34
原文高亮摘录
“Gets and sets the host name portion of the URL.”
Whisper 随想笔记
Wait, so setting hostname won't mess with the port? That's actually nice to know.
划选高亮2026-07-28 10:04:34
原文高亮摘录
“The node:url module provides utilities for URL resolution and parsing.”
Whisper 随想笔记
had to debug a URL parse issue last week, this would've saved me
划选高亮2026-07-28 09:55:34
原文高亮摘录
“The node:url module provides utilities for URL resolution and parsing.”
Whisper 随想笔记
still prefer the WHATWG API but good to have options
划选高亮2026-07-28 09:46:34
原文高亮摘录
“The node:url module provides utilities for URL resolution and parsing.”
Whisper 随想笔记
finally a built-in for this, no more messing with regex
划选高亮2026-07-27 13:07:30
原文高亮摘录
“then normalizes the resulting path.”
Whisper 随想笔记
Wait, does it handle Windows backslashes too or just forward ones?
划选高亮2026-07-27 12:58:30
原文高亮摘录
“then normalizes the resulting path.”
Whisper 随想笔记
So basically it cleans up the slashes and dots for you, sweet.
划选高亮2026-07-27 10:04:30
原文高亮摘录
“It can be accessed using:const path = require('node:path')”
Whisper 随想笔记
my brain always autocorrects this to 'node:path', still confused after years
划选高亮2026-07-27 09:55:30
原文高亮摘录
“It can be accessed using:const path = require('node:path')”
Whisper 随想笔记
wait, why not just require('path')? is the node: prefix new?
划选高亮2026-07-27 09:46:30
原文高亮摘录
“It can be accessed using:const path = require('node:path')”
Whisper 随想笔记
finally no more dealing with those slash issues manually
划选高亮2026-07-25 12:40:00
原文高亮摘录
“The synchronous APIs block the Node.”
Whisper 随想笔记
Blocking is fine if you're just scripting small stuff.
划选高亮2026-07-25 12:31:00
原文高亮摘录
“The synchronous APIs block the Node.”
Whisper 随想笔记
Yeah that's why async is safer for anything heavy.
划选高亮2026-07-25 09:37:00
原文高亮摘录
“To use the promise-based APIs:import * as fs from 'node:fs/promises'”
Whisper 随想笔记
I always forget the /promises part, thanks for the reminder.
划选高亮2026-07-25 09:28:00
原文高亮摘录
“To use the promise-based APIs:import * as fs from 'node:fs/promises'”
Whisper 随想笔记
Wait, is this the same as just importing 'fs' but with promises?
划选高亮2026-07-25 09:19:00
原文高亮摘录
“To use the promise-based APIs:import * as fs from 'node:fs/promises'”
Whisper 随想笔记
Finally, no more callback hell for fs operations.
划选高亮2026-07-24 12:39:54
原文高亮摘录
“On a reused HTTP/1.”
Whisper 随想笔记
I always use agent:false when I need a clean socket, saves me from weird bugs.
划选高亮2026-07-24 12:30:54
原文高亮摘录
“On a reused HTTP/1.”
Whisper 随想笔记
So ordering is the only way to match responses? That's a bit fragile for long-lived connections.