src/content/docs/linter/rules/no-invalid-builtin-instantiation.mdx
import { Tabs, TabItem } from '@astrojs/starlight/components';
<Tabs> <TabItem label="JavaScript (and super languages)" icon="seti:javascript"> ## Summary - Rule available since: `v1.7.2` - Diagnostic Category: [`lint/correctness/noInvalidBuiltinInstantiation`](/reference/diagnostics#diagnostic-category) - This rule is **recommended**, meaning it is enabled by default. - This rule has an [**unsafe**](/linter/#unsafe-fixes) fix. - The default severity of this rule is [**error**](/reference/diagnostics#error). - Sources: - Same as [`unicorn/new-for-builtins`](https://github.com/sindresorhus/eslint-plugin-unicorn/blob/main/docs/rules/new-for-builtins.md) - Same as [`no-new-native-nonconstructor`](https://eslint.org/docs/latest/rules/no-new-native-nonconstructor){
"linter": {
"rules": {
"correctness": {
"noInvalidBuiltinInstantiation": "error"
}
}
}
}
Ensure that builtins are correctly instantiated.
The following builtins require new to be instantiate:
Conversely, the following builtins cannot be instantiated with new:
const text = new BigInt(1);
const map = Map([
['foo', 'bar']
]);
const text = BigInt(1);
const map = new Map([
['foo', 'bar']
]);