-
-
Notifications
You must be signed in to change notification settings - Fork 170
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: async boundary option #1888
Conversation
refactor for easier management
…ors when replacing variables
…r using MFP (#1881) Co-authored-by: ScriptedAlchemy <zackary.l.jackson@gmail.com>
9f21375
to
77369ef
Compare
77369ef
to
b5c4c3b
Compare
@@ -553,6 +553,10 @@ export default { | |||
runtime: { | |||
$ref: '#/definitions/EntryRuntime', | |||
}, | |||
asyncBoundary: { |
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.
Should we update this option in "packages/enhanced/src/schemas/container/ModuleFederationPlugin.check.ts" ?
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.
ahh yes, i forgot to do the .ts file only did the schema file.
Stale pull request message |
Stale pull request message |
Description
add
asyncBoundary
option to federation plugin interfaceThis internally enables the automatic async boundary plugin, allowing it to be enabled without manually doing so.
Allows apps to be imported synchronously without getting eager error or call of undefined when not using a async import in the entrypoint.
Related Issue
N/A
Types of changes
Checklist