Sam Ko

@nilsmehlhorn @mtnhld Thanks for the clarification! > Instead, could you tell us whether Preact will work with Next.js 13 and onward at some point? Not anytime soon I'm afraid →...

@petejodo Thank you for submitting an issue—taking a look!

@petejodo Can confirm this is still an issue. We will be taking a look at this!

@shadowspawn Thank you for the confirmation! Given how things are nicely updated in the root help output (e.g., `description()`) when things are updated in a subcommand, I was expecting it...

@Badlapje The `Developer Experience` was too generic of a label, so it wasn't helpful!

@felipe-linares is it possible to fix your reproduction? I am getting this error. ``` [Error: Invalid interception route: /(..)product/[id]. Cannot use (..) marker at the root level, use (.) instead.]...

* **#67280** 👈 * `canary` This stack of pull requests is managed by Graphite. Learn more about stacking. Join @samcx and the rest of your teammates on Graphite

@onigoetz Thank you for sharing. I can confirm this is an issue we're there is different behavior happening from `next dev / next dev --turbo` and `next build`. We are...

No updates yet, but we are indeed prioritizing this issue! @balatD The CSS merging works as expected versions prior to v14.2.0-canary.28 (just tested on v14.2.0-canary.27).

Hi everyone— Let us know if canary [v15.0.0-canary.56](https://github.com/vercel/next.js/releases/tag/v15.0.0-canary.56) or higher fixes your issue—we recently shipped a bug fix that changes how we merge global css → https://github.com/vercel/next.js/pull/67373. @onigoetz I can...