Add comprehensive Node.js 26 release blog post#35
Merged
Conversation
Code-heavy tour of Node.js 26 highlights, prioritised by excitement: Temporal API (now stable by default), Map/WeakMap upsert helpers, Iterator.concat, crypto raw-key support and Ed25519 context, plus an upgrade checklist for the breaking changes. Each section shows what the new API looks like and, where useful, the older pre-26 equivalent. https://claude.ai/code/session_01AQihcJjkxeokR9LrdeYuZY
v25 was not skipped: it was the standard October 2025 odd-numbered Current release that reaches end-of-life when v26 ships. Replaces the incorrect intro paragraph and FAQ entry. https://claude.ai/code/session_01AQihcJjkxeokR9LrdeYuZY
Adds a short paragraph acknowledging Moment.js, Luxon, and date-fns as the libraries we used to reach for, and frames Temporal as one less dependency to worry about. https://claude.ai/code/session_01AQihcJjkxeokR9LrdeYuZY
Mentions Python's dict.setdefault and Rust's HashMap::entry().or_insert_with to give context to readers who have used the same pattern in other languages and missed it in JS. https://claude.ai/code/session_01AQihcJjkxeokR9LrdeYuZY
Adds a canonical-reference link to nodejs.org/en/blog/release/v26.0.0 in the wrapping-up section so readers can dig into the full changelog. https://claude.ai/code/session_01AQihcJjkxeokR9LrdeYuZY
Final pass over the article and content calendar after two reviews and several rounds of in-line revisions. Highlights: - Iterator.concat section: broken async paginated example (Iterator.concat is sync-only) replaced with a sync log-merge example, plus a streaming async companion in the example repo - Ed25519 context strings demoted from a full subsection to a one-line mention; raw-key snippet updated to the real v26 API (format: 'raw-private', asymmetricKeyType) - temporal-sort snippet fixed (Array#map was passing the index into Temporal.PlainDate.from's options slot) - File-name tabs (title="...") on every code block that mirrors a file in lmammino/nodejs-26-examples - Internal links added to HTTP-requests and install-Node guides - Content calendar updated with the new article entry, linking map, and a note about release-announcement articles as a recurring slot - Publish date set to 2026-05-10T16:15:00
ddc6b61 to
5b26e64
Compare
Local typecheck passed but CI was failing on `pnpm typecheck` because TypeScript was only a transitive dep (via @typescript-eslint / astro), and CI's environment ended up resolving a newer TypeScript (pnpm even hinted "6.0.3 is available" on install). The newer compiler flagged `baseUrl` as a hard error (TS5101) and recommended setting `"ignoreDeprecations": "6.0"` — a value that doesn't exist in 5.8.3. Pinning typescript@5.8.3 as a direct devDep makes CI and local use the same version unambiguously. The large pnpm-lock.yaml diff is mostly formatting/consolidation; the only intentional change is the new `typescript: 5.8.3` entry.
Lockfiles are auto-generated and shouldn't be reformatted by prettier; .tmp/ is a local scratch directory. Both were causing format:check to fail on CI after the typescript-pin lockfile rewrite.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a detailed blog post covering the features, improvements, and breaking changes in Node.js 26, released on May 5, 2026.
Key Changes
src/content/blog/whats-new-in-nodejs-26/index.md(515 lines)getOrInsert()andgetOrInsertComputed()methodsNotable Implementation Details