-
Notifications
You must be signed in to change notification settings - Fork 12k
Lots of Copyright comment blocks in main.js build #2386
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
@hansl can you have a look? This must be part of the total bundle size. |
I need to talk to the legal team about this. The google ones are probably okay to only put one, but third party libraries might be more complicated. |
Just FYI I made a new beta16 project and ran the main bundle through a comment stripper, and non-gzipped size went from 815kb to 764kb. |
Speaking of comments. I'm using material-design-lite and building it from scss. My styles.bundle.js with --prod contains 31 occurrences of every single /* */ comment (not // comments) in _variables.scss as it's included 31 times. Perhaps I should create a separate issue for this tho? |
CSS comments has been solved in #2593. |
I see the comments with builds using ngCLI beta.17 as well. Can we strip the credits into a credits.txt file that refers to the compiled .js/.css? MIT doesn't require the presence of the copyright notice in binary distributions. Can a *.js file be considered a binary distribution? |
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. |
Version: beta.16
OS: OSX 10.12
So I just ran an
ng build -prod --aot
using beta.16 and was looking at the output. I noticed main.js has about 20 - 30 instances of Google Copyright notice (one above each block). The same happens for a build without AoT as well actually.I'm guessing there should only really be one or none of those at the top of the generated dist/main.js
Screenshot: https://www.dropbox.com/s/4cuf1yxtik9drjy/Screenshot%202016-09-28%2010.50.09.png?dl=0
The text was updated successfully, but these errors were encountered: