Maikel van Dort

Hi all, We've also hit a point where we would like to mock server-side data requests, as playwright currently only supports client-side intercepting. We currently have a POC using msw,...

> Interestingly the docs do suggest that it should work across type boundaries, but there aren't any unit tests for that scenario, and the code clearly doesn't support it. So,...

> The original issue author didn't end up having time to complete the work on this, if anyone else wants to take a stab at addressing it. Sadly I don't...

Would love to know too @joeworkman :)

> I am working with the Sass team in order to migrate off `@include` and over to `@use`. It's a big deal. Maybe I should release what I already have...

Faced similar issues, ended up using something like: https://github.com/vercel/next.js/discussions/18301#discussioncomment-113660

hi 👋 I see this PR has been stalled for a while. We're are currently implementing shared caching with next 15 and would love this update 👀

> Have you looked into using `AsyncLocalStorage`? See [this article](https://dev.to/rexessilfie/using-asynclocalstorage-in-nextjs-44c8) We make use of Nextjs' workUnit, which headers() use under water ```ts import { throwForMissingRequestStore, workUnitAsyncStorage, } from 'next/dist/server/app-render/work-unit-async-storage.external'; //...

Partially related; https://github.com/parcel-bundler/lightningcss/issues/969 & https://github.com/parcel-bundler/lightningcss/issues/872

@devongovett any ideas? For backwards compatibility vendor-prefixes are sometimes needed, with `appearance` for example