ng deploy with prerender builder

[wagnermaciel]

Feature Request

Change our deploy implementation to accept a different build target.

https://github.com/angular/angularfire/blob/master/src/schematics/deploy/actions.ts#L29

Issue

Because the current deploy implementation builds before deploying, it will overwrite the prerendered routes.

Use Case

angular/universal has recently added a builder which prerenders static routes. Our goal is to make it possible for developers to easily deploy their static routes to firebase.

[alan-agius4]

Duplicate of #2063

[michaeljota]

I understand that OP is literally requesting a build target, but prerender is a complete new task introduced by Angular Universal. I read the other issue, and the user would likely be able to do something like this if the user have two different scripts to do it, a first script with ng prerender (I think is called that, will check) and another with ng deploy --no-build.

However, I think this is supoptimal, as I would have to remember the order, or create another script for this.

Maybe you could introduce another configuration property to define the build task, being build the default one.

[alan-agius4]

@michaeljota, I am not following why one would need to remember anything. It would be simply a single to build and deploy command.

ng deploy --build-target project:prerender:prod

The problem is that currently the target and configuration are hardcoded and not configurable.

angularfire/src/schematics/deploy/actions.ts

Lines 28 to 32 in 76f7212

	const run = await context.scheduleTarget({
	target: "build",
	project: context.target.project,
	configuration: "production"
	});

[wagnermaciel]

Closing this issue as it is a duplicate for #2063