-
-
Notifications
You must be signed in to change notification settings - Fork 798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: getBlitzContext() can only be used in React Server Components in Nextjs 13 or higher #4299
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🦋 Changeset detectedLatest commit: 9606722 The changes in this PR will be included in the next version bump. This PR includes changesets to release 8 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
siddhsuresh
added
0 - <(^_^)> - merge it! ✌️
Kodiak automerge
and removed
0 - <(^_^)> - merge it! ✌️
Kodiak automerge
labels
Feb 14, 2024
…ort` possibly causing the issue
…litz-js/blitz into siddharth/remove-thrown-errors
siddhsuresh
changed the title
fix: remove custom errors thrown by blitz for next imports
fix: getBlitzContext() can only be used in React Server Components in Nextjs 13 or higher
Feb 14, 2024
siddhsuresh
commented
Feb 14, 2024
siddhsuresh
commented
Feb 15, 2024
siddhsuresh
commented
Feb 15, 2024
flybayer
approved these changes
Feb 16, 2024
Still not fixed on my side. Blitz version: 2.0.5 (local)
Linux 6.1 | linux-x64 | Node: v20.11.1
Package manager: pnpm
System:
OS: Linux 6.1 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
CPU: (16) x64 AMD EPYC 7B13
Memory: 40.17 GB / 62.79 GB
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.11.1 - ~/.nvm/versions/node/v20.11.1/bin/node
Yarn: 1.22.21 - ~/.nvm/versions/node/v20.11.1/bin/yarn
npm: 10.2.4 - ~/.nvm/versions/node/v20.11.1/bin/npm
npmPackages:
@blitzjs/auth: 2.0.5 => 2.0.5
@blitzjs/next: 2.0.5 => 2.0.5
@blitzjs/rpc: 2.0.5 => 2.0.5
@prisma/client: 5.4.2 => 5.4.2
blitz: 2.0.5 => 2.0.5
next: 13.5.6 => 13.5.6
prisma: 5.4.2 => 5.4.2
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
typescript: ^4.8.4 => 4.9.5 |
@gengjiawen can you open an issue for this? I can't help without more information or a repro. Thanks! |
@siddhsuresh Please see #4303 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes: #4242
What are the changes and their implications?
Bug Checklist
pnpm changeset
in the root directory)