Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe pull request updates the documentation for the Changes
Possibly related PRs
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (1)
docs/reference/plugins/tanstack-query.mdx (1)
683-691: Consider enhancing the error explanation.The error explanation could be more comprehensive by:
- Briefly explaining why React hooks can't be used in server components
- Adding a link to Next.js documentation about server vs. client components
Consider expanding the explanation like this:
### Next.js error "createContext" is not a function If you see an error like: ```plain Error in Next.js: "TypeError: (0 , react__WEBPACK_IMPORTED_MODULE_0__.createContext) is not a function"-It's usually due to you're using the hooks in a React server component. Make sure to add the
'use client;'directive at the top of your component file.
+It's usually because you're using React hooks in a Server Component. By default, Next.js 13+ components are Server Components which cannot use React hooks or browser APIs. To fix this, add the'use client;'directive at the top of your component file to mark it as a Client Component.
+
+Learn more about Server and Client Components in Next.js.</blockquote></details> </blockquote></details> <details> <summary>📜 Review details</summary> **Configuration used: CodeRabbit UI** **Review profile: CHILL** <details> <summary>📥 Commits</summary> Reviewing files that changed from the base of the PR and between a1f454715d42e16f6de4a86f7e0d7c9ddd7c3d66 and 9d37dfffdc8ff3f7785cb64eb720f3874f9b1cb3. </details> <details> <summary>📒 Files selected for processing (1)</summary> * `docs/reference/plugins/tanstack-query.mdx` (1 hunks) </details> <details> <summary>🔇 Additional comments (1)</summary> <details> <summary>docs/reference/plugins/tanstack-query.mdx (1)</summary> `680-691`: **LGTM! The FAQ section is a valuable addition.** The FAQ section effectively addresses a common Next.js-specific error with clear instructions for resolution. </details> </details> </details> <!-- This is an auto-generated comment by CodeRabbit for review status -->
1 participant
Summary by CodeRabbit
@zenstackhq/tanstack-queryplugin to include a new FAQ section.'use client;'directive.