-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
feat(plugins): add primitives to support sub-compiler usage #1887
Conversation
|
Thanks for the PR. We'll support compiling dynamically added inputs in Farm v2.0, it can solve the issue you mentioned, sharing thread pool and module graph. |
CodSpeed Performance ReportMerging #1887 will create unknown performance changesComparing Summary
|
There are CI errors @ssttevee , we'll merge and publish it as soon as possible when all tests passed |
Oh sorry, I didn't catch those before. It should be fixed now. |
Description:
I'm building framework around farm that requires "sub-build"s. The main problem blocking me from achieving this is the inability to access the plugins from the current compiler context/plugin driver.
With these changes, I am able to create a sub-compiler to create a sub-build like this:
Note that there are a few issues with this approach:
BREAKING CHANGE:
None.
Related issue (if exists):