-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Bundle the web workers #7700
Comments
@evenstensberg any interest in taking this on? |
Yep, this would be cool to implement! @ozyx I've sent you an invite to the webpack internal slack. If you have any problems/feedback about webpack, you can give that there. |
Can i take this |
@hussainu6 sure 👍🏽 |
Hi @hussainu6 , thanks for your interest! We're currently addressing this issue as part of our ongoing sprint, so we're not seeking additional contributions on it at the moment. However, I encourage you to check out our help wanted issues for other areas where your contributions would be greatly appreciated. Also, please ensure you have submitted a Contributor License Agreement (CLA) if you haven't done so already. We require this before we can merge any contributions you make. |
@ozyx How do you plan to initiate the workers and where? |
I guess we can declare the workers in the global scope in openmct.js Edit: We can import the workers where they are initiated, instead of a public url to the workers after bundled, we can import them directly using import.meta |
Summary
On build, Open MCT creates its bundle
openmct.js
along with a bunch of other files, many of which are WebWorkers that are conditionally instantiated by different plugins:We should bundle these into
openmct.js
using webpack.entry
points for each web/shared worker in webpack configThe text was updated successfully, but these errors were encountered: