Subresource Integrity support for Module Federation#220
Subresource Integrity support for Module Federation#220sowtame wants to merge 10 commits intowaysact:mainfrom
Conversation
|
guys, please look |
|
@sowtame thanks for your contribution and for your patience, I've been distracted in recent weeks. I'm going to take a look at this next week. |
|
@jscheid thanks, I've changed the implementation a lot, I'm using a more reliable way of finding modules using chunkGraph |
There was a problem hiding this comment.
There's another scenario that needs to be filtered.
When using async import for a remote module, such as:
const B2View = defineAsyncComponent(() => import("mfRemoteModule/Example.vue"))
It also throws the error: Asset js/207.13044ce8.js contains unresolved integrity placeholders.
We need to find a new way to filter it.
hi, can you give a repository where you can reproduce the problem? |
|
Hi there! |
|
any progress? |
|
@jscheid friendly ping |
@sowtame if you add this to the host bootstrap code you'd see // mock dependency
import("lodash");
import("app1")
.then((module) => {
console.log(module);
})
.catch((e) => console.error(e));
console.log("ok"); |
|
So there are 2 issues. But I kept getting this: I think It's because I added And it compiles. But I'm new to webpack internals so not sure if those are legit |
|
bump |
|
I download the @sowtame/webpack-subresource-integrity but still while bundling the files, i get this error message which the line is script.integrity = webpack_require.sriHashes[chunkId]; We use micro fe. |
|
Hello everyone! |
Hi, I'm adding support for the webpack federation module.
The main problem was that the wmf plugin creates mock chunks that are not used in production. It can be detected finding shared files by