Meteorite does not check for bundled packages as dependencies about meteorite

[possibilities]

I see smart.json as a way to extend package.js. In a perfect world smart.json goes away and all the meta data that you'd normally place in it goes in package.js. I imagine it working this way if mrt was merged into meteor core. So for now I want to avoid defining the jquery dependency in both package.js and smart.json. I don't like the metadata is split between the two files but it keeps things simple while we wait to see how long mrt is going to be relevant.

[tmeasday]

Agreed. If it's a core package, you don't need to rely on it in your smart.json; you can just include it in your package.js. Including it in smart.json wouldn't necessitate it actually being added to the user's project anyway.

I'm not totally convinced that they shouldn't be in separate files anyway; this is something we need to consider closely if/when mrt gets merged into core.

[badslug]

Understood. I think the natural tendency would be for devs to focus on editing the smart.json file which could lead to confusing errors but I agree that taking a wait and see stance is the best use of resources.