feat(basic): prefer non global process object

[zanminkian]

Description

I've re-thought it carefully.

• For people who use vite, they should use import.meta.env.PROD. See https://vitejs.dev/guide/env-and-mode.html.
• For people who use webpack, they should use new webpack.DefinePlugin({'import.meta.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV)}) to inject it. See https://webpack.js.org/plugins/environment-plugin/

Any way, we should not use process.env in frontend projects. So enable this rule will benefit node projects.

BTW, why did not vite document mention the process.env but import.meta.env? Maybe vite author do not recommend us to use process.env in frontend project. 😆

Linked Issues

Additional context

#159

[cuebit]

This does not take into consideration applications that use string replacement for environment definitions. For example, all Nuxt applications will require this to be disabled or set to "always".

[Hebilicious]

cc @antfu can confirm that this breaks the types of all my nuxt projects and modules 😅

[cuebit]

FYI this won’t be an issue in the much anticipated release of Nuxt 3.7 nuxt/nuxt#22428