'export' is not recognized as an internal or external command

# 'export' is not recognized as an internal or external command

The error "'export' is not recognized as an internal or external command, operable program or batch file" occurs when we use the export command on Windows, in a CMD shell.

To solve the error, use the set command to set environment variables.

Copied!
'export' is not recognized as an internal or external command, operable program or batch file

The term 'export' is not recognized as the name of a cmdlet, function, script file, or operable program.

The set and setx commands are the Windows equivalent of the Unix export command in CMD.

Copied!
# 👇️ set an environment variable
set DB_URL=example.com

# 👇️ print an environment variable's value
set DB_URL

echo %DB_URL%

If you use PowerShell, you would use the $env: command.

Copied!
# 👇️ set an environment variable
$env:POST_CODE="abc123"

# 👇️ print an environment variable's value
$env:POST_CODE

However, it is much more intuitive to use CMD to set environment variables, so the following examples use CMD.

You can use the set command to print the values of all environment variables.

Copied!
set

You can unset an environment variable by setting it to nothing after the equal sign.

Copied!
# 👇️ set an environment variable
set DB_URL=example.com

# 👇️ print an environment variable's value
set DB_URL

# 👇️ unset an environment variable
set DB_URL=

# 👇️ "Environment variable DB_URL not defined"
set DB_URL

You can enclose a variable in percent signs to evaluate its value.

Copied!
set DB_PORT=1234

set DB_URL=example.com:%DB_PORT%

# 👇️ "DB_URL=example.com:1234"
set DB_URL

echo %DB_URL%

Note that the set command doesn't set environment variables permanently.

The set command:

• modifies the environment variables in the current shell only, and not the other active shells.
• the modified variables are available in the current shell session but are temporary and get removed if you restart your shell.

The setx command:

• modifies the environment variables for future shells permanently.
• the changes are not reflected in currently active shell sessions.
• you have to close and reopen the shell to be able to access the updated environment variables.

# Using setx to set environment values permanently

Here is an example of using setx to permanently set environment values.

Copied!
setx DB_URL example.com

# 👇️ it's still not defined
set DB_URL

Instead of separating the variable name and its value with an equal sign, they're separated with a space when using setx.

However, if I close the shell and reopen it, the DB_URL variable is available.

Copied!
# 👇️ New shell session (DB_URL=example.com)
set DB_URL

# 👇️ DB_URL=example.com
echo %DB_URL%

An alternative way to set and edit environment variables permanently is to use "Control Panel".

# Using Control Panel to set environment values permanently

To use Control Panel to set environment values permanently:

1. Click on the Search bar and type "environment variables".
2. Click on "Edit the system environment variables".

3. Click on the "Environment Variables" button.

4. In the "System variables" section, click on "New".

5. In the "New system variable" window, enter a name and a value for the environment variable.

6. Click on "OK" twice to confirm the changes.

7. Close your Command prompt application and then reopen it.

Open a new Command prompt window and display the value of your environment variable.

Copied!
echo %TEST_VAR%

set TEST_VAR

If you want to display the environment variable in PowerShell, you would use the $env: syntax.

Copied!
$env:TEST_VAR

This approach also sets environment variables permanently.

# Additional Resources

You can learn more about the related topics by checking out the following tutorials:

• 'sudo' is not recognized as an internal or external command
• The term 'pip' is not recognized as the name of a cmdlet
• 'touch' is not recognized as an internal or external command
• 'vim' is not recognized as an internal or external command
• 'vite' is not recognized as an internal or external command
• 'wget' is not recognized as an internal or external command
• 'nano' is not recognized as an internal or external command
• process.env.NODE_ENV is undefined issue [Solved]
• gcc is not recognized as an internal or external command
• Treating warnings as errors because process.env.CI = true