Ngô Đức Anh

@richardHaggioGwati I'm having no problem using React's Context API in appDir without adding a `use client` directive to the main `layout.tsx`. You just have to isolate the provider into a...

@margalit I don't think your issue is related to mine, though yours probably happens because List doesn't contain Item on the server (when you `console.log()` you will see $$typeof, filepath,...

@cwikio that's why you need Typescript 💀

@jookshub I also do '@/components' and '@/components/client' and it's kinda fine tbh. It's an issue with the development build only (at least it was last time I checked), so it...

@irekrog sounds great! I wonder how it just fixes the issue though.

@diegosanz that's nice, I don't recommend exporting Shared/Server Components through files that have `"use client"` at the top of it though. I personally prefer a `client.ts` for Client Components and...

@feledori > Also having this problem with compound components I prefer the method of using Object.assign and that doesn't work. This no longer works (it seems that Next doesn't want...

@akomm this issue has been open for months. There was also a new issue (#46293) and nothing came out of it either after a month, so yeah.

I ended up forking this repo: https://github.com/DuCanhGH/next-pwa (it works with App Router and has built-in TypeScript, JSDoc support - all examples are also written in TypeScript). This happens because [this...

@AaronLayton I don't think his solution would work. If you want to use next-pwa, you can try adding this to your next-pwa config: ```js const withPWAInit = require("next-pwa"); const isDev...