T04435
T04435
I don't know but I add my fonts as usual in the head as a ```html ``` and after running ***npm run build*** it loaded the font. Thanks, T04435.
> Here's a workaround (i.e., disabling the rule's `noHref` aspect): > > ```json > "jsx-a11y/anchor-is-valid": [ "error", { > "components": [ "Link" ], > "specialLink": [ "hrefLeft", "hrefRight" ], >...
This is my work around ``` // MyLink.tsx import React, { PropsWithChildren } from 'react'; import Link, { LinkProps } from 'next/link'; // This will allow you to pass any...
Any updates on this, using Pulumi not any other infra as code provider? Thanks.
I faced this issue as well my solution uses dynamic import from NEXTJS https://nextjs.org/docs/advanced-features/dynamic-import So Create a component `QR.tsx` (whatever really) and on you Page imported like, important bit is...
I have followed instructions from [Geist npm](https://www.npmjs.com/package/geist?activeTab=readme) and it all worked fine So: ``` // layout.tsx // import your fonts + import { GeistSans } from 'geist/font/sans'; + import {...
same happens if the path provided is `~/components/ui` it creates a folder `~/`
Style issue issue  og 
Not a solution for PROD envs, but... I had this error while setting up the project and I'm on yolo push mode. DO NOT USE IN PROD - connect to...