Ban does not detect after 'new' Keyword.

[marvinside]

Bug Report

• TSLint version: 5.11.0
• TypeScript version: 3.2.0-dev.20181010
• Running TSLint via: VSCode

TypeScript code being linted

const a:Error = new Error("ABC"); 	// fine
const b:Error = Error("ABC"); 		// TSLint shows Error as Expected

with tslint.json configuration:

"ban": [
	true,
	{"name": "Error", "message": "Use Meteor.Error instead."}
],

Actual behavior

Only the second Line is marked as an Error

Expected behavior

Both Lines (with and without new Keyword) should trigger an Error.

Background Information

We use meteor to develop. Meteor provides the Class Meteor.Error (which extends the Normal Error).
This allows to include more details into the Error, but usually just Error is used.
By banning the Normal Error, developers should use the Meteor.Error and provide better Error messages.

[stnwk]

I would also love to have a solution to this problem. Anyone got any ideas?

[JoshuaKGoldberg]

Related: #2791

[JoshuaKGoldberg]

💀 It's time! 💀

TSLint is deprecated and no longer accepting pull requests other than security fixes. See #4534. ☠️
We recommend you instead use typescript-eslint to lint your TypeScript code with ESLint. ✅

👋 It was a pleasure open sourcing with you!

[JoshuaKGoldberg]

🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖

🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