Starred repos weekly — Aug 17–23, 2026: Rust 1.98 lands; Next.js splits stable from canary

Next.js

• Hot watch: The most-commented open thread is [#49279, "App router issue with Framer Motion shared layout animations"] with 142 comments. [#64921, "Inconsistent CSS resolution order with App Router"] has 104 comments. Both remain useful checks for teams using App Router transitions or relying on stable CSS ordering across environments. 34
• Upgrade call — Conditional: Move to v16.3.2 when the application runs the 16.3 line, especially if it uses Turbopack or Turborepo remote caching. Keep v16.4.0-canary.3 in a test lane until the next stable release.

VS Code

• Hot watch: The current comment leaders are [#519, "Allow to change the font size and font of the workbench"] with 600 comments and [#3130, "Allow customization of mouse shortcuts"] with 453 comments. They are long-running workbench requests rather than 1.134 regressions, so they describe product gaps rather than a release blocker. 78
• Upgrade call — Conditional: Upgrade when the new chat and agent workflow solves a current need and the gradual rollout fits the desktop validation process. Hold for a later maintenance window when those features are outside the team’s workflow.

React

• Hot watch: [#13991, "Hooks + multiple instances of React"] has 515 comments and covers misleading Hooks errors when an application loads multiple React instances. [#11347, "RFC: Plan for custom element attributes/properties in React 19"] has 286 comments and remains relevant to custom-element integration. 1011
• Why included now: These two open discussions remain practical upgrade checks for applications with duplicated React packages or Web Components, even with the stable version unchanged this week.
• Upgrade call — Hold: Stay on the tested React version unless v19.2.8 is still missing from the application’s baseline or the Server Components decoding fix addresses a measured workload.

Rust

• Hot watch: The formal comment leader is [#112049, "[do not merge] CI experiments"] with 2,264 comments, an infrastructure pull request with little direct value for application planning. The practical watch is [#32838, "Allocator traits and std::heap"] with 495 comments, where the original summary is outdated and current work sits with a dedicated working group. 1314
• Upgrade call — Conditional: Test Rust 1.98 in compiler, benchmark, and release CI. The release is a strong candidate for applications that need the stabilized APIs or target-support changes; projects sensitive to the compatibility notes should stage the move.

Tailwind CSS

• Hot watch: [#17958, "Error: Cannot find module '../lightningcss.linux-x64-musl.node'"] has 38 comments and remains the main Alpine or musl deployment check. [#15005, "@property isn't supported in shadow roots"] has 33 comments and matters to teams styling Web Components. 1617
• Why included now: The unchanged stable version still needs an environment-specific decision when a project uses Alpine or musl, Shadow DOM roots, polling watch mode, or Windows CJK text.
• Upgrade call — Conditional: Move to v4.3.3 when the release fixes a problem in the project’s environment or the project is below that version. Hold when the current version already covers the workflow and none of the open watch items apply.

Quick reference