-
Notifications
You must be signed in to change notification settings - Fork 12k
prod build/serve fails with angular2-material #940
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
Can confirm, I'm experiencing this in my project as well. There appear to be a handful of open issues currently that all describe similar problems with production builds. |
Ive been digging around the build task but I can't figure out whats wrong. especially since it isn't happening with all 3rd party libs |
I'm having this problem too. Note this line from log:
See how that's referencing @jelbourn's path? There are sourceMappingURLs all over material2 that reference that path. Could that be tripping things up? Edit: See: angular/components#541 Stripping out the incorrect sourcemap refs will temporarily fix. Quick cmds to do so: Linux:
FreeBSD/OSX:
|
I didn't notice that! Ill confirm and then close this issue |
@benjaminkitt I have confirmed that this is the issue. (I couldn't get your script to work though). Since this does indeed seem to be an issue with angular2-material and not with angular-cli I am closing this issue |
@benjaminkitt : thanks !! It fixed the issue |
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. |
Mac OSX El Capitan
angular-cli: 1.0.0-beta.5
node: 4.4.5
os: darwin x64
angular-cli-build.js:
src/system-config.ts
src/app/test-app.component.ts
Other 3rd party libs like moment are working fine. I am not sure why this would only be happening with angular2-material. running things in dev mode works fine (ng server and ng build). It is happening with any and all angular2 material components. the components themselves seem to be working just fine.
The text was updated successfully, but these errors were encountered: