environment variables in Win

[jshwlkr]

This particular method of passing environment variables doesn't work in Windows.
https://stackoverflow.com/questions/25112510/how-to-set-environment-variables-from-within-package-json-node-js

[d2s]

Steps to fix the issue

npm install --save-dev cross-env

Modify package.json npm scripts

Modify dev npm script from:

    "dev": "ELEVENTY_ENV=development eleventy --config=eleventy.config.js --serve & gulp dev",

to:

    "dev": "cross-env ELEVENTY_ENV=development eleventy --config=eleventy.config.js --serve  npm run gulp",
    "gulp": "cross-env-shell gulp dev",

This should fix the issue for the people who use Windows as their web development environment.

TODO: I haven't tested how the updated npm script works on Linux or macOS, so you might want to try the updated config on those before applying the change to the public Git repository.

More details

• npm - How to set Environment variables from within package.json [Node.js] - Stack Overflow (as pointed out by the original creator of this GitHub issue ticket)
• cross-env - npm
  • kentcdodds/cross-env
    • "Cross platform setting of environment scripts"

[d2s]

Found a better way to solve the issue.

Steps to fix the issue

Install new dependencies for managing parallel & sequential tasks (npm-run-all) and for managing environmental variables on multiple platforms (cross-env).

npm install npm-run-all cross-env --only=dev

Modify package.json npm scripts

Modify package.json to make npm scripts have more clearly split tasks:

    "dev": "npm-run-all --parallel dev:eleventy dev:gulp",
    "dev:eleventy": "cross-env ELEVENTY_ENV=development eleventy --config=eleventy.config.js --serve",
    "dev:gulp": "cross-env-shell gulp dev",
    "build": "npm-run-all --parallel build:gulp build:eleventy",
    "build:gulp": "gulp build",
    "build:eleventy": "eleventy --config=eleventy.config.js",

This should fix the issue for the people who use Windows as their web development environment.

TODO: I haven't tested how the updated npm script works on Linux or macOS, so you might want to try the updated config on those before applying the change to the public Git repository.

npm-run-all

• mysticatea/npm-run-all
  • "A CLI tool to run multiple npm-scripts in parallel or sequential."
  • npm-run-all - npm
• NPMCompare.com - Comparing concurrently vs. npm-run-all vs. parallelshell
• How to bundle a npm package with TypeScript and Rollup

cross-env

• npm - How to set Environment variables from within package.json [Node.js] - Stack Overflow (as pointed out by the original creator of this GitHub issue ticket)
• cross-env - npm
  • kentcdodds/cross-env
    • "Cross platform setting of environment scripts"

Bonus: Add way to preview the built site

Install serve package.

npm install serve --only=dev

Modify package.json to add npm run serve task.

    "serve": "serve dist"

[atomtigerzoo]

Thank you for the workaround on Windows, but I spotted a bug in the line:

"dev:gulp": "cross-env-shell gulp dev",

It should be:

"dev:gulp": "cross-env-shell gulp",

because there is no dev task, only the default in gulp.