- 
                Notifications
    
You must be signed in to change notification settings  - Fork 29.8k
 
Closed
Closed
Copy link
Labels
TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.
Description
Link to the code that reproduces this issue
https://github.com/mantinedev/next-app-template
To Reproduce
- Clone the repository and install dependencies
 - run 
npm run dev - See that 
next-env.d.tsfile changed - run 
npm run build - See that 
next-env.d.tsfile changed again 
As I understood, the next-env.d.ts file must be commited to the vcs and it changing depending on the script might polute the git history.
Current vs. Expected behavior
Current behavior: The next-env.d.ts file changes depending on whether next build or next dev script.
Expected behavior: (same as prior Next.js 16) next-env.d.ts file does not change depending on the script.
Provide environment information
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.0.0: Wed Sep 17 21:41:45 PDT 2025; root:xnu-12377.1.9~141/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 24.8.0
  npm: 11.6.0
  Yarn: 4.10.3
  pnpm: N/A
Relevant Packages:
  next: 16.0.1
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: 5.9.3
Next.js Config:
  output: N/AWhich area(s) are affected? (Select all that apply)
Turbopack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
Information with more details here – mantinedev/next-app-template#46
gfaziolistefanprobst
Metadata
Metadata
Assignees
Labels
TurbopackRelated to Turbopack with Next.js.Related to Turbopack with Next.js.