Jens Fosgerau
Jens Fosgerau
> + initial-value:0 > - initial-value:0% > It seems like some extra CSS minifier strips the percentage sign from the above `@property` value, causing the gradient to stop working. I...
Are there any tickets tracking this issue that you know of, @RobinMalfait?
Following some breadcrumbs, this might have fixed it? https://github.com/cssnano/cssnano/pull/1695 Edit: Seems like nextjs@canary is using [email protected] that doesn't contain the above PR, so maybe upgrading to 7.0.7 could do something.
> That might fix it, but I also think that Next.js is bundling the dependency instead of relying on it as an actual dependency. They also use `cssnano-simple`: https://github.com/vercel/next.js/tree/canary/packages/next/src/bundles/cssnano-simple Yes,...
As a follow-up, I'm confident the PR I referenced earlier does not fix the underlying issue. It's only about `` and quotes around it, it doesn't affect ``. (See my...
We're currently missing "key" on TaxRate. Can we do anything to land this draft in a release? 🚀
Same issue here. Overriding document, window etc. also seems to trip up NextJS's API runtime, so an option to pass in JSDOM as an override would be amazing.
NextJS doesn't seem to extract incoming headers `traceparent` and `tracestate`.
This might be fixed with https://github.com/vercel/next.js/pull/57084 but I haven't tested it yet.
We'd be very interested in this, assuming it hits the go-sdk. Our primary headache is running all microservices locally, and we've been trying various solutions to intercept traffic and route...