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.

Sign up for GitHub

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

Jump to bottom

Angular performance in production #15

Open

pdonorio opened this issue May 6, 2016 · 3 comments

Owner

pdonorio commented May 6, 2016 •

edited

Loading

We must pay attentions to details.

An example:
https://medium.com/swlh/improving-angular-performance-with-1-line-of-code-a1fb814a6476#.60xbcmm2y (better explained here)

Owner Author

pdonorio commented May 31, 2016 •

edited

Loading

Official docs say:
https://docs.angularjs.org/guide/production

Owner Author

pdonorio commented Jun 26, 2016

Also more tips here:
http://www.gros-engineering.com/angularjs-performance-tweaks

Owner Author

pdonorio commented Aug 2, 2016 •

edited

Loading

@mdantonio we may already convert to the first post in "Disabling Debug Data".
That is used from tests and the chrome batarang which we do not use...

We just need:

angular.module('web')
    .config(['$compileProvider', function ($compileProvider) {
      $compileProvider.debugInfoEnabled(false);
    }]);

in common.run.js?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment