Slava Kim

We can have a boolean in `.tern-project` like `{"plugin":{"meteor":{"isPackage": true}}}`. In that case, for packages we would start the analysis from `package.js`. Otherwise we would load everything with `packages/*/package.js` first.

Right now we require users to put 'loadEagerly' option with all those `*.js, */*.js` things. This is not very cool as well as it is not correct. The scoping can...

For app-code: - use same rules as [bundler](https://github.com/meteor/meteor/blob/devel/tools/bundler.js) for file's path to put the code in either `client` or `server` category. - understand `isClient` and `isServer` blocks For packages: -...

Improve tern's `condense` tool. The ideal variant is teach this project to deal with packages and then supply the plugin to tern's `condense`. (right now it looks like a circular...

We could use `{loadEagerly: ["/packages/*/package.js", ... ]}` to load `package.js` file first and then load other files and understand the exports. We _don't_ want to load everything to make it...

Scoping rules are different for app vs packages. In app, every file has its own scope and the global scope is app-wise. In package, every file has its own scope,...