Integrate tern project configuration to package.json

[marcinant]

Feature request:

Project directory is currently cluttered with .tern-project file, although all project settings could be included into package.json file.

https://www.npmjs.org/doc/package.json.html#config

Is this possible to move project config to package.json or at least add this as optional config location?

[marijnh]

NPM's config mechanism seems poorly suited for Tern's purposes. Dumping the config in package.json somewhere might work, but adds to the amount of work plugins have to do to determine where the project directory is (they have to walk the directory tree up, and whereas right now they have to only see if .tern-project exists, with this change they'd also have to read and parse all package.json files they run across).

So I'm not really enthusiastic about this idea, though I'm leaving this open for further discussion.

[AugustSaintFreytag]

Even though it's been 3 years, I'd second that idea – at least as an optional alternative if no .tern-project is found. It sounds like a decent concept since I've gotten used to having the Linter XO configuration within package.json.