---
title: "no-new-wrappers"
description: "Disallow `new String()`, `new Number()` and `new Boolean()`"
# Generated by src/codegen/lint-rule-docs.ts. Do not edit below this line.
plugin: "eslint"
aliases: ["eslint/no-new-wrappers"]
kind: "suggestion"
category: "pedantic"
default: "off"
fixable: "no"
typeAware: false
deprecated: false
---

With `new`, `String`, `Number` and `Boolean` return an object that wraps the value, not the value itself. `typeof new String("a")` is `"object"`, `new Number(1) === 1` is `false`, and `new Boolean(false)` is truthy, so the `if` below always runs.

Without `new`, the same functions convert a value and return a plain string, number or boolean.

With an oxlint config, `--fix` rewrites `new String("Ada")` to `"Ada"` and `new Number(input)` to `Number(input)`.

{/* Generated by src/codegen/lint-rule-docs.ts. Do not edit this section. */}

## Configure

Off by default. To turn it on:

```toml bunfig.toml
[lint.rules]
"no-new-wrappers" = "error" # or "warn"
```

{/* End of the generated section. */}

## Examples

Reported:

{/* bad */}
```js
const enabled = new Boolean(false);

if (enabled) {
  start();
}
```

{/* bad {"count": 2} */}
```js
const name = new String("Ada");
const port = new Number(input);
```

Not reported:

{/* good */}
```js
const enabled = false;
const name = "Ada";
const port = Number(input);
```