-
Notifications
You must be signed in to change notification settings - Fork 12k
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
fix(@ngtools/webpack): prevent emitting sourcemaps #4221
Conversation
@hansl can you review? |
e2fd262
to
d0ed70f
Compare
// If it wasn't there - delete it. | ||
delete this._parentCompilation.assets[outputName]; | ||
} | ||
Object.keys(childCompilation.assets).forEach((filename) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit: filename
should be fileName
, as it is two words.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
Requested change in angular#4221
In some cases compilation of a component style generates a sourcemap and it's not deleted from assets. This would be cause hangup in Windows.
00e7ee5
to
3c41bcd
Compare
In some cases compilation of a component style generates a sourcemap and it's not deleted from assets. This would be cause hangup in Windows.
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. |
In some cases compilation of a component style generates a sourcemap and it's not deleted from assets.
This would cause hangs in Windows and make unnecessary outputs in other platform.
may fix #3019