Thanks to visit codestin.com
Credit goes to github.com

Skip to content

typescript non-strict #369

@akomm

Description

@akomm

I just realized why so many errors in the typing could remain unnoticed. Its because you run on strict: false. No serious typescript project, except those migrating from pure JS to TS incrementally, will have it set to false, otherwise its totally pointless.

Are there amy plans changing this? Also what makes some things to fix for strict now hard is the fact that you mutate objects like for example the request, making it harder to proper type it, wit hout copy & pasting vendor (next) types to adjust them, which makes code more prone to changes on nextjs side of typings. But I think changing this is due to huge BC break it would need is not to debate ;(

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions