Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/angular/angular-cli/issues/24617 below:

Angular should *not* disable Webpack's import.meta.url parsing (for WebAssembly files, at least) · Issue #24617 · angular/angular-cli · GitHub

build

• Yes, this behavior used to work in the previous version

No response

Actually, Angular should just make up its h*cking mind (see #24616).

Currently, its mysterious and ephemeral built-in webpack configuration disables module.parser.javascript.url, so assets imported with new URL(..., import.meta.url) do not get packaged by default.

Okay, that's fine, if you're into that kind of thing, but at the same time it keeps module.parser.java.importmeta enabled, leading webpack to output entirely useless file:// URLs instead of doing any packaging.

End result is that you just can't use any ES6 module (such as anything compiled with Emscripten's EXPORT_ES6 option) that tries to load some possibly really important asset, like, say, a WebAssembly file. You are damned if you do and damned if you don't! If you do what is suggested in #22351 and try to use the assets option, the actually generated code will not reference this asset because import.meta.url got rewritten to some path on your build filesystem.

But if you then disable module.parser.java.importmeta manually in a custom webpack config, then you end up with import.meta.url in the output code, which utterly breaks testing with karma (since karma does not do ES6 modules, because that's like not groovy, man) and of course also any possibility of targeting a non-ES6-aware browser.

This is the opposite of webpack's perfectly good and sane defaults. A reasonable workaround is to create a custom webpack config which enables module.parser.java.url, like this:

module.exports = {
  module: {
    parser: {
      javascript: {
        url: true,
      },
    },
  },
};

From an Angular app, try to load an ES6 module (like https://www.npmjs.com/package/soundswallower?activeTab=explore) that has an accompanying WASM file, or any kind of asset that is loaded with new URL(..., import.meta.url). The relevant code output by Emscripten is:

 wasmBinaryFile = new URL("soundswallower.web.wasm", import.meta.url).href;

No response

Angular CLI: 15.1.2
Node: 18.12.1
Package Manager: npm 9.1.3
OS: linux x64

Angular: 15.1.1
... animations, cdk, common, compiler, compiler-cli, core, forms
... localize, material, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1501.2
@angular-devkit/build-angular   15.1.2
@angular-devkit/core            15.1.2
@angular-devkit/schematics      15.1.2
@angular/cli                    15.1.2
@schematics/angular             15.1.2
rxjs                            7.5.7
typescript                      4.8.4
webpack                         5.75.0

No response

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4