feat(mf): report concrete shared provider metadata - #15687
Draft
ScriptedAlchemy wants to merge 1 commit into
Draft
ScriptedAlchemy wants to merge 1 commit into
ScriptedAlchemy wants to merge 1 commit into
Conversation
This was referenced Sep 15, 2026
Deploying rspack with
|
| Latest commit: |
dda1f5f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://7fee2fd0.rspack-v2.pages.dev |
| Branch Preview URL: | https://codex-mf-provider-metadata-d.rspack-v2.pages.dev |
Contributor
📦 Binary Size-limit
❌ Size increased by 24.00KB from 68.82MB to 68.84MB (⬆️0.03%) |
Contributor
Rsdoctor Bundle Diff AnalysisFound 5 projects in monorepo, 0 projects with changes. 📊 Quick Summary
Generated by Rsdoctor GitHub Action |
Contributor
Merging this PR will not alter performance
Comparing Footnotes
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Propose the native Rspack implementation for RFC #5082.
A build can provide two implementations under one shared key. The current manifest has one summary version and a combined asset list, so a reader cannot associate each version with its files.
Changes
Add optional
shared[].providersrecords tomf-stats.jsonandmf-manifest.json. Each record contains a version, a resolved import relative to the build context, and its assets.For example, two implementations of
reactcan report these pairs:18.3.1./react18.jsreact18.js19.0.0./react19.jsreact19.jsExisting shared fields remain unchanged. The array is omitted for zero or one provider and when asset analysis is disabled. Runtime registration and version selection do not change.
This is an independent draft based on
main, outside the layers stack. It keeps main's existing name-based grouping. Scope/layer reconciliation, provider-specific fallback metadata, and cross-bundler parity remain open in the RFC. The core prototype is #5083.StatsSharedProviderderivesClonebecause existing shared stats and manifest records are cloneable. Cloning copies the owned version, import, and asset paths.Verification
providers.The complete earlier prototype, including layer-aware grouping and fallback enrichment, remains preserved at f0a9c614.