Skip to content

Commit 4311b75

Browse files
digest: add issues for 2026-06-14
1 parent 293bf2d commit 4311b75

12 files changed

Lines changed: 252 additions & 0 deletions
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
date: 2026-06-13
3+
repo: biomejs/biome
4+
size: M
5+
title: "Biome fixes migrate comma bug"
6+
excerpt: "A malformed trailing comma could break strict JSON migrations when the renamed rule was last in its group; this patch fixes it and adds coverage."
7+
commits: 1
8+
authors: [tom-groves]
9+
commit_authors: {"5f837df": tom-groves}
10+
---
11+
12+
### **Fix malformed migrate output for renamed rules** (5f837df)
13+
`biome migrate` now preserves separator state correctly when a renamed rule is the last item in a group, preventing an invalid trailing comma from being emitted. That matters because the bad output could abort migrations of strict-JSON `biome.json` files with a parse error.
14+
15+
### Other misc changes
16+
- Added a regression test and snapshot for `renamedRuleLastInGroup`.
17+
- Changelog entry for the patch release.
Lines changed: 51 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,51 @@
1+
---
2+
date: 2026-06-13
3+
repo: denoland/deno
4+
size: L
5+
title: "Deno gets parameterized tests and WebCrypto in Rust"
6+
excerpt: "Major test, crypto, networking, and resolver changes landed, plus several fixes for fetch, serve, fs events, and LSP behavior."
7+
commits: 20
8+
authors: [bartlomieju, divybot, nathanwhitbot, crowlbot, petamoriken]
9+
commit_authors: {"8297980": bartlomieju, "d7a4b01": bartlomieju, "f82cc27": bartlomieju, "c5fee2e": divybot, "e8c6f4a": bartlomieju, "69de4f4": crowlbot, "fb90ee0": bartlomieju, "197dfca": bartlomieju, "b7446ed": bartlomieju, "99542ca": bartlomieju, "7b3cd9d": bartlomieju}
10+
---
11+
12+
### **Add `Deno.test.each` for parameterized tests** (d7a4b01)
13+
Deno now supports a Jest/Vitest-style `Deno.test.each`, registering one real test per case so each input gets its own reporting, filtering, and editor run integration. The implementation also handles name templating, `.only.each`, `.ignore.each`, and array/object/primitive case argument handling.
14+
15+
### **Port WebCrypto from JS to Rust** (c5fee2e)
16+
WebCrypto moved out of the massive JS shim and into native Rust-backed cppgc classes, leaving JS as a thin bootstrap layer for prototypes, singleton setup, and a small spec-driven `deriveBits` wrapper. This is a major internal refactor with a big performance and maintainability payoff for crypto-heavy workloads.
17+
18+
### **Stabilize bare Node built-in resolution** (e8c6f4a)
19+
Bare specifiers like `import "fs"` and `import "path"` now resolve without `--unstable-bare-node-builtins`, and npm packages can no longer shadow Node built-ins. That removes a long-standing instability gate and brings Deno’s Node compatibility in line with Node’s own resolution priority.
20+
21+
### **Support `navigator.userAgentData`** (69de4f4)
22+
Deno now exposes the User-Agent Client Hints API in both window and worker scopes, including the `NavigatorUAData` interface and high-entropy value lookup. This fills a compatibility gap for code that inspects browser-like UA metadata.
23+
24+
### **Require network अनुमति for Unix socket operations** (7b3cd9d)
25+
Unix domain socket connect/listen operations now require `--allow-net` in addition to filesystem access, closing a local IPC escape hatch that could reach services like Docker or dbus with only read/write permissions on the socket path. The permission model and CLI docs were updated to support scoped grants like `--allow-net=unix:/var/run/docker.sock`.
26+
27+
### **Support `catalog:` in `deno.json` imports** (8297980)
28+
`catalog:` references now work in `deno.json` `imports` and `scopes`, not just `package.json`. That unblocks catalog-based dependency resolution for both `deno run` and `deno install`, including materializing packages and CLI bins correctly.
29+
30+
### **Keep compressed response headers after transparent decompression** (197dfca)
31+
Fetch now preserves `content-encoding`, `content-length`, and `transfer-encoding` on decompressed responses, matching the fetch spec and browser/undici behavior. The change also adjusts cache and server serialization so only the wire headers are stripped when re-emitting decoded bodies.
32+
33+
### **Fix `Deno.watchFs` event loss under load** (99542ca)
34+
Filesystem watcher events are no longer silently dropped when the backend queue overflows; instead, the consumer is told to rescan. This makes watch mode far more reliable during bursts like mass file writes or archive extraction.
35+
36+
### **Make `deno serve --parallel --watch` stop old workers** (fb90ee0)
37+
Watcher restarts now cancel the previous worker generation instead of leaving old threads and the detached main worker alive. That prevents stale code from continuing to serve requests after edits and avoids eventual isolate-mismatch crashes.
38+
39+
### **Fix async op promise-id wraparound** (f82cc27)
40+
The core async promise-id counter no longer breaks after integer wraparound, which previously could send lookups to the wrong ring buffer and crash the process with missing-promise errors. This is a correctness fix for long-running or very high-op-count workloads.
41+
42+
### **Fix LSP requests for files opened from `node_modules`** (b7446ed)
43+
Files opened via managed `node_modules` paths now get associated with a TypeScript project correctly, so hover, diagnostics, code actions, and refactors work instead of failing or returning nothing. That unblocks common editor workflows when jumping into dependency sources.
44+
45+
### Other misc changes
46+
- SQL formatter switched to `lax-sql` for unstable SQL formatting.
47+
- `links` field in `deno.json` stabilized via schema cleanup.
48+
- WebCrypto and formatter-related internals updated to match the Rust port.
49+
- `deno serve` deprecation warning added for legacy request abort behavior.
50+
- Unix socket and watcher-related docs/tests/expectations updated.
51+
- WPT runner and deno_dom dependency updates.
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
date: 2026-06-13
3+
repo: denoland/std
4+
size: N
5+
title: "No changes"
6+
excerpt: ""
7+
commits: 0
8+
---
9+
10+

