-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
👍 |
1 similar comment
👍 |
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:
No Issue:
|
👍 Seeing this as well. |
…ngmin#89, btford/ngmin#87, btford/ngmin#85, btford/ngmin#78, btford/ngmin#77, btford/ngmin#73, btford/ngmin#70, btford/ngmin#64, btford/ngmin#63, btford/ngmin#61, btford/ngmin#59, btford/ngmin#57, btford/ngmin#56, btford/ngmin#54, btford/ngmin#50, btford/ngmin#46, btford/ngmin#43, btford/ngmin#42, btford/ngmin#37, btford/ngmin#35, btford/ngmin#22
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. |
It does not minify-safeguard ("module").run(function(inject) {});
The text was updated successfully, but these errors were encountered: