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.

Not choosing task

See original GitHub issue

I have the following scripts setup:

  "scripts": {
    "start": "per-env",
    "start:development": "npm run build:development",
    "start:production": "npm run build:production",
    "clean-styles": "rimraf web/css && mkdirp web/css",
    "build": "per-env",
    "build:development": "npm run styles:development",
    "build:production": "npm run styles:production",
    "prestyles": "per-env",
    "prestyles:development": "npm run clean-styles",
    "prestyles:production": "npm run clean-styles",
    "styles": "per-env",
    "styles:development": "node-sass src/sass/main.scss | postcss -u autoprefixer > web/css/style.css",
    "styles:production": "node-sass src/sass/main.scss | postcss -u autoprefixer | cleancss > web/css/style.css"
  }

When I run npm start I just get the output showing per-env is running and then it finishes before going to the next task.

I’ve tried using the example setup from the readme but I’m getting the same issue. I’m running this on Windows 10, I haven’t tried on a Mac yet.

Issue Analytics

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

Top GitHub Comments

2reactions

louisflycommented, May 16, 2017

I have experienced the same on windows, and the “FIX on windows” - https://github.com/ericclemmons/per-env/pull/10 seems to work! An update to the module would be cool…

1reaction

qiulangcommented, Sep 29, 2018

@ericclemmons hi it seems no one does that so I just created a pull request for it using cross-spawn . I test on window, no extensively though, but the change is simple.