Skip to content

Instantly share code, notes, and snippets.

@coryhouse

coryhouse/package.json

Last active September 26, 2024 04:50
Show Gist options
  • Save coryhouse/b26f49bead69066844d9 to your computer and use it in GitHub Desktop.
Save coryhouse/b26f49bead69066844d9 to your computer and use it in GitHub Desktop.
Download ZIP
Example of calling one script from another
Raw
package.json
{
"name": "npm-scripts-example",
"version": "1.0.0",
"description": "npm scripts example",
"scripts": {
"clean": "rimraf ./dist && mkdir dist",
"prebuild": "npm run clean",
"build": "cross-env NODE_ENV=production webpack"
}
}
@x11x
Copy link

x11x commented Jul 7, 2022

I should note if you are using corepack, you should use corepack enable, not npm -g install .... See the docs

@gulhe
Copy link

gulhe commented Mar 15, 2023 •
edited
Loading

If you are happy to force everyone to use a specific setup

Joke aside: it's not bad practice to write your package.json (or any source for that matter) as it'll be used by your CI and stop there.

Anyone wants anything fancier/newer/better/more-comfy they may do it on their machine but it's up to them.

Joke back on: not my fault if (close to) all CIs are on unix ¯\_(ツ)_/¯

@mcandre
Copy link

mcandre commented Sep 25, 2024 •
edited
Loading

&& assumes a POSIX sh environment. This likely breaks on various and sundry Windows environments, it may break the default (Free)BSD csh. It may break fish, Plan 9's rc, ion, and more.

A Gruntfile or makefile are more portable than NPM's awful built-in task runner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment