反应 | webpack | 在 Azure 上获取 process.env.NODE_ENV== undefined

Question

Used below scripts in package.json to set NODE_ENV while creating the build.

"scripts": {
    "build-dev": "set NODE_ENV=development && webpack --config webpack.config.prod",
    "build-client": "set NODE_ENV=production && webpack --config webpack.config.prod",
}

locally if I run "npm run build-dev or build-client" its working correctly and able to read correct NODE_ENV on webpack.config.common.js file.

But if I try same command to create build on Azure pipeline then process.env.NODE_ENV returning as undefined

Not sure on Azure why "process.env.NODE_ENV" returning as undefined. Can someone please help to understand and what needs to be done on Azure to read correct NODE_ENV which was set at the Build time.

Below are the pipeline details

# Node.js
# Build Data Direct UI project with npm.
# https://docs.microsoft.com/azure/devops/pipelines/languages/javascript

trigger: none
#- master

pool: AGENTS

variables:
  system.debug : true
  
steps:

- task: Docker@0
  displayName: 'Build an Image'
  inputs:
    azureSubscription: 'CIS-DEV-001-SC'
    azureContainerRegistry: `{"loginServer":"acrncusd.azurecr.io", "id" : "acrncusd"}`



- task: Docker@0
  displayName: 'Push Image'
  inputs:
    azureSubscription: 'CIS-DEV-001-SC'
    azureContainerRegistry: `{"loginServer":"acrncusd.azurecr.io", "id" :  
    "acrncusd"}`
    action: 'Push an image'
    imageName: `$(Build.Repository.Name):$(Build.BuildId)`

Answer 1

If you're using windows-hosted agent , we should remove the whitespace before and after the && .

Try:

"scripts": {
    "build-dev": "set NODE_ENV=development&&webpack --config webpack.config.prod",
    "build-client": "set NODE_ENV=production&&webpack --config webpack.config.prod",
}