[Error [TurbopackInternalError]: Next.js package not found

[Nizodevlo]

Link to the code that reproduces this issue

https://github.com/Nizodevlo/Redux.git

To Reproduce

1. first initialized the project with: npx create-next-app@latest ./ --use-pnpm
2. then create this folder structure:
   
3. Add the Store provider to the root layout:
   
   4.execute: pnpm dev
4. here's waht happend:
   

here's the report log:

Current vs. Expected behavior

I tryed to use the store provider in root layout:

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 16076
  Available CPU cores: 8
Binaries:
  Node: 22.12.0
  npm: 11.0.0
  Yarn: N/A
  pnpm: 9.15.1
Relevant Packages:
  next: 15.1.1-canary.16 // Latest available version is detected (15.1.1-canary.16).
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I've used the canary version 15.1.1-canary.16 yet still the same issue

[Ivor808]

I have also been running into this issue on fresh next builds even without redux.

[Ivor808]

@Nizodevlo what error do you get if you build without the --turbopack flag in the pnpm dev cmd?

[Nizodevlo]

@Ivor808 after I removed the flag, it showed the ui for a second but it disappeared.
Here's the error :

It said that I'm using outdated canary version but I'v used this cmd in docs: npm i next@canary
Now I will try it again if its not working. I'm gonna use this cmd: npm i next@latest

After I use "npm i next@latest" it showed different error:

here's the terminal:

I will try again fresh using npm not pnpm to see if there is a difference

[Nizodevlo]

Update:

-I've used just redo everything here's the steps:
1.delete node_modules folder: rm -rf node_modules package-lock.json
2.clear the cache: npm clear cache --force
3.reinstall the dependencies with: npm install

Now it workings:

I think the problem is coming from pnpm. Just my opinion cuz I'm 1year to development

[Nizodevlo]

@Ivor808 try using just npm and see what happend cuz it fixed my problem

[bburgess19]

@Nizodevlo this worked for me! Thanks.

Though, make sure to use

npm cache clear --force

instead of

npm clear cache --force

My issue was caused (I believe) because I moved my project directory around while re-architecting it.

[Ivor808]

yep using just npm fixed my issue. Anyone know if this issue is tracked with pnpm or next?

[Nizodevlo]

No problem brothers.
@bburgess19 thx for the info I always mess up in commands