npm scriptsare low-level and leverage the actual library you want to use (example:"lint": "eslint ./")package.jsonis a central place to see what scripts are available (alsonpm runwill list all scripts)- When things get too complicated you can always defer to another file (example:
"complex-script": "babel-node tools/complex-script.js") npm scriptsare more powerful than one might first think (pre/post hooks, passing arguments, config variables, chaining, piping, etc...)