Just copy all the package names that you want into the .meteor/packages file. The version of these packages that is used is determined by the Meteor release that you use (.meteor/release).
// These are useful too! But you don't have to see their exports
// unless you want to.
api.use([
// We can reload the client without messing up methods in flight.
'reload',
// And update automatically when new client code is available!
'autoupdate'
], ['client', 'server']);
// More mobile specific implies
api.imply([
// Remove the 300ms click delay on mobile
'fastclick',
// Good defaults for the mobile status bar
'mobile-status-bar'
], 'web.cordova');
api.imply([
// Launch screen configuration. Currently only on mobile but we include the
// no-op browser version anyway.
'launch-screen'
], 'web');
Yes you just add those too. If you also want a Cordova app, you can just copy the source code of the meteor-platform package into you /packages folder and modify it there. The .meteor/packages file would then just have your custom meteor-platform package as dependency (just give it another name).
I’ve tried to do that, but when I add webapp package it adds Blaze as a dependency. And if do not add it, it has no main.
Has anyone already dig into it?
Yes. You can create your own modified version of webapp and add it as local package. This will overwrite the original one. The package version must match with the original one.