Add a core.umd.js bundle to published package

[mikehaas763]

I'm willing to put the PR together for this. I would like to rely on Overlay and Portal. So it'd be nice to import just a material core.umd.js and avoid the other Material components.

Will the PR be considered/accepted if I take time putting it together?

[devversion]

@jelbourn If we do this, then I would highly recommend after PR #3443. Otherwise there will be X rebases.

Also I think if you just want to use the CoreModule, you can just use the module and use treeshaking to get rid of the other components.

[mikehaas763]

That's fine I'll keep rebasing off your branch until it gets merged!

[mikehaas763]

@devversion meaning point my app's build to CoreModule and compile that?

[devversion]

@mikehaas763 Yeah just using MdCoreModule instead of MaterialModule would do it.

Make sure you have a bundler, like Webpack 2, that automatically removes the unused chunk of code.

[mikehaas763]

Yeah and I've done that before but it always had weird issues when pointing my apps build at something in node_modules. You gotta pretty much set up a completely separate config that ignores any linting etc. would just be nice to consumers to have a core bundle already built

[devversion]

The package structure has changed. Currently we only ship a bundle of the full Material library.

We have plans on shipping the different components bundled as well. This would then include a core.js bundle.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}