I second tedmiston's point above. It's mainly convenience (running `npm run` which can be auto-completed with a shell integration too), but also discoverability: If you're switching between multiple projects, its nice to know that you can simply look there for the commands that you're able to run.
I especially like the package.json scripts for simple one-liners, if I have something complicated I might also create a ./scripts directory with a script and call that from an npm run-script.
Looks great from the website. I like that it seems to do one thing and do it well
Unfortunately it's not super easy for teams to add a Slack bot to their channel in large companies (with an IT department), so I can't take it for a spin
I built this package while working on an app that I deployed to production, staging and my local dev environment. I had a couple of scripts (one to deploy, one to migrate the database, etc.) that I wanted to run, but I didn't want to have to maintain one script for each environment doing almost the same but to different endpoints.
So, I built a simple CLI that reads one or more .env files and spawns a new child process running an NPM script from the package, with the environment variables extended with the contents of the files.
It also supports expansion, where one file use the value defined in another file.
Please see the README for more details and usage and consider giving it a spin in your next project if you're faced with a similar problem.
"The battle for talent is as important as the battle for customers." I totally agree .. With an amazing product, customers won't be able to not use a CRM system such as Zendesk.
I especially like the package.json scripts for simple one-liners, if I have something complicated I might also create a ./scripts directory with a script and call that from an npm run-script.