Fix: Inline layout worker - #114
Merged
Merged
Conversation
tonilastre
approved these changes
Aug 12, 2026
tonilastre
left a comment
tonilastre
left a comment
Contributor
There was a problem hiding this comment.
Looks good! Great catch for removing min.js scripts from docs too.
|
🎉 This PR is included in version 1.0.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The layout Web Worker was loaded via
new Worker(new URL('./simulator.worker', import.meta.url)), which esbuild-based bundlers don't resolve, the worker never started and layout silently fell back to the main thread.It's now bundled into a self-contained blob at build time and started from a Blob URL, so it works under any bundler (esbuild/Vite/rollup/webpack), with no bundler, and in Electron file:// - no consumer config. If the worker can't start, it transparently falls back to the main-thread simulator with a one-time warning.
No public API changes.