-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subresource Integrity support for Module Federation #220
base: main
Are you sure you want to change the base?
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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. |
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