Turbopack Error: Next.js package not found

[zlace0x]

Turbopack version: v15.4.5-2-g91e5b6b84
Next.js version: 0.0.0

Error message:

Next.js package not found

Debug info:
- Execution of get_entrypoints_with_issues_operation failed
- Execution of EntrypointsOperation::new failed
- Execution of Project::entrypoints failed
- Execution of AppProject::routes failed
- Execution of directory_tree_to_entrypoints_internal failed
- Execution of get_next_package failed
- Next.js package not found

[zlace0x]

I've tried removing node_modules, any packages-lock.json within apps/ without success.

This happened after trying to reinstall next after prompts of import errors

[zlace0x]

Why does next needs to be hoisted to root?

[icyJoseph]

Yeah that comment looks like it is copy paste from LLM, and without even testing looks like.

• Turbopack Error: Next.js package not found #78192 (comment) this is the comment that ought to be followed

I see, are you using npm? from where do you run the command? at the end of the day, it is likely a good idea to be explicit with the root path, and move on though.

[icyJoseph]

Why does next needs to be hoisted to root?

That depends on your package manager. A pnpm workspace for example, hoists things to the root of your project. You have to explicitly tell the package manager, what dependencies should remain deep on the tree. Even more, if you have a monorepo manager, it might do this for you too.

I see you have node_modules nested, and at the top, does next exist in the nested one? It'd be nice to have a good grasp on where your dependencies really live and how the package manager/monorepo stack, handles them.

[zlace0x]

It doesnt exist in the nested, even when I npm install next within trading-web.

[icyJoseph]

Right, so it is getting hoisted to the root of the project.

[akrmcodes]

Make sure Next.js is installed inside your app package (Make sure Next.js is installed inside your app package (not just in the root).
npm i next -w trading-web
cd trading-web
npm run dev

You can run next dev directly, but it’s usually safer to use => npm run dev <=since it follows the script in your package.json

[zlace0x]

Tried this, didn't work. Ended up switching to pnpm

[akrmcodes]

Makes sense 👍
pnpm usually handles workspaces/hoisting a lot more predictably than npm, especially in monorepos.
If you haven’t already, add a simple pnpm-workspace.yaml at the root to make things smoother.
learned something new myself 😅

Glad you got it working!