[Turbopack] The behavior of turbopack is different with and without it (3 issues)

[MrOxMasTer]

Goals

I'm tired of riveting examples for this repository so I'll leave it here, promote it if you can.

Turbopack has gone to a stable version, and still I keep noticing different behaviour and I'm already starting to doubt my knowledge of next.js every time.

0. Here we see an error that occurs because I used cookies() and didn't put in connection, which of course doesn't say that it should be put in now, and the links don't give much information either

   ▲ Next.js 15.1.7
   - Environments: .env
   - Experiments (use with caution):       
     · reactCompiler

   Creating an optimized production build ...
(node:23492) ExperimentalWarning: CommonJS module C:\Users\user\Desktop\petProjects\shopco\src\shared\configs\env.ts is loading ES Module C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\@t3-oss+env-nextjs@0.11.1_typescript@5.7.1-rc_zod@3.24.1\node_modules\@t3-oss\env-nextjs\dist\index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:23788) ExperimentalWarning: CommonJS module C:\Users\user\Desktop\petProjects\shopco\src\shared\configs\env.ts is loading ES Module C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\@t3-oss+env-nextjs@0.11.1_typescript@5.7.1-rc_zod@3.24.1\node_modules\@t3-oss\env-nextjs\dist\index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
(node:39340) ExperimentalWarning: CommonJS module C:\Users\user\Desktop\petProjects\shopco\src\shared\configs\env.ts is loading ES Module C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\@t3-oss+env-nextjs@0.11.1_typescript@5.7.1-rc_zod@3.24.1\node_modules\@t3-oss\env-nextjs\dist\index.js using require().
Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
 ✓ Compiled successfully
Error occurred prerendering page "/auth/signin". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Dynamic server usage: Route /auth/signin couldn't be rendered statically because it used `cookies`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
    at m (C:\Users\user\Desktop\petProjects\shopco\.next\server\chunks\573.js:1:41161)
    at d (C:\Users\user\Desktop\petProjects\shopco\.next\server\chunks\694.js:1:13606)
    at C:\Users\user\Desktop\petProjects\shopco\.next\server\chunks\358.js:1:49616    
    at C:\Users\user\Desktop\petProjects\shopco\.next\server\chunks\694.js:5:69094    
Export encountered an error on /(main)/(Footer)/auth/signin/page: /auth/signin, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null
 ELIFECYCLE  Command failed with exit code 1.

 *  The terminal process "C:\Program Files\PowerShell\7\pwsh.exe -Command pnpm run next:build" terminated with exit code: 1. 

Once we have added the coveted connection to the place where we use cookies() - we can move on

1. Look at the work with turbopack. Here, with js disabled, we can see turbopack trying to load something that doesn't exist (there's nothing in the markup)
   

2. Let's see the behaviour without turbopack. It's not trying to download anything
   

3. Here in standalone build my application got epilepsy and started to call global loader magically
   https://github.com/user-attachments/assets/6fb571f8-19b8-4a70-a228-79b0cb472c3d

All of this without the js

4. Because of the wonderful standalone build I had a build accident, I just stopped running dev mode and now I have to reinstall all the dependencies

▲ Next.js 15.1.7
   - Local:        https://localhost:3000
   - Network:      https://172.26.80.1:3000
   - Environments: .env
   - Experiments (use with caution):       
     · reactCompiler

 ✓ Starting...
Error: Cannot find module 'next/dist/pages/_app'
Require stack:
- C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\next@15.1.7_@babel+core@7.26.7_babel-plugin-react-compiler@19.0.0-beta-27714ef-20250124_react_pqt3saljkuvrmgosfexzmj27zy\node_modules\next\dist\build\entries.js
- C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\next@15.1.7_@babel+core@7.26.7_babel-plugin-react-compiler@19.0.0-beta-27714ef-20250124_react_pqt3saljkuvrmgosfexzmj27zy\node_modules\next\dist\server\dev\hot-reloader-webpack.js
- C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\next@15.1.7_@babel+core@7.26.7_babel-plugin-react-compiler@19.0.0-beta-27714ef-20250124_react_pqt3saljkuvrmgosfexzmj27zy\node_modules\next\dist\server\lib\router-utils\setup-dev-bundler.js        
- C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\next@15.1.7_@babel+core@7.26.7_babel-plugin-react-compiler@19.0.0-beta-27714ef-20250124_react_pqt3saljkuvrmgosfexzmj27zy\node_modules\next\dist\server\lib\router-server.js
- C:\Users\user\Desktop\petProjects\shopco\node_modules\.pnpm\next@15.1.7_@babel+core@7.26.7_babel-plugin-react-compiler@19.0.0-beta-27714ef-20250124_react_pqt3saljkuvrmgosfexzmj27zy\node_modules\next\dist\server\lib\start-server.js
    at Array.map (<anonymous>) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [Array]
}

5. Removing the next.js folder doesn't help:

> next dev --experimental-https

node:internal/modules/cjs/loader:1252
  throw err;
  ^

Error: Cannot find module 'C:\Users\user\Desktop\petProjects\shopco\node_modules\next\dist\bin\next'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1249:15)
    at Function._load (node:internal/modules/cjs/loader:1075:27)
    at TracingChannel.traceSync (node:diagnostics_channel:322:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:219:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:170:5)
    at node:internal/main/run_main_module:36:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.12.0
 ELIFECYCLE  Command failed with exit code 1.

 *  The terminal process "C:\Program Files\PowerShell\7\pwsh.exe -Command pnpm run next:dev" terminated with exit code: 1. 

Non-Goals

No response

Background

I think it would be nice if these errors didn't occur.

Proposal

I think it would be nice if these errors didn't occur.