Maikel van Dort
Maikel van Dort
Still working on this one? @kedevked :)
> Hello ! I encountered the same issue after upgrading to apollo v4 but I haven't succeed to resolve it like you describe. I got some other types with invalid...
Uff we're struggling with the same issue, not necessarily a typical barrel file. A typography & card component, both from the same package, where the card component uses the typography...
As we now also get typed env variables, will we also get typed page & layout params? (Kind of like NextPage type of the pages directory, but the params attribute...
> includePaths is not working either with turbo. In NextJS v16 they bumped to sass-loader v16, which includes using the modern Sass API by default as the legacy Sass API...
@dotansimha @ardatan @dimaMachina friendly ping 😅
I don't think strikethrough would be the right approach, maybe something else...?
> The element check for if it should scroll (specifically topOfElementInViewport > > [next.js/packages/next/src/client/components/layout-router.tsx](https://github.com/vercel/next.js/blob/87fb29ee7143c1e9a4c129585f9546c3f5e0b2b8/packages/next/src/client/components/layout-router.tsx#L151) > > Line 151 in [87fb29e](/vercel/next.js/commit/87fb29ee7143c1e9a4c129585f9546c3f5e0b2b8) > > function topOfElementInViewport(element: HTMLElement, viewportHeight: number) { > )...
The SASS team even mentioned this already themself; https://github.com/vercel/next.js/discussions/67931
Having the same issue, but trying to query for table elements of; https://stylelint.io/user-guide/rules (while it does work on other websites) If I go over the object returned from the `parse()`,...