Skip to content
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

bug: pnpm dev not working in older versions of Node 18 #1600

Closed
williamneves opened this issue Oct 16, 2023 · 10 comments
Closed

bug: pnpm dev not working in older versions of Node 18 #1600

williamneves opened this issue Oct 16, 2023 · 10 comments

Comments

@williamneves
Copy link

williamneves commented Oct 16, 2023

Provide environment information

System:
OS: macOS 13.4.1
CPU: (10) arm64 Apple M1 Pro
Memory: 201.78 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 19.6.0 - ~/.nvm/versions/node/v19.6.0/bin/node
npm: 9.4.0 - ~/.nvm/versions/node/v19.6.0/bin/npm
pnpm: 8.8.0 - ~/.nvm/versions/node/v19.6.0/bin/pnpm

Describe the bug

Just is not loading at the first installation. I tried ran pnpm create t3-app and use the AppRoute, but after all installation (with works well), when I open the localhost:3000, the error pops:

Unhandled Runtime Error
Error: Missing result

Call Stack
TRPCClientError.from
node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@trpc/client/dist/TRPCClientError-0de4d231.mjs (37:15)
from
node_modules/.pnpm/@[email protected]_@[email protected]/node_modules/@trpc/client/dist/httpBatchLink-204206a5.mjs (200:55)
process.processTicksAndRejections
node:internal/process/task_queues (95:5)

Reproduction repo

don't needed

To reproduce

Just
pnpm create t3-app

Options Selected:

  • Auth: none,
  • TS
  • TW
  • App Route
  • ~/

pnpm dev

Additional information

No response

@player0x3
Copy link

when you run: pnpm build
image

@kwerenta
Copy link

Downgrading to Next.js 13.5.4 fixes "Missing result" error

@c-ehrlich
Copy link
Member

CleanShot 2023-10-17 at 21 17 00@2x

could you give more detailed steps or provide a repo from which this can be reproduced? it's working for me, including with Next 13.5.5

@pablasso
Copy link

@c-ehrlich hopefully you're able to reproduce with this repo: https://github.com/pablasso/reproduce-no-results, the same thing was happening with me with npm and latest next.

The problem is also solved for me when pegging nextjs to 13.5.4 like @kwerenta mentioned.

Error thrown:

Unhandled Runtime Error
Error: Missing result

Call Stack
TRPCClientError.from
node_modules/@trpc/client/dist/TRPCClientError-0de4d231.mjs (37:15)
from
node_modules/@trpc/client/dist/httpBatchLink-204206a5.mjs (200:55)
process.processTicksAndRejections
node:internal/process/task_queues (95:5)

Installed versions:

  • Node: v18.12.1
  • NPM: 8.19.2
  • NextJS: 13.5.5

Used options:

  • Typescript
  • Tailwind, yes
  • tRPC, yes
  • Auth provider, none
  • ORM, none
  • Nextjs App Router, yes

@williamneves
Copy link
Author

CleanShot 2023-10-17 at 21 17 00@2x

could you give more detailed steps or provide a repo from which this can be reproduced? it's working for me, including with Next 13.5.5

I just created a new project with the latest version, install and pnpm run the project and get this error.

@williamneves
Copy link
Author

I found also the solution, but this not end the issue, but at least work,

go to the package.json and to "next": "^13.5.4" and change to "next": "13.5.4", with this you get fixed to 13.5.4 and solve the error, so, next on version 13.5.5 is not working yet.

@sscotth
Copy link

sscotth commented Oct 18, 2023

Worked for me with Next v13.5.5. I did get the pnpm build error though

macOS Sonoma 14.0 (arm)
Node v20.8.1
pnpm v8.9.2

Screenshot 2023-10-17 at 22 02 15

No issues with @pablasso 's repo either. Tried Node v18.18.2 too, same result.

image

@c-ehrlich c-ehrlich changed the title bug: pnpm dev not working bug: pnpm dev not working in older versions of Node 18 Oct 18, 2023
@c-ehrlich
Copy link
Member

Thanks for the repo. I can reproduce with node v18.12.1. With the current Node 18 version (18.16.0), it works fine. So if you want a quick fix, upgrade your node version. But I guess we'll also need to think about how to guide people who run into this.

@pablasso
Copy link

You're right! I upgraded to latest LTS (v18.18.2) and it works fine. Thanks for looking into it.

IMO this could be closed.

@c-ehrlich
Copy link
Member

opened a pr to prevent people from hitting this :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants