Skip to content
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

Support for Run #46

Closed
Goffen opened this issue Aug 30, 2013 · 5 comments
Closed

Support for Run #46

Goffen opened this issue Aug 30, 2013 · 5 comments

Comments

@Goffen
Copy link

Goffen commented Aug 30, 2013

It does not minify-safeguard ("module").run(function(inject) {});

@oltodo
Copy link

oltodo commented Sep 18, 2013

👍

1 similar comment
@raine
Copy link

raine commented Dec 19, 2013

👍

@majgis
Copy link

majgis commented Jan 7, 2014

We are experiencing this issue. We found that if run is the only method call or by moving run to the top as the first method call, there is no issue. When run follows another method call, then this issue is present.

Issue:

  • angular.module(...).config(...).run(...)

No Issue:

  • angular.module(...).run(...)
  • angular.module(...).run(...).config(...)

@mrwillis21
Copy link

👍 Seeing this as well.

@eddiemonge
Copy link
Collaborator

Please try https://github.com/olov/ng-annotate. ngmin is now deprecated: #93

If your issue isn't resolved there please open an issue at https://github.com/olov/ng-annotate/issues

If you really want ngmin to fix this issue, feel free to fork it and use that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants