unicorn/no-new-buffer Pedantic

🚧 An auto-fix is still under development.

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.

Example

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 in the CLI or using the config file, you can use:

CLI

oxlint --deny unicorn/no-new-buffer

Config (.oxlintrc.json)

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

References

• Rule Source