-
Notifications
You must be signed in to change notification settings - Fork 12k
No error reported when using buildOptimizer with aot set to false #11157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I think we're swallowing an error somewhere. Using the You should be able to use |
…and enabled build optimizer Fixes angular#11157
…and enabled build optimizer Fixes #11157
…and enabled build optimizer Fixes #11157
its working for me with ng b --prod --aot=false --build-optimizer=true |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug Report or Feature Request (mark with an
x
)Area
Versions
node --version is v10.1.0
npm --version is 5.6.0
Repro steps
I ran ng new testtheprob
I entered the repo.
run ng build --prod --aot=false and notice that no dist folder is created
I then tried modifying the angular.json so that the prod build had aot:false
I ran ng build --prod and no dist folder was created
The log given by the failure
Nothing is printed to the console. The command just stops without building a dist folder. Also I tried running --verbose=true to see if that added details but it did not
Desired functionality
I need to be able to do a prod build without aot. Neither editing the angular.json file nor using the command line args works.
We have multiple servers that we are testing our code on, our app is so big that running an aot build takes several minutes, this won't work for us on some of our servers that we are deploying to many times per day. In angular 5 we were able to turn off aot, but are no longer able too with angular 6.
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: