-
Notifications
You must be signed in to change notification settings - Fork 12k
Building Angular 10 app shows incomplete "Warning in" messages #18231
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
This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please or share the project even privately? You can read here why this is needed. A good way to make a minimal repro is to create a new app via |
I've seen this too with version 10.0.2 and I tried to track it down. |
@rurku, that’s really good info. |
Hi @alan-agius4 , the empty
May I know if the fix is published or if there's something that I have missed. |
The fix will be published later on this week in the next patch version. |
Was the fix released? |
Yeah, it’s available in 10.0.3 |
Hello @alan-agius4 |
@UrbanNuke, can you provide the output of |
@alan-agius4 of course, here
|
@UrbanNuke, you do have the correct packages, would you be able to share a reproduction even privately? |
Same here, still getting the "warning in" message after updating to 10.0.3
|
`chunk {0} runtime-es2015.409e6590615fb48d139f.js (runtime) 1.45 kB [entry] [rendered] WARNING in WARNING in ` |
@alan-agius4 unfortunately I can't provide reproduction because our security politics.
|
@UrbanNuke, can you try to create a minimal reproduction using It would be super helpful to quickly identify and solve the problem. |
Alternatively what would be helpful is modify |
@alan-agius4 |
@UrbanNuke, thanks for the info and reproduction. Will take a look sometime between today and Monday. |
@alan-agius4 After adding the console above with the updated packages:
When I ran the app, this is the result of the log:
On
we can try to have it like this:
With that, the empty warnings are now gone: |
The problem there is that we except an array of strings.
I know what’s happening 😊, it’s an easy fix. Thank you everyone for all
the information provided.
…On Fri, 17 Jul 2020 at 14:46, Kristy Mae Almuete ***@***.***> wrote:
Alternatively what would be helpful is modify
***@***.***/build-angular/src/angular-cli-files/utilities/stats.js
line 84 and add console.log({warnings}); and provide the outputted values.
After adding the console above with the updated packages:
***@***.***/build-angular": "^0.1000.3",
***@***.***/cli": "^10.0.3",
When I ran the app, the result of the logs is this:
{
warnings: [
'Conflict: Multiple assets emit different content to the same filename 3rdpartylicenses.txt',
'Conflict: Multiple assets emit different content to the same filename 3rdpartylicenses.txt',
'Conflict: Multiple assets emit different content to the same filename 3rdpartylicenses.txt',
'Conflict: Multiple assets emit different content to the same filename 3rdpartylicenses.txt',
'Conflict: Multiple assets emit different content to the same filename 3rdpartylicenses.txt',
'Conflict: Multiple assets emit different content to the same filename 3rdpartylicenses.txt',
[],
[],
[],
[],
[],
[],
[],
[],
[],
[]
]
}
On stats.js line 85 maybe instead of this:
return rs('\n' + warnings
.filter(m => !!m)
we can have it this:
return rs('\n' + warnings
.filter(m => m.length)
With that, the empty warnings are now gone:
[image: image]
<https://user-images.githubusercontent.com/7908747/87787548-67b38f00-c86e-11ea-8bb8-4f00902716d7.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#18231 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEF74WSELBIBYRNBBYBEZ7DR4BBZZANCNFSM4OXRKYZA>
.
|
@alan-agius4 thanks for very fast fix 😊 |
Couldn’t have been possible without the info that all of you provided. So thank you all as well 😊 |
Have tested it and All is now well when I updated my packages with:
and run |
Thanks for the confirmation @KShewengger. |
updated to Angular: 10.0.5 and empty warnings now gone. Thanks for the fix. |
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. |
🐞 Bug report
Is this a regression?
Yes
Description
Whenever I tried to build my app, there are warning in relevance to "Fix CommonJS or AMD dependencies can cause optimization bailouts" and incomplete "Warning in" message but the first one is now resolved through editing the
angular.json
and add this line right here:But the 2nd issue - incomplete "Warning in" messages still persists. With this, would like to be guided.
🔬 Minimal Reproduction
It is through when running
ng build --prod
but since the warning shown is incomplete, I'm quite not sure when does it persist but these are the list of packages that I have added underallowedCommonJsDependencies
🔥 Exception or Error
🌍 Your Environment
Angular CLI: 10.0.2
Node: 12.11.1
OS: macOS Catalina
Angular: 10.0.3
The text was updated successfully, but these errors were encountered: