by default, npm install and npm start look for package.json.
Is there a way to specify to use a different package.json file?
========
Something like package.json, package_dev.json, package_staging.json, package_dev_features.json when run npm install, i can specify which package*.json to be used instead of the default package.json
========
The reason is, it may be easier to handle using different packages for development / testing.
========= Final solution:
At the end, i just have one package.json for each environment (or branch). and set environment for dependencies . e.g. 'myLodash':"github.com/.../myLodash.git#testing"
Then when I merge from one environment to another, (e.g. from testing to staging), I merge the package.json. and then run a script to check & update the dependencies. Then push the updated package.json
it is a bit more works but it works. :)
=========