Invalid resource URL

[janousek]

🐞 Bug report

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• extract-i18n
• run
• config
• help
• version
• doc

Is this a regression?

Yes.

Description

Resource URL generated by WebpackResourceLoader is invalid. It is caused by this line:

angular-cli/packages/ngtools/webpack/src/resource_loader.ts

Line 110 in 638344a

const entry = data ? `angular-resource:${resourceType},${hash}` : filePath;

It should looks like this:

const entry = data ? `angular-resource://${resourceType},${hash}` : filePath; 

This is regression caused by this change:
8e741e1#diff-8f746eb1f9444d4c0e52eea0175d6a080fd8f7c38b8c8056e5abba89de3337c4

For me, this bug currently causes this error during i18n extraction:

angular-resource:style,13704965354860b52a891d7d35de9bb3:1:0 - Error: Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

[clydin]

That's a valid URI. A data URI, for instance, is of the form data:[<mediatype>][;base64],<data> (no slashes).

The error there is caused by the content failing to parse.

[janousek]

@clydin If this is correct URI, then the bug is here:

angular-cli/packages/angular_devkit/build_angular/src/extract-i18n/index.ts

Line 243 in 638344a

/^angular-resource:\/\//,

Because it requires slashes.

[clydin]

Yes. that should be corrected. However, that would only affect i18n extraction and not a build.

[clydin]

As a temporary workaround, you can use 12.0.0 to extract and then re-upgrade to the latest until the next patch release.

[alan-agius4]

Closed via #20971

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}