We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
System: OS: Windows 10 10.0.19045 CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor Memory: 5.42 GB / 15.92 GB Binaries: Node: 20.10.0 - C:\Program Files\nodejs\node.EXE npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
#1599 seems to be still happening for me, for builds only, both locally and Vercel. I can run the dev server just fine.
I'm using npm and used:"initVersion": "7.24.2"
"initVersion": "7.24.2"
--> known bandaid import "server-only"; makes the error disappear
import "server-only";
https://github.com/josesei/bug-create-t3-app
Create a fresh app with create-t3-app version 7.24.2 using app router and trpc
create-t3-app
7.24.2
The text was updated successfully, but these errors were encountered:
It does build successfully despite the terminal output - check ./.next or try starting a server with pnpm start.
./.next
pnpm start
what you are seeing is the same as this issue: #1663
Sorry, something went wrong.
No branches or pull requests
Provide environment information
System:
OS: Windows 10 10.0.19045
CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
Memory: 5.42 GB / 15.92 GB
Binaries:
Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD
Describe the bug
#1599 seems to be still happening for me, for builds only, both locally and Vercel. I can run the dev server just fine.
I'm using npm and used:
"initVersion": "7.24.2"
--> known bandaid
import "server-only";
makes the error disappearReproduction repo
https://github.com/josesei/bug-create-t3-app
To reproduce
Create a fresh app with
create-t3-app
version7.24.2
using app router and trpcThe text was updated successfully, but these errors were encountered: