fix(@angular/build): resolve only ".wasm" files

[ms-dosx86]

PR Checklist

Please check to confirm your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/angular/angular-cli/blob/main/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Currently the wasm plugin introduced in v18.1.0 resolves not only .wasm imports, but any imports that end with (any character)wasm. It must be a typo in the wasm plugin regex /.wasm$/ which should look like /\.wasm$/.

You can see it in this example by running ng build.
In the example above matrix-js-sdk depends on @matrix-org/matrix-sdk-crypto-wasm which is treated as a wasm import by the plugin which causes build error

The plugin "angular-compiler" didn't set a resolve directory for the file "angular:wasm:init:/home/projects/stackblitz-starters-nnuphq/node_modules/@matrix-org/matrix-sdk-crypto-wasm/pkg/index.js", so esbuild did not search for "./matrix_sdk_crypto_wasm_bg.wasm.js" on the file system.

What is the new behavior?

Wasm plugin resolves only .wasm imports.

Does this PR introduce a breaking change?

• Yes
• No

Other information

[alan-agius4]

LGTM, thanks

[dgp1130]

The changes were merged into the following branches: main, 18.1.x

[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.}