Home > Web Front-end > JS Tutorial > Detailed explanation of the use of Node.js environment variable process.env

Detailed explanation of the use of Node.js environment variable process.env

php中世界最好的语言
Release: 2018-04-16 15:37:51
Original
4868 people have browsed it

This time I will bring you a detailed explanation of the use of the Node.js environment variable process.env. What are the precautions when using the Node.js environment variable process.env. The following is a practical case. Get up and take a look.

Node environment variables

First of all, when we are developing single-page applications in react and vue, I believe that process.env in config file is not unfamiliar to everyone.

Can not remember? Black question mark.jpg.

It’s the following stuff.

Literally, it is this env attribute. The configuration will be somewhat different in different environments of development and production.

Okay, let's start to see what this so-called process is.

Documentation: http://nodejs.cn/api/process.html

Official explanation: The process object is a global (global variable) that provides relevant information and controls the current Node.js process. As an object, it is always available to Node.js applications, so there is no need to use require().

Process (process) is actually a global variable that exists in nodejs.

Then, we can get some interesting things through this so-called process.

But today we mainly talk about process.env.

process.env

what is this?

Official: The process.env property returns an object containing user environment information.

Documentation: http://nodejs.cn/api/process.html#process_process_env

Oh oh oh, it turns out that this attribute can return some information about the environment where the project is running.

What's the use?

It's an obvious usage scenario, relying on this we can put a label on the server. In this case, we can do some configuration processing according to different environments. For example, turning on sourceMap, switching the domain name of the backend interface, etc.

你是 dev 环境
他是 uat 环境
她是 product 环境。
Copy after login

How to configure environment variables

Let's talk about how to configure the environment variables of each environment.

Windows Configuration

Temporary configuration

Just configure it directly in the cmd environment, view environment variables, add environment variables, and delete environment variables.

#node中常用的到的环境变量是NODE_ENV,首先查看是否存在 
set NODE_ENV 
#如果不存在则添加环境变量 
set NODE_ENV=production 
#环境变量追加值 set 变量名=%变量名%;变量内容 
set path=%path%;C:\web;C:\Tools 
#某些时候需要删除环境变量 
set NODE_ENV=
Copy after login

Permanent configuration

Right-click (This PC) -> Properties (R) -> Advanced System Settings -> Environment Variables (N)...

Linux Configuration

temporary

View environment variables, add environment variables, delete environment variables

#node中常用的到的环境变量是NODE_ENV,首先查看是否存在
echo $NODE_ENV
#如果不存在则添加环境变量
export NODE_ENV=production
#环境变量追加值
export path=$path:/home/download:/usr/local/
#某些时候需要删除环境变量
unset NODE_ENV
#某些时候需要显示所有的环境变量
env
Copy after login

permanent

Open the configuration file location

# 所有用户都生效
vim /etc/profile
# 当前用户生效
vim ~/.bash_profile
Copy after login

Add a statement similar to the following at the end of the file to set or modify environment variables

# 在文件末尾添加如下格式的环境变量
export path=$path:/home/download:/usr/local/
export NODE_ENV = product
Copy after login

After the final modification is completed, you need to run the following statement to reload the system

# 修改/etc/profile文件后
source /etc/profile
# 修改~/.bash_profile文件后
source ~/.bash_profile
Copy after login

Solve the problem of backend interface change caused by environment

After figuring out this problem, we can set different NODE_ENV on machines in different environments. Of course, this field is not necessarily certain.
You can also change to other NODE_ENV_NIZUISHUAI, etc., it is customized anyway.

Solution steps

1. Modify the backend address configuration in the code

It's very simple, just use the process.env.NODE_ENV field to judge. (process is nodeglobal attribute, just use it directly)

2. On linuxSet environment variables

export NODE_ENV=dev
Copy after login

Then you can go and have fun Startup Project.

Said at the end

Because my current project is React server-side rendering. Therefore, the backend request forwarding is not handed over to nginx for processing.
Like ordinary pure single-page applications, nginx is generally used to forward requests.

This article was written relatively quickly, haha. If there are any mistakes in the article, please tell me and I will learn from it.

I believe you have mastered the method after reading the case in this article. For more exciting information, please pay attention to other related articles on the php Chinese website!

Recommended reading:

Implementation method of pre-order, in-order and post-order traversal of JS binary tree

Processing Sublime Text opening Chinese garbled characters in GBK format

The above is the detailed content of Detailed explanation of the use of Node.js environment variable process.env. For more information, please follow other related articles on the PHP Chinese website!

Related labels:
source:php.cn
Statement of this Website
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn
Popular Tutorials
More>
Latest Downloads
More>
Web Effects
Website Source Code
Website Materials
Front End Template