When global Node.js objects are referenced, Deno should error out with a friendly error message

[dsherret]

Extracted from #17475

Objects that will be handled: process, global, Buffer, setImmediate, clearImmediate, module, exports.

Uncaught ReferenceError: process is not defined. 
    To use Node's process object in Deno, add this to `<filename>`:
        import process from "node:process";

For global the hint in the error should be globalThis.global = globalThis.

[aapoalas]

These should probably be LSP FixIts as well.

[calebegg]

I think this may now be obsolete, as deno appears to create an import for node:process automatically

[dmint789]

I'm not sure if this belongs here, but I find it annoying that Deno LSP always highlights the process object as a warning, even with the lint rule no-process-globals disabled. It wants me to do the node:process import, but I can't use that in a Next JS application.

[bartlomieju]

@dmint789 could you please open a new issue for that? This seems like a bug

[dmint789]

@dmint789 could you please open a new issue for that? This seems like a bug

Sure
Edit: #26578