Closed johnpapa closed 4 years ago
I have started a discussion at ngx-deploy-starter RFC #1 about a standardised set of options. It would be great if we could find a common approach so that the expected behaviour and usability of the different builders are consistent.
--configuration
(alias -c
): A named build target, as specified in the "configurations" section of angular.json--no-build
: Skip build process during deployment
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
The app builds and then deploys.
Now change something in the app. Then run ...
Browser to the site in Azure. Notice that what is deployed does not contain your changes. It appears that the deploy command is not building if something already exists in the
dist/
folder.Expected behavior I expected that the deploy command would have always re-built the angular app first or never rebuild it. Options:
ng build --prod
I like 1 or 3.
Thoughts?