Devin Clark

> There should be HOWTO for Visual Studio Code's Jest plugin as well (maybe something like eslint's "write to file") I was able to get the Jest plugin working by...

It's a lot easier to see this bug if you enable fullUrl logging in `next.config.js`. Without, it just looks like your app is stalled. ```js const nextConfig = { logging:...

Thanks for the response @Fredkiss3 ! I'm sure it will help someone. Unfortunately for my scenario that won't trigger the suspense boundary because I am loading new data via the...

@Fredkiss3 Thanks for the tweet thread, I hopped in the replies. Since NextJS is handling the boundaries, there should be a way to re-trigger the suspense boundary, whether that's giving...

I was having this issue and realized the culprit was the way I was importing the component to my story. My directory: `src/` `src/index.tsx` `/src/Button` `/src/Button/button.tsx` My component in `button.tsx`...

@shadcn > I initially had an issue with this (on older versions of Next.js 13). I'll give this a try again. Thought to fix this before I saw the ticket...

If you're using this in a component library, you can install emotion as a devDependency and externalize them in your vite.config.ts. ```json "devDependencies": { "@emotion/react": "^11.11.4", "@emotion/styled": "^11.11.0", } ```...

Adding here that this package doesn't work in next 13 for me. Hoping for an update soon! Signup / sign in / auth providers all also not working.

@MarkLyck You could re-export your toast handlers like so: ```typescript export const errorToast = ( message: ReactNode, data?: ExternalToast | undefined ) => { // Custom options in the second...

We catch errors in our backend and return a structured response with an error key to indicate an error. It'd be great to be able to escape hatch by throwing...