unicorn/no-new-buffer Pedantic

🚧 An auto-fix is planned for this rule, but not implemented at this time.

What it does

Disallows the deprecated new Buffer() constructor.

Why is this bad?

Enforces the use of Buffer.from and Buffer.alloc() instead of new Buffer(), which has been deprecated since Node.js 4.

Examples

Examples of incorrect code for this rule:

const buffer = new Buffer(10);

Examples of correct code for this rule:

const buffer = Buffer.alloc(10);

How to use

To enable this rule using the config file or in the CLI, you can use:

Config (.oxlintrc.json)

{
  "rules": {
    "unicorn/no-new-buffer": "error"
  }
}

CLI

oxlint --deny unicorn/no-new-buffer

References

• Rule Source