KEMBAR78
Ability to pass a custom tsconfig for `next dev` · Issue #8060 · vercel/next.js · GitHub
Skip to content

Ability to pass a custom tsconfig for next dev #8060

@jerrygreen

Description

@jerrygreen

Feature request

Is your feature request related to a problem? Please describe.

I'm bored of seeing someVar is declared but its value is never read:

I'm actively write and delete code, exploring some libraries' features - I don't want my dev server to stuck me into an error. Of course it's bad to leave them. Of course my IDE should highlight that - and for that reason, I want to have noUnusedLocals or noUnusedParameters, strict in overall. Of course there should be some pre-commit hook that will prevent me from committing this clutter into the repository. But I don’t want my dev server to throw noUnusedLocals and noUnusedParameters - I don't want it to prevent me playing with the code.

UPD. That’s okay for the default behavior, but there should be an option that these keys should be enabled by VSCode, and by linter, but not used by dev server so it won’t throw error that prevents you to do anything.

Describe the solution you'd like

I'd like an ability of passing a tsconfig path for next dev command.

Something like:

next dev --tsconfig=tsconfig.devserver.json

While I can use the original tsconfig.json for my IDE.

Describe alternatives you've considered

Well, I could make an issue for IDE (vscode doesn't support anything other than tsconfig.json too), but anyway - both sides should support that.

UPD. There's one: microsoft/vscode#12463. Still, both sides should support that.

Additional context

Idk maybe it's possible. But I don't see it from next dev --help:

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions