Module Federation Share should support layers/issuerLayer
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 65.9k
- Forks
- 9.5k
- Avg merge
- 10h 40m
- Merged PRs (30d)
- 296
Description
Feature request
Loader layers currently have no convention for support when using something like issueLayer, for example with RSC
What is the expected behavior?
There should be a convention to specify or auto assign the layers used when creating the shares
What is motivation or use case for adding/changing the behavior?
RSC support likely will need loader layers or layers to work
How should this be implemented in your opinion?
Unsure but i think it needs to be cone at ConsumeShared and ProvideShared, either in the hooks or in the Module classes of these - but i do not know
Are you willing to work on this yourself?
yes
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Module Federation sharing through ConsumeShared and ProvideShared, including the hooks and Module classes named in the issue. Determine a convention for specifying or auto-assigning loader layers when shares are created, then verify that the behavior supports the RSC use case described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100