feat(basic): prefer non global object of node

[zanminkian]

Description

Ban using Buffer and process object without import.

Why: These two objects can only be used in Node. Browser and other runtime (like Deno) have no such objects. Before using them, if we have require or import statement, we can quickly migrate the Node script to browser or Deno by replacing the require('node:process') to another object.

If we don't enforce these rules, we have to check manually, like global searching.

Linked Issues

Additional context

[antfu]

I am not so sure. As we are using process.env.NODE_ENV a lot in front-end to do conditional env logic.

[zanminkian]

Your opinion is reasonable.

I think, mounting Buffer object and process object to global object is a design mistake. It make me difficult to migrate my Node code to Deno. I think all the Node apis (like fs and child_process and Buffer ...) should be required to use.

Maybe we can ban the Buffer first?

[DanSnow]

Just a quick question. From what I understand, eslint-plugin-n is a maintained version of eslint-plugin-node, and the rules from eslint-plugin-node are available in eslint-plugin-n, which includes the prefer-global rule. May I ask why eslint-plugin-node is being used instead of eslint-plugin-n in this case?

[antfu]

Oh I didn't know, thanks. PR welcome to improve it!