Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

My proposal is suitable for this project

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Link to the rule's documentation

https://typescript-eslint.io/rules/no-throw-literal/

Description

I would like to add an additional option to this rule, allowThrowingTypes, that would allow users to override the current hard-coded behaviour of checking for the global Error class.

I'd find this useful in Remix projects, where you can throw a Response object. Currently, I have to disable this rule, when what I would prefer to do is only allow Error or Response objects to be thrown.

I think this could potentially also be useful in codebases with custom error types, where you want to enforce usage of a more specific subtype of Error.

I'm not sure what the syntax of the option should be - you would need be able to specify the import location and type, rather than just matching on the type name. Are there any other rules where it is possible to precisely specify types in this way?

Fail

throw "/login";

Pass

// with allowThrowingTypes: ["Error", "Response"]
// redirect returns Response & { json(): Promise<never> }
throw redirect("/login");

Additional Info

No response