Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

docs(guide): switch from ngmin to ng-annotate #8117

Closed
wants to merge 1 commit into from

Conversation

mgol
Copy link
Member

@mgol mgol commented Jul 9, 2014

Per last AWG meeting.

ng-annotate is an independent alternative to ngmin that is non-invasive
and more performant. For the background around the switch, see the discussion
at:
btford/ngmin#93

cc @IgorMinar @olov

ng-annotate is an independent alternative to ngmin that is non-invasive
and more performant. For the background around the switch, see the discussion
at:
btford/ngmin#93
@mary-poppins
Copy link

Thanks for the PR! Please check the items below to help us merge this faster. See the contributing docs for more information.

  • Uses the issue template (#8117)

If you need to make changes to your pull request, you can update the commit with git commit --amend.
Then, update the pull request with git push -f.

Thanks again for your help!

@IgorMinar
Copy link
Contributor

can you also add a note about the strict-di mode please? I think that only with the strict mode tools like ngmin and ng-annotate can be used reliably.

@mgol mgol closed this in 81cd836 Jul 10, 2014
olov added a commit to olov/ng-annotate that referenced this pull request Jul 10, 2014
@mgol
Copy link
Member Author

mgol commented Jul 11, 2014

@IgorMinar I see you've merged it without the strict-di mention; was that intended?

@mgol mgol deleted the ng-annotate branch July 11, 2014 09:47
ckknight pushed a commit to ckknight/angular.js that referenced this pull request Jul 16, 2014
ng-annotate is an independent alternative to ngmin that is non-invasive
and more performant. For the background around the switch, see the discussion
at:
btford/ngmin#93

Closes angular#8117
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants