Edge Runtime Fix and Build Path Debugging
Two pull requests were merged fixing edge runtime crashes with setImmediate and improving debug build path handling for dynamic routes. Next.js version 16.1.1-canary.32 was also released.
Duration: PT1M17S
Transcript
Good morning, this is Next.js Daily for January 18th, 2026.
Janka Uryga merged a fix for edge runtime crashes caused by accessing setImmediate when it's not defined in the global scope. This addresses an issue where the promisify custom property access would fail in edge environments, following up on previous work to improve async scheduling.
Hendrik Liebau merged improvements to the debug build paths flag, specifically fixing bracket escaping for glob patterns in dynamic routes. The previous implementation failed when glob wildcards like double asterisk preceded bracket expressions because the filesystem existence check couldn't resolve paths containing glob characters. The fix ensures that Next.js dynamic route brackets are always treated as literal directory names rather than glob character classes.
The Next.js bot also published version 16.1.1-canary.32, updating package versions across the monorepo including core packages, ESLint configurations, and developer tools.
What's next: These fixes improve developer experience with debugging tools and ensure more reliable edge runtime behavior. The canary release makes these improvements available for testing in development environments.
That's your Next.js update for today.