src/posts/2026-06-13_jsr-io-jsr.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
date: 2026-06-13
3+
repo: jsr-io/jsr
4+
size: N
5+
title: "No changes"
6+
excerpt: ""
7+
commits: 0
8+
---
9+
10+
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
date: 2026-06-13
3+
repo: leanprover/lean4
4+
size: M
5+
title: "BitVec flattening lands, docstring roles fixed"
6+
excerpt: "Lean4 adds BitVec.flattenList with lemmas and improves builtin assert docstring highlighting and parsing."
7+
commits: 2
8+
authors: [david-christiansen, kim-em]
9+
commit_authors: {"4e28544": david-christiansen, "67dffca": kim-em}
10+
---
11+
12+
### **Add BitVec.flattenList with fast runtime implementation** (67dffca)
13+
Lean4 now has `BitVec.flattenList`, which concatenates a list of fixed-width bitvectors into a single wider bitvector. The new lemmas pin down how individual bits and extracted ranges map back to list elements, and the implementation is swapped to a divide-and-conquer fast path at runtime for much better scaling on long lists.
14+
15+
### **Fix builtin assert docstring highlighting and roles** (4e28544)
16+
The builtin `assert'` docstring role now accepts two or three code fragments instead of a single combined snippet, matching the intended “lhs = rhs [: type]” shape more robustly. It also fixes hover/highlight metadata for downstream rich-doc consumers, including proper styling for option values and previously private structure exposure.
17+
18+
### Other misc changes
19+
- None.
Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
date: 2026-06-13
3+
repo: microsoft/typescript-go
4+
size: M
5+
title: "Declaration emit and diagnostics tightened"
6+
excerpt: "Fixes declaration emit diagnostics, UTF-16 diagnostic positions, and a checker bug around instantiated symbols."
7+
commits: 4
8+
authors: [jakebailey, weswigham]
9+
commit_authors: {"551b02d": jakebailey, "c78d39e": weswigham}
10+
---
11+
12+
### **Declaration emit now handles newer JS cases correctly** (c78d39e)
13+
The declaration transformer now sets up diagnostic context for additional expression shapes, including `object.defineProperty` calls and expando-style assignments. This improves error reporting and keeps newer JS declaration emit paths from missing symbol-accessibility diagnostics.
14+
15+
### **Checker avoids unstable symbol identity for instantiated members** (551b02d)
16+
The checker simplifies how it compares symbols from instantiated types and moves `this`-only instantiation handling into the symbol instantiation path itself. This should make “same reference” checks more deterministic and fix cases where `this`-substituted symbols were compared inconsistently.
17+
18+
### **Diagnostics API now returns UTF-16 offsets** (0751b19)
19+
Diagnostic responses are converted from file offsets to UTF-16 positions before being returned, matching editor-facing position semantics. This prevents misreported locations for Unicode text and aligns the API with consumer expectations.
20+
21+
### Other misc changes
22+
- Reclassified `nodeModulesAllowJsImportAssignment` JS emit diffs as accepted baselines (1 commit)
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
date: 2026-06-13
3+
repo: nodejs/node
4+
size: L
5+
title: "Node adds fs buffer reads, keepalive tuning"
6+
excerpt: "New fs readFile buffer support lands alongside TCP keepalive controls, debugger probe limits, and native API deprecations."
7+
commits: 12
8+
authors: [addaleax, Renegade334, guybedford, clavin, joyeecheung, npm-cli-bot, ShenHongFei, mcollina, watilde]
9+
commit_authors: {"2fb168f": addaleax, "1efdce3": guybedford, "fc28d94": addaleax, "8c4ec8a": joyeecheung, "de67c5c": mcollina}
10+
---
11+
12+
### **fs: support caller-supplied readFile() buffers** (de67c5c)
13+
`fs.readFile()` and `fsPromises.readFile()` can now read directly into a caller-provided buffer or a buffer factory, returning a view over the bytes read. This enables fewer allocations and more control over memory use when reading files.
14+
15+
### **net: expose TCP_KEEPINTVL and TCP_KEEPCNT in setKeepAlive** (1efdce3)
16+
`socket.setKeepAlive()` now accepts `interval` and `count` in addition to the existing keepalive delay, letting users tune probe cadence and drop thresholds from Node. That makes the API much more useful for long-lived connections and maps cleanly to `TCP_KEEPINTVL` and `TCP_KEEPCNT`.
17+
18+
### **debugger: add --max-hit option to probe mode** (8c4ec8a)
19+
Probe sessions can now stop as soon as a per-probe hit limit is reached, rather than waiting for timeout or process exit. This is a meaningful ergonomics upgrade for inspector-driven tooling and future attach-to-running-process workflows.
20+
21+
### **src: officially deprecate `node::ObjectWrap`** (fc28d94)
22+
Node now formally deprecates the long-unmaintained `node::ObjectWrap` interface and steers addon authors toward public interfaces and newer alternatives. This is an API-shaping change for native addon guidance, with docs updated to reflect the preferred patterns.
23+
24+
### **src: do not track weak `BaseObject`s as children of `Realm`s** (2fb168f)
25+
Heap tracking was adjusted so weak `BaseObject` instances no longer show up as if they were strongly retained by `Realm`/`Environment` nodes. That fixes misleading heap dumps and makes memory-retainer analysis more accurate for leak hunting.
26+
27+
### Other misc changes
28+
- Primordials/frozen-intrinsics coverage tweaks, including adding `Iterator` to primordials.
29+
- Official ABI registry update for Electron 44.
30+
- Dependency bumps and build metadata updates, including npm 11.17.0 and ngtcp2 configuration.
31+
- Test runner cleanup removing an unused shuffle helper and adding deterministic generator coverage.
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
date: 2026-06-13
3+
repo: oven-sh/bun
4+
size: M
5+
title: "Discord.js guide gets a real slash-command flow"
6+
excerpt: "Bun’s Discord.js docs now walk through a working /ping bot, plus deployment notes and fixed guide links."
7+
commits: 3
8+
authors: [robobun]
9+
commit_authors: {"14bcc6c": robobun, "719be62": robobun, "6f67e09": robobun}
10+
---
11+
12+
### **Discord.js guide rewritten around a working `/ping` bot** (719be62)
13+
The guide now takes readers from setup to a bot that actually responds to a slash command, instead of stopping at login. It adds a separate command-registration script, clearer env handling, and a more production-relevant flow that matches how Discord.js bots are typically deployed.
14+
15+
### **Added deployment guidance for running the bot in production** (6f67e09)
16+
A new closing section explains that Bun can run `bot.ts` directly without a bundling step, so the source can be shipped as-is. It also points readers toward process managers like systemd and PM2 to keep the bot alive after crashes or reboots.
17+
18+
### **Fixed outdated Discord.js guide links** (14bcc6c)
19+
The guide’s links were updated to the new `discordjs.guide` locations after the docs site moved. This keeps the setup instructions from sending readers to dead pages.
20+
21+
### Other misc changes
22+
- Tightened a typo in the Discord.js guide copy.
23+
- Minor wording and phrasing edits in the docs.

src/posts/2026-06-13_pnpm-pnpm.md

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
---
2+
date: 2026-06-13
3+
repo: pnpm/pnpm
4+
size: L
5+
title: "Batch publish lands, lockfile fixes"
6+
excerpt: "pnpm adds recursive batch publishing, plus lockfile and install correctness fixes across pacquet and pnpm."
7+
commits: 11
8+
authors: [zkochan, KSXGitHub, truffle-dev]
9+
commit_authors: {"8dfe438": KSXGitHub, "f1521cf": zkochan, "29981f6": zkochan, "a98767a": zkochan, "4819fb4": zkochan, "f20ad8f": truffle-dev}
10+
---
11+
12+
### **Batch publish packages in one request** (f1521cf)
13+
pnpm now supports an opt-in `--batch` mode for recursive publish, bundling selected packages into a single registry request instead of one per package. That reduces publish overhead and adds all-or-nothing semantics, with a clear error when the target registry doesn’t support the new endpoint.
14+
15+
### **Match install freshness to catalog changes** (29981f6)
16+
Pacquet now treats `catalogs:` drift as lockfile staleness, so changing workspace catalog entries will correctly force a fresh install. This closes a fast-path hole where plain `install` could incorrectly skip after catalog edits.
17+
18+
### **Preserve git-hosted tarball paths in lockfiles** (f20ad8f)
19+
Lockfile resolution now keeps the `path` for git-hosted tarballs that point at a subdirectory, instead of dropping it when the tarball is reserialized. That prevents later installs from unpacking the repository root instead of the intended subfolder.
20+
21+
### **Keep resolver metadata when reusing deprecated entries** (a98767a)
22+
Pacquet’s lockfile reuse path now preserves deprecated metadata instead of losing it during reuse. The added coverage suggests this is a correctness fix for installs that rely on stale-but-reusable lockfile entries.
23+
24+
### **Tighten peer-resolution to match pnpm** (4819fb4)
25+
Pacquet’s peer resolution and lockfile output were aligned more closely with pnpm, including transitive optional peer variants and Yarn-compat package extensions. The change also adds support for `ignoreCompatibilityDb`, which should make pacquet behave more predictably on real-world projects.
26+
27+
### **Catch bare @mentions in commit messages** (8dfe438)
28+
A new Husky commit-msg hook rejects bare `@mentions` unless they’re wrapped in backticks, preventing accidental GitHub notifications from commit messages. The scanner is careful to ignore comments, scissors-cut diffs, and code spans, so it targets only text that would actually be committed.
29+
30+
### **Other misc changes**
31+
- CI/test resource fixes and sharding changes across Jest and clippy runs (4 commits)
32+
- Heavy deps-installer test isolation and worker recycling tweaks (2 commits)
33+
- Publish/release and install test updates, plus minor lockfile/workspace deps bumps (3 commits)
Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
---
2+
date: 2026-06-13
3+
repo: tc39/ecma262
4+
size: N
5+
title: "No changes"
6+
excerpt: ""
7+
commits: 0
8+
---
9+
10+

0 commit comments

Comments
 (0)