Question about environment variables: import.meta.env.DEV|PROD

[usedlife]

Description of two fields in rsbuild:

• If mode is 'development', the value is true; otherwise, it is false.
• If mode is 'production', the value is true; otherwise, it is false.

If use rsbuild, writing import.meta.env.DEV is actually equal to import.meta.env.MODE === 'development'
So what's the point of import.meta.env.DEV | import.meta.env.PROD?

in vite:

• import.meta.env.DEV: {boolean} whether the app is running in development (always the opposite of import.meta.env.PROD)
• import.meta.env.PROD: {boolean} whether the app is running in production (running the dev server with NODE_ENV='production' or running an app built with NODE_ENV='production').

I can judge by import.meta.env.DEV that it is running on a local server to do development. Why not maintain consistency with Vite instead of declaring redundant fields?

[chenjiahan]

When using Rsbuild, you can judge that it is running on a local server from import.meta.env.DEV, as in most cases the app will use mode: 'development' for local dev development.

[usedlife]

Another situation is building and deploying with mode: 'development' to the testing server, by detecting the dev server, certain content, such as development plugins, can be hidden from testers.

[chenjiahan]

Can you share the reasons for deploying with mode: 'development'? Perhaps this can be satisfied with other configurations.

[usedlife]

Can you share the reasons for deploying with mode: 'development'? Perhaps this can be satisfied with other configurations.

I see. When run rsbuild build, the mode should be prodoction. It has a different meaning than vite's mode

[chenjiahan]

Yes, Rsbuild's mode can only be production development or none.