Move some of project.config.js into package.json?

[baer]

I was reading about the future of npm and it's about to get crazy. The tldr; of the post is that npm is being broken apart into 3 modules: a registry, a cache and an installer in such a way that you could use BOTH Bower and NPM (of today)'s version of dependency resolution at the same time.

This is largely in response to the fact that lots and lots of people use NPM, a purposefully nody tool as a dependency resolution tool for projects that have nothing to do with node. They are moving to a "roll your own dependency system" to make it more flexible for projects that mix frontend and node. Interestingly the roll your own thing is what Express is doing too with Pilar.js in Express 5.

Anyway, the npm folks issued a call to action on the new plan which involves a few things - one of them is moving more config into your package.json. I thought I'd see what you thought about moving some of project.config.js into the package.json.

[divmain]

I think I'd prefer to see what best practices materialize before using that pattern here. I'll leave this issue open, and we can revisit in a couple of months.