Skip to content

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

@m1tyya

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugIssue was opened via the bug report template.linear: nextConfirmed issue that is tracked by the Next.js team.locked

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions