Build warnings under Angular 17

[russelg]

angular-froala-wysiwyg/froala v4.1.3.

I have been seeing this warning when building my angular projects that use Froala:

▲ [WARNING] This case clause will never be evaluated because it duplicates an earlier case clause [duplicate-case]

    angular:script/global:scripts.js:10:622815:
      10 │ ...tFileIcon("jpegIcon");case"image/jpeg":return k.icon.getFileIco...
         ╵                              ~~~~~~~~~~~~
  The earlier case clause is here:

    angular:script/global:scripts.js:10:622760:
      10 │ ...etFileIcon("gifIcon");case"image/jpeg":return k.icon.getFileIco...
         ╵                              ~~~~~~~~~~~~

The code in question it is complaining about comes from Froala (specifically the filesManager plugin):

Not sure if this report belongs in the angular repo, or the editor repo (https://github.com/froala/wysiwyg-editor).
However, this warning was not visible until we updated to angular 17 (and therefore esbuild as the builder).

[michael-koch787]

Any updates on this?

[Romilkajaria]

Any updates on this?

[superole]

@russelg I am very curious; -how did you find the code it is complaining about?
I am not using froala, but get a similar warning:

▲ [WARNING] This case clause will never be evaluated because it duplicates an earlier case clause [duplicate-case]

angular:script/global:scripts.js:2:1076775:
  2 │ ...2:return H1(G,2662,2671,!0,W);case 22:return Jf(G,1,10999,nd,3,W...
    ╵                                  ~~~~

The earlier case clause is here:

angular:script/global:scripts.js:2:1076739:
  2 │ ...1:return H1(G,2790,2799,!0,W);case 22:return H1(G,2662,2671,!0,W...
    ╵                                  ~~~~

...and I don't even know where to start looking.

[myhrcounsel]

I have the same error while trying to update an angular application to 19 and the latest Froala. I've taken froala out of the application and still get this error.

And as Superrole commented, I can't find any reference to that partial line of code.

[superole]

I finally found the "source" of my warning. By randomly searching through script files included in angular.json's "scripts":[].
I feel that it was "sheer dumb luck" though as Professor McGonagall would have put it ;)

I found it in a non public (company internal) dependency built with web-components.

I am sorry for the flooding of this thread with something clearly unrelated to froala, but it was the only relevant hit on google for this issue. And hopefully it will ease the frustration of others finding themselves fumbling in the dark on a similar bug-hunt.