You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -59,13 +60,8 @@ The loader does support scripts modules, files with the `.mjs` extension.
59
60
However, due to the limitations imposed on those files in regard to the MIME, we added a support to those files ending with `.module.js`.
60
61
This permits us to load those files as script modules too even if we do not have control over the server configuration.
61
62
62
-
Moreover, if your file ends with `.module.js` or `.mjs`, the loader will not try to build the asset `handle` from the file name.
63
-
Instead, it will use the `key` from the manifest file as the **handle**.
64
-
The reason is that there might be conventions regarding the handle naming, which might not be compatible with the `WebpackManifestLoader::parseData` logic.
65
-
66
-
Imagine that `$handle` is `@vendor/lib-name`, then `pathinfo($handle, PATHINFO_FILENAME)` will return `lib-name`.
67
-
68
-
This is because `pathinfo` treats the last part after a slash as the filename, so it extracts `lib-name` from `@vendor/lib-name`.
63
+
Moreover, if your file ends with `.module.js` or `.mjs`, the loader will automatically resolve these files as a `Inpsyde/Assets/ScriptModule`.
64
+
Additionally, we support `@vendor/` in the handle name when parsing from `manifest.json`. Before, the `@vendor/` was detected as part of the filepath and being stripped away.
0 commit comments