-
Notifications
You must be signed in to change notification settings - Fork 12k
Production build broken since RC6 upgrade. #2007
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
Comments
Same here |
Same here. However i noticed that |
@hassanasad its strange that --env=prod doesn't create production build :). ng build --target=production --environment=prod ng build createst the same build, so I am not sure if --env=prod is a valid flag or there is some issue with cli. |
I believe this was an issue with webpack that has been resolved. This should be fixed with the next update. |
You're misinterpretting two concepts: I'm looking at this. Never seen it before. Is it an open source projet I could repro with? |
@hansl I have upgraded it to RC7, but I think you should be able to replicate this issue from one of my repo. Above error was from the same repo. |
There's something wrong with your global / local versions of Angular CLI. I got it working locally the first try; literally just |
Actually nevermind, just found the error when running prod. Investigating. |
Okay found the bug. This is already fixed by #1937. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
production build is erroring because of an undefined script
When running ng build --prod, it ended up in following error:
Upgraded to Angular 2 RC6 with following environment details:
angular-cli: 1.0.0-beta.11-webpack.8
node: 6.3.1
os: win32 x64
The text was updated successfully, but these errors were encountered: