-
-
Notifications
You must be signed in to change notification settings - Fork 268
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
chore(enhanced): adjust add federation init process #2035
Conversation
Is this the same idea as my init pr? If so, I can work on this - there's a failing test case here when runtimeChunk: single in that case, I add a second ContainerEntry with {name + '_partial', runtime:false} If runtime is false, you do not want to addEntry again. |
yes this is similar to your init pr, this EntryPlugin is to add init federation runtime as a entry chunk in remoteEntry. |
# Conflicts: # packages/enhanced/package.json # pnpm-lock.yaml
# Conflicts: # packages/runtime/src/index.ts
# Conflicts: # packages/sdk/src/types/stats.ts
…iverse into chore/prefetch-type
… in runtime bootstrap (#2057) Co-authored-by: ScriptedAlchemy <zackaryjackson@bytedance.com> Co-authored-by: 2heal1 <TwoHeal@163.com> Co-authored-by: nyqykk <1327719263@qq.com>
# Conflicts: # packages/nextjs-mf/README.md
This reverts commit df3ef24
This reverts commit df3ef24
This reverts commit df3ef24
This reverts commit df3ef24
This reverts commit df3ef24
This reverts commit df3ef24
This reverts commit df3ef24
This reverts commit df3ef24
This reverts commit df3ef24
Description
change federation init to entryPlugin to make sure init at the beginning
Related Issue
Types of changes
Checklist