Skip to content

Conversation

@CGNonofr
Copy link
Contributor

@CGNonofr CGNonofr commented Feb 11, 2025

If the extension host iframe is hosted on another domain, it refuses messages from the main thread because the domain does not match. VSCode handle this by adding a parentOrigin parameter but in our case it wasn't used

Also, force set the domain of the extension host worker, it was the case before a previous refactor and is a regression, forcing us to set the webpack publicPath for it to work, or provide a iframeAlternateDomain by hands

@CGNonofr CGNonofr requested a review from kaisalmen February 11, 2025 19:09
@CGNonofr
Copy link
Contributor Author

@kaisalmen I'm trying to update the lib in our apps which all use the last version of webpack, and I'm surprised to encounter so many issues that nobody had before 🤔

Copy link
Collaborator

@kaisalmen kaisalmen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@kaisalmen
Copy link
Collaborator

and I'm surprised to encounter so many issues that nobody had before 🤔

Webpack changed to better or worse or nobody looked closely enough. I don't use webpack if I don't have to, so the checks in mlc are limited to basic bundling checks.

@CGNonofr CGNonofr merged commit 4d042d7 into main Feb 11, 2025
2 checks passed
@CGNonofr CGNonofr deleted the fix-extension-host-worker-cdn branch February 11, 2025 20:25
@github-actions
Copy link

🎉 This PR is included in version 14.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants