I have a complex production environment driven by package.json.
The problem: I wish to install locally some additional packages, keep an eye on the list and versions of them.
Solution (how to get there): point npm to use another config file, excluded from git, which would keep my private dependencies. Use the file to add packages to local node_modules with npm install. So actually all I need is to change configuration context of npm.
I have no clue how to point npm to use a different config (something like gulp -gulpfile).
Update from comments The dev-dependencies is not the way to go. I use stuff 90% of other developers do not need to get installed in their node_modules (in fact I could break their environment in a strange way updating dev-dependencies in git-shared core project-wide package.json).