I am developing an Angular4 + Meteor app for a while now. I have read a lot about this build/dev process and I have came down to a point of a fundamental question I have been thinking about. That is, should i separate my Meteor project into two separate builds, Front end Angular CLI and backend meteor. I came down to this thought process because the features Angular CLI supports AoT, tree shaking and lazy loading which doesn’t seem to be possible through Meteor CLI yet. I have been looking at meteor-client-bundler to have this setup. Although Meteor has dynamic imports in 1.5, I still don’t believe it will give me the performance boost as native angular CLI would give me. I have noticed a large bundle and very slow rendering times.
Thinking one step ahead, what if Angular comes out with a new build process that Meteor does not inherit straight away. I lose this benefit until Meteor catches up…
Has Anyone have any experience with this type of thinking and implemented a solution. It would be nice to hear from the community before I make a decision to start doing this. As of right now I think this would be the best solution to get the benefits of both worlds and having decoupled CLI.