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] Error bundling using SystemJS Builder in Beta.1 #6366
Hi, I just updated my starter project to angular2.0.0@beta.1 and when running in development, it was okay, but when I run production build and serve it, it showed error as follows: It's not happening in angular2.0.0@beta.0
you can reproduce it by cloning my repo using repro-mangle-error branch, then run gulp serve-build
Finally getting it to work, I had to set mangle: false in SystemJS Builder options. But then the boot.js size becomes ~957 KB, which in beta.0 (that works without mangle) size ~650 KB...
Looks like there's a bug in the viewFactory, this didn't happen in beta.0 (dev & build), and only didn't happen in beta.1 when dev, but broken when build (with mangle: true).
Activity
antonybudianto commentedon Jan 9, 2016
Finally getting it to work, I had to set

mangle: falsein SystemJS Builder options. But then theboot.jssize becomes~957 KB, which in beta.0 (that works without mangle) size~650 KB...[-]Error bundling in Beta.1[/-][+]Error bundling using SystemJS Builder in Beta.1[/+][-]Error bundling using SystemJS Builder in Beta.1[/-][+][beta.1] Error bundling using SystemJS Builder in Beta.1[/+]antonybudianto commentedon Jan 10, 2016
Found something interesting here

Looks like there's a bug in the viewFactory, this didn't happen in beta.0 (dev & build), and only didn't happen in beta.1 when dev, but broken when build (with
mangle: true).pkozlowski-opensource commentedon Jan 18, 2016
Duplicate of #6380
antonybudianto commentedon Jan 18, 2016
but the 2nd picture is no duplicate issue I think
angular-automatic-lock-bot commentedon Sep 7, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.