-
-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
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
extendsentry intsconfig.json
This would help preserve the out-of-the-box typing experience for users migrating from v2.
What do you think?
Metadata
Metadata
Assignees
Labels
No labels