feat: merge increment B - documentation and changesets

- Add changesets for enhanced layer support features
- Update advanced sharing documentation with nodeModulesReconstructedLookup
- Update experiments documentation with filter options
- Update Vite guide with latest federation features
- Document new sharing capabilities and configuration options

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <[email protected]>

Author: ScriptedAlchemy

.changeset/ai-eager-wolf.md

@@ -0,0 +1,12 @@
+---
+"@module-federation/runtime-core": minor
+---
+
+Added support for OR ranges in semantic version satisfaction logic with comprehensive unit tests.
+
+- Implemented parsing for OR (||) conditions in version ranges.
+  - Split input ranges by || to evaluate alternatives individually.
+  - Ensured logical handling of wildcards '*' and 'x' within ranges.
+- Refactored internal parsing to support more complex range constructs.
+- Added comprehensive test cases to cover diverse scenarios for OR range support.
+- Introduced error handling during range processing, with console logging for tracking issues.

.changeset/ai-happy-fox.md

@@ -0,0 +1,12 @@
+---
+"@module-federation/nextjs-mf": minor
+---
+
+Refactor and enhance module federation support for Next.js.
+
+- Introduced `getShareScope` function to dynamically generate the default share scope based on the client or server environment, replacing static DEFAULT_SHARE_SCOPE declarations.
+- Implemented `RscManifestInterceptPlugin` to intercept and modify client reference manifests, ensuring proper prefix handling.
+- Refined server-side externals handling to ensure shared federation modules are bundled.
+- Simplified and modularized sharing logic by creating distinct functions for React, React DOM, React JSX Runtime, and React JSX Dev Runtime package configurations.
+- Captured the original webpack public path for potential use in plugins and adjustments.
+- Enhanced logging for debug tracing of shared module resolution processes in runtimePlugin.

.changeset/ai-hungry-bear.md

@@ -0,0 +1,10 @@
+---
+"@module-federation/enhanced": minor
+---
+
+Enhancements to layer handling in module federation tests and configuration.
+
+- Improved handling of `shareKey` for layers within `ConsumeSharedPlugin` and `ProvideSharedPlugin`.
+  - Conditionally prepend the `shareKey` with the `layer` if applicable.
+- Introduced new layer configurations to support more nuanced federation scenarios that consider multiple layers of dependency.
+

.changeset/ai-sleepy-fox.md

@@ -0,0 +1,9 @@
+---
+"@module-federation/enhanced": patch
+---
+
+Refactored module sharing configuration handling.
+
+- Simplified plugin schema for better maintainability
+- Improved layer-based module sharing test coverage
+- Removed redundant plugin exports

.changeset/ai-sleepy-tiger.md

@@ -0,0 +1,5 @@
+---
+"@module-federation/runtime": minor
+---
+
+- Added a new property 'layer' of type string or null to SharedConfig.

.changeset/brown-badgers-fetch.md

@@ -0,0 +1,5 @@
+---
+'@module-federation/enhanced': minor
+---
+
+support request option on ConsumeSharePlugin. Allows matching requests like the object key of shared does

.changeset/shy-snails-battle.md

@@ -0,0 +1,5 @@
+---
+'@module-federation/enhanced': minor
+---
+
+Layer support for Provide Share Plugin

apps/website-new/docs/en/configure/advanced-sharing.mdx

@@ -26,6 +26,7 @@ interface SharedConfig {
   issuerLayer?: string;          // Restrict config to apply only when the consuming module (issuer) is in this layer.
   include?: IncludeExcludeOptions; // Rules to include specific modules/versions
   exclude?: IncludeExcludeOptions; // Rules to exclude specific modules/versions
+  nodeModulesReconstructedLookup?: boolean; // Enable enhanced matching for relative imports for this shared item
 }
 
 interface IncludeExcludeOptions {
@@ -83,6 +84,24 @@ new ModuleFederationPlugin({
 });
 ```
 
+## How Share Matching Works
+
+:::note
+Module Federation matches shared modules in a specific order. This applies to both providing and consuming shared modules, and is essential for advanced sharing scenarios.
+:::
+
+**Matching order:**
+
+1. **Direct match:** Exact match for the requested module name (e.g., `'react'`).
+2. **Prefix match:** If no direct match, check for prefix-based shares (e.g., `'next/'` for `'next/router'`).
+3. **Reconstructed path match:** If enabled, try matching the path after `node_modules` (for relative/absolute imports inside node_modules), first direct, then prefix.
+4. **No match:** Falls back to normal module resolution.
+
+- Matching stops at the first match found.
+- `include`/`exclude`, `layer`, and `issuerLayer` filters apply at each step.
+
+See `ProvideSharedPlugin.ts` and `ConsumeSharedPlugin.ts` for implementation details.
+
 ## Layers
 
 ### `layer`
@@ -348,53 +367,9 @@ In this Next.js-style example:
 
 ## nodeModulesReconstructedLookup
 
-This section covers the nodeModulesReconstructedLookup experiment, which helps with sharing modules that use relative imports internally.
-
-Module Federation offers an experimental feature `nodeModulesReconstructedLookup` to solve a common issue with sharing modules that use relative imports internally.
-
-### The Problem
+`nodeModulesReconstructedLookup` is now a per-shared-item option in the `shared` configuration. It enables enhanced matching for relative imports inside node_modules for the specific shared item where it is set.
 
-When you share a module like `'shared'` and its subpaths like `'shared/directory/'`, Module Federation matches the **import request** against these patterns. However, if your module uses **relative imports** internally, Module Federation can't match them properly:
-
-```js
-// shared/index.js
-export * from './package.json';
-export { default as thing } from './directory/thing'; // This relative import won't match 'shared/directory/'
-```
-
-The problem occurs because:
-1. You configure Module Federation to share `'shared'` and `'shared/directory/'`
-2. When code imports `'shared'`, it works fine
-3. But inside `shared/index.js`, there's a relative import `import './directory/thing'`
-4. Module Federation doesn't recognize this as matching `'shared/directory/'` because the import request is `'./directory/thing'` (relative)
-
-### The Solution
-
-The `nodeModulesReconstructedLookup` experiment solves this by:
-1. Detecting relative imports inside shared modules
-2. Reconstructing the full path (e.g., `'node_modules/shared/directory/thing'`)
-3. Extracting the module name after node_modules (e.g., `'shared/directory/thing'`)
-4. Matching it against your shared configuration
-
-### Example Project Structure
-
-```
-your-project/
-├── node_modules/
-│   ├── shared/
-│   │   ├── directory/
-│   │   │   └── thing.js  // Exports a component or functionality
-│   │   ├── index.js      // imports './directory/thing' with relative path
-│   │   └── package.json  // version: 1.0.0
-│   └── my-module/
-│       ├── index.js      // Might also import from shared
-│       └── package.json  // version: 2.0.0
-├── src/
-│   └── index.js          // imports 'shared'
-└── webpack.config.js
-```
-
-### Configuration Example
+**How to use:**
 
 ```js
 // webpack.config.js
@@ -405,21 +380,23 @@ module.exports = {
   plugins: [
     new ModuleFederationPlugin({
       name: 'host',
-      experiments: {
-        nodeModulesReconstructedLookup: true // Enable the feature
-      },
       shared: {
-        'shared': {}, // Share the root module
-        'shared/directory/': {} // Share all modules under this path
+        'shared': { nodeModulesReconstructedLookup: true }, // Share the root module with enhanced lookup
+        'shared/directory/': { nodeModulesReconstructedLookup: true } // Share all modules under this path with enhanced lookup
       }
     })
   ]
 };
 ```
 
-### Code Example
+**When to use:**
+1. Your shared modules use relative imports internally (e.g., `./directory/thing`)
+2. You're sharing a package that has internal subdirectory imports
+3. Module Federation isn't correctly sharing submodules because the request doesn't match the shared configuration
 
-This is the key difference - you don't directly import the deep path, but it gets shared automatically when used internally:
+This option is only effective for the specific shared item where it is set.
+
+**Example Project Structure and Code**
 
 ```js
 // shared/index.js (inside node_modules)
@@ -432,15 +409,6 @@ console.log(version); // "1.0.0"
 console.log(thing); // The correctly shared submodule
 ```
 
-Without this experiment, the relative import in `shared/index.js` wouldn't be properly shared, potentially leading to duplicate instances of the same module.
-
-### When to Use This Feature
-
-This feature is particularly useful in scenarios where:
-1. Your shared modules use relative imports internally (e.g., `./directory/thing`)
-2. You're sharing a package that has internal subdirectory imports
-3. Module Federation isn't correctly sharing submodules because the request doesn't match the shared configuration
-
 ## Advanced Filtering Examples (`include`/`exclude`)
 
 Here are focused examples for using `include` and `exclude`:

apps/website-new/docs/en/configure/experiments.mdx

@@ -47,24 +47,24 @@ When using this mode, all entrypoints will initialize asynchronously. If you're
 
 ## nodeModulesReconstructedLookup
 
-- Type: `boolean`
-- Required: No
-- Default: `false`
+- **Type:** `boolean`
+- **Required:** No
+- **Default:** `false`
 
 Enables enhanced module resolution for packages located in `node_modules`, particularly for modules that use relative imports internally.
 
-**What it solves**: When a shared module uses relative imports (e.g., `import './directory/thing'`), Module Federation might not correctly recognize these as matching your shared configuration. This experiment reconstructs the full path and extracts the proper module name to enable correct sharing.
+**What it solves**: When a shared module uses relative imports (e.g., `import './directory/thing'`), Module Federation might not correctly recognize these as matching your shared configuration. This option reconstructs the full path and extracts the proper module name to enable correct sharing.
+
+**How to use:**
+
+Set `nodeModulesReconstructedLookup: true` on individual shared items that need this behavior:
 
 ```ts
-// Simple example
 new ModuleFederationPlugin({
   name: 'host',
-  experiments: {
-    nodeModulesReconstructedLookup: true
-  },
   shared: {
-    'shared': {},
-    'shared/directory/': {}
+    'shared': { nodeModulesReconstructedLookup: true },
+    'shared/directory/': { nodeModulesReconstructedLookup: true }
   }
 });
 ```

apps/website-new/docs/en/guide/basic/vite.mdx

@@ -1,16 +1,21 @@
 # Vite Plugin
 
+:::tip
+This is a community plugin.
+:::
+
 - Can build modules that meet the `Module Federation` loading specifications.
 - Can consume modules that adhere to the `Module Federation` specifications using aliases.
 - Can configure shared dependencies for modules, so that when the host environment of the loaded module already has the corresponding dependency, it will not be loaded again.
 
+
 :::warning Unsupported Options
 Except for the [dev、dts](../../configure/dev.html) options, all options are supported
 :::
 - roadmap 🗓️
   - When a module has remote types, it will automatically download and consume the types of the remote modules.
   - Consuming remote modules will have hot update capabilities.
-  - nuxt ssr 
+  - nuxt ssr
 
 ## Quick Start