[NEXT-689] next dev rewrites isolatedModules to true in tsconfig with typescript 5 option verbatimModuleSyntax set to true

[m1tyya]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.9.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant packages:
  next: 13.2.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

CLI (create-next-app)

Link to the code that reproduces this issue

https://github.com/m1tyya/next-typescript5-bug

To Reproduce

1. Clone repo and install dependencies.
2. Run yarn dev and see changes in tsconfig.json.

Describe the Bug

Typescript 5 has a new option verbatimModuleSyntax which makes isolatedModules redundant. However, starting a dev server sets isolatedModules to true.

Expected Behavior

Not setting isolatedModules value.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-689

[wiesson]

I just want to notice that it happens with next build as well

[belgattitude]

Note that when extending a tsonfig.base.ts, it's still required to add explicitly "verbatimModuleSyntax": true, in the app tsconfig.json. As tested with next 13.4.6

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.