Enable prod mode about angular-bazel-example HOT 6 CLOSED

Right now we have a layering violation, and it's specifically for Ivy:
https://github.com/bazelbuild/rules_nodejs/blob/e72723558e3eaf998e36af85be3b6ae543efa3d6/internal/rollup/uglify.config.json#L9

this is the right general approach though - the optimizer should use constant folding with a global constant like this.

from angular-bazel-example.

This might be a silly question, but is it currently possible to specify any of the flags listed under --dev vs. --prod builds at https://github.com/angular/angular-cli/wiki/build? It's unclear to me to what extent or how the cli tool is used by the Bazel rules.

from angular-bazel-example.

Its currently not possible to use those flags. There are bazel specific alternatives like creating different ng_modules for different environments, but they are much more manual than what the CLI does with the environment flags

from angular-bazel-example.

Awesome, thanks for answering. If you don't mind, I'm trying to wrap my head around a potential build process. Unless I'm mistaken I don't have to worry about flags like --sourcemaps, because I get them in the output by default. But I'm curious about two things,

Does this use the closure compiler to produce minified output?

Would it be appropriate to use e.g. jsonnet for producing the config that I normally switch using the angular-cli --env flag?

from angular-bazel-example.

This currently uses Rollup/Uglify for bundling and optimization, not Closure Compiler. We have some work-in-progress to hook up closure compiler with Bazel, but it's quite hard to use so we consider that an expert tool. Whereas the setup demonstrated in this repo is simple enough that we should be able to hide all the moving parts under the Angular CLI eventually.

Bazel builds always use AOT. In general, you should expect some configuration options to disappear while moving to Bazel, but at the same time you could compose different bazel rules together to customize the build.

from angular-bazel-example.

Was fixed in a54ce41

from angular-bazel-example.