Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Environment variable handling in a crossplatform way

See original GitHub issue

Environment variables are passed differently in Windows and unix systems, so we cannot write scripts easily that run on both platforms. It would be very nice if concurrently would include such functionality, so we don’t need to write horrors like

concurrently "cross-env FIRST_ENV=one my-program arg1" cross-env ANOTHER_ENV=two my--other-program arg3

Issue Analytics

State:
Created 3 years ago
Comments:9 (2 by maintainers)

Top GitHub Comments

3reactions

matyasfcommented, Sep 20, 2021

cross-env is no longer developed anymore. Is it OK if I try to submit a PR for this issue?

2reactions

milahucommented, Sep 7, 2021

we can implement both 2 and 3 with backward compatibility (default is --no-parse-env)

Top Results From Across the Web

How to set environment variables in a cross-platform way?

I recently came across the cross-env project. It's pretty straight-forward { "scripts": { "build": "cross-env NODE_ENV=production webpack ...

kentcdodds/cross-env: Cross platform setting of ... - GitHub

The main use case for cross-env-shell is when you need an environment variable to be set across an entire inline shell script, rather...

Variables in any environment - Christopher G. Jennings

To make using them easier, this page provides a quick cross-platform guide to common environment variable tasks. The basics. This table compares how...

Environment Variables: What They Are and How To Use Them

Environment variables add dynamicity to your static code base; you can switch between internal/external resources based on the value of the ...

Tips for Writing Cross-Platform PowerShell Code

on those platforms. Since environment variable names are case-insensitive on Windows, you should prefer the case from Linux/MacOS. Always Use “ ...