Do not include empty packages on the client

[mitar]

I am looking at a simple build of Meteor on the client and I see that packages which do not have any client code are still packaged and pushed to the client. I think this should be a simple optimization to not do that? I also think it would be pretty cool if Meteor would not leak to the client all server-side packages I might be using. It is true that in production those files become a very small line (just _define call), but still, I think it is unnecessary.

Tested with Meteor 1.8.1.

Examples:

//////////////////////////////////////////////////////////////////////////
//                                                                      //
// This is a generated file. You can view the original                  //
// source in your browser if your browser supports source maps.         //
// Source maps are supported by all recent versions of Chrome, Safari,  //
// and Firefox, and by Internet Explorer 11.                            //
//                                                                      //
//////////////////////////////////////////////////////////////////////////


(function () {



/* Exports */
Package._define("mobile-experience");

})();

And the same for:

• static-files
• standard-minifier-css
• standard-minifier-js
• es5-shim (on non-legacy browser)
• modern-browsers
• babel-compiler
• ecmascript
• shell-server
• ecmascript-runtime (there is also ecmascript-runtime-client, why then two packages, if ecmascript-runtime is empty on the client)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mitar]

Still relevant.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[mitar]

Still relevant.