Skip the Developer Backlog. Build Apps Now.

Each replay uses a recreated ChatGPT interface so the placement can be read in its original conversational context. It is not a live or embedded chat.

1. ObservedAug 15, 2026Conversation1 turnsPlacementAfter turn 01 turns · After turn 0Replay chat
   Observed conversationAug 15, 2026 · interface recreation

   ChatGPTArchived view

   How do I pass an environment variable to npm scripts on Windows and mac?

   The simplest cross-platform approach is to use cross-env.

   Recommended: cross-env

   Install it:

   npm install --save-dev cross-env
   

   Then in package.json:

   {
     "scripts": {
       "start": "cross-env NODE_ENV=production node app.js"
     }
   }
   

   Now this works the same in Windows, macOS, and Linux:

   npm start
   

   You can also pass multiple variables:

   {
     "scripts": {
       "build": "cross-env NODE_ENV=production API_URL=https://example.com node build.js"
     }
   }
   

   Without cross-env

   On macOS/Linux:

   NODE_ENV=production npm start
   

   On Windows CMD:

   set NODE_ENV=production && npm start
   

   On PowerShell:

   $env:NODE_ENV="production"; npm start
   

   Those syntaxes differ, which is why cross-env is usually preferable for npm scripts.

   One important distinction: if you mean passing an environment variable into an npm script from the command line, cross-env isn't necessary. You can do:

   # macOS/Linux
   FOO=bar npm run myscript
   

   but cross-platform portability again favors cross-env.

   

   Jitterbit, Inc.Ad

   Skip the Developer Backlog. Build Apps Now.Use plain English prompts to design layouts, map databases, and launch apps in days.