Skip to content

Enable tsconfig generation by default #6

@schplitt

Description

@schplitt

Coming from Nitro v2, it was a bit surprising that useRuntimeConfig() is no longer automatically typed by default.

This happens because tsconfig generation is not enabled by default in newly scaffolded Nitro projects.

I’d like to propose that the default Nitro scaffold:

  • enables automatic tsconfig generation, and
  • includes an uncommented extends entry in tsconfig.json

This would help preserve the out-of-the-box typing experience for users migrating from v2.

What do you think?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions