Aditya Raj

Hey @Jaibles Can I take this up? Also, based on the video you attached, I had some questions I needed to clarify. Do you just want it for the input...

Hey @elhadis There is a PR already raised with the fix for this issue. But there are still a lot of `good first issues` and `quick wins` that you can...

Hey @shirazdole I dug into this issue and found the cause. It seems to be an issue of browser caching. Everything is updating fine but because the image url stays...

Hey @sean-brydon Could you please suggest a workaround for dealing with this caching of image issue? I have explained the issue in my comment and also attached a video. The...

Hey @mohitk05 , Can I take up this feature? I believe a custom header component shouldn't be necessary because when we pass content then we define our own headers anyway...

I migrated our entire turborepo (3 client apps and a server app) in my last company from Next.js pages to app router when it was just released so I would...

Thanks a lot @Shpigford . I was actually going through the app and noting down the point to plan the upgrade and then raise a better draft request.

@DestroyerXyz I don't think upgrading to canary would be a good idea, we should upgrade to a stable release and the `eslint-config-next` should upgrade too because ideally it goes hand-in-hand...

Screenshot to show the errors that I am addressing in point 2:

> Screenshot to show the errors that I am addressing in point 2: Turns out this was mainly due to the devDependencies `@types/react` & `@types/react-dom` not being upgraded corresponding to...