You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Beta 1 breaking on production build, but working in development. #7
Hey, I'm running into an issue since upgrading to beta 1 where it will run fine but give errors like this when doing a production build...
No provider for t! (t -> t)
I've also seen undefined errors after with another app copy...any ideas as to what may be causing this? It runs fine in beta 0 and fine in beta 1 on watch, but not build.
Hey, yes, I see most of the issues I'm experiencing are beta 1 issues, not just webpack issues. I even ran into this issue that goes beyond being minified where there's an error if try to set class attributes even without being minified: angular/angular#6374
I guess I'll stick with beta 0 until some of the obvious bugs are patched. Thanks.
Activity
ocombe commentedon Jan 10, 2016
You're right, I'll look into it, thanks a lot for the report.
edit: it looks like it's an error with UglifyJS, without it everything works fine, you can disable to plugin until I find the fix.
ocombe commentedon Jan 10, 2016
It looks like there's a lot of error with minified builds in beta.1:
angular/angular#6366
angular/angular#6380
I disabled "mangle" for the uglify js plugin until they fix the beta :-/
I'll let the issue opened until then.
qdouble commentedon Jan 10, 2016
Hey, yes, I see most of the issues I'm experiencing are beta 1 issues, not just webpack issues. I even ran into this issue that goes beyond being minified where there's an error if try to set class attributes even without being minified: angular/angular#6374
I guess I'll stick with beta 0 until some of the obvious bugs are patched. Thanks.
ocombe commentedon Jan 16, 2016
It will be fixed once this PR has been merged
ocombe commentedon Jan 20, 2016
This has been fixed with angular/angular@eda4c3e
We just need a new beta now.
ocombe commentedon Jan 28, 2016
This has been fixed in beta.2 !