version 2.0.0 breaks ng Angular 8 -> webpack in my project about raw-loader

[alexander-akait]

Shortly: some of angular loader(s) is not compatibility with latest raw-loader (we use esm instead commonjs)

#77

[alexander-akait]

Can be fixed like:

function assertArrayOfStrings(identifier, value) {
            value = value && value.default ? value.default : value
            if (value == null) {
                return;
            }
            if (!Array.isArray(value)) {
                throw new Error("Expected '" + identifier + "' to be an array of strings.");
            }
            for (var i = 0; i < value.length; i += 1) {
                if (typeof value[i] !== 'string') {
                    throw new Error("Expected '" + identifier + "' to be an array of strings.");
                }
            }
        }
        

[thw0rted]

There is an issue open with angular2-template-loader, which I was using for my dev build. That project hasn't seen an update in over 2 years, so for now I'm switching from raw-loader to html-loader for component CSS includes, and it Just Works. It also has the advantage of using a single config for both dev and prod builds.

[ViieeS]

[email protected] is better though, simple plug and play solution.

[thw0rted]

I'd rather keep a live dependency on the "wrong" loader than a pinned dep on the "right" one, personally. If you stick with 1.0 to avoid this bug then you're going to miss out on updates that could possibly be security-relevant.