Conversation
…ation - Implemented config-exposes-check.js to validate exposes configuration in module federation. - Created module-info.js to fetch and display information about remote modules. - Added performance-check.js to provide performance-related recommendations for bundlers. - Developed shared-config-check.js to identify conflicts between shared and external dependencies. - Introduced type-check.js to validate TypeScript configuration and type generation status.
|
✅ Deploy Preview for module-federation-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
@module-federation/devtools
@module-federation/cli
create-module-federation
@module-federation/data-prefetch
@module-federation/dts-plugin
@module-federation/enhanced
@module-federation/error-codes
@module-federation/esbuild
@module-federation/managers
@module-federation/manifest
@module-federation/metro
@module-federation/metro-plugin-rnc-cli
@module-federation/metro-plugin-rnef
@module-federation/modern-js
@module-federation/modern-js-v3
@module-federation/native-federation-tests
@module-federation/native-federation-typescript
@module-federation/nextjs-mf
@module-federation/node
@module-federation/retry-plugin
@module-federation/rsbuild-plugin
@module-federation/rspack
@module-federation/rspress-plugin
@module-federation/runtime
@module-federation/runtime-core
@module-federation/runtime-tools
@module-federation/sdk
@module-federation/storybook-addon
@module-federation/third-party-dts-extractor
@module-federation/treeshake-frontend
@module-federation/treeshake-server
@module-federation/typescript
@module-federation/utilities
@module-federation/webpack-bundler-runtime
@module-federation/bridge-react
@module-federation/bridge-react-webpack-plugin
@module-federation/bridge-shared
@module-federation/bridge-vue3
@module-federation/inject-external-runtime-core-plugin
commit: |
Bundle Size Report10 package(s) changed, 30 unchanged. Package dist + ESM entry
Bundle targets
Consumer scenarios
Total dist (raw): 6.32 MB (no change) Bundle sizes are generated with rslib (Rspack). Package-root metrics preserve the historical report. Tracked subpath exports such as |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b3fbe912ee
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| session.close(); | ||
| tab = newTarget; | ||
| session = new Session(tab.webSocketDebuggerUrl); | ||
| await session.open(); | ||
| await Promise.all([ |
There was a problem hiding this comment.
When --click opens a new tab, this block replaces session with a fresh Session instance, but none of the Runtime.consoleAPICalled, Runtime.exceptionThrown, Network.*, or Log.entryAdded listeners that populate logs/network-idle state are attached to the new session. In the default followNewTab path, captures after the tab switch can miss runtime/network errors and report misleadingly clean results.
Useful? React with 👍 / 👎.
| Prefer this baseline command first: | ||
|
|
||
| ```bash | ||
| node ../scripts/browser-capture.mjs "<failing-page-url>" 20000 --vars __FEDERATION__,__webpack_require__,window.__FEDERATION__ |
There was a problem hiding this comment.
The runtime-error guidance points to ../scripts/browser-capture.mjs, but this skill’s scripts live under skills/mf/scripts and other sub-skills invoke them as node scripts/... from the skill root. In that execution context, ../scripts/... resolves to a non-existent path, so the automatic browser-capture flow fails before diagnosis starts.
Useful? React with 👍 / 👎.
| 'Quit Chrome and relaunch with remote debugging (macOS):\n' + | ||
| ' CHROME=$(find /Applications ~/Applications -name "Google Chrome" -path "*/MacOS/Google Chrome" 2>/dev/null | head -1)\n' + | ||
| ' killall "Google Chrome" 2>/dev/null; sleep 1\n' + | ||
| ' "$CHROME" --remote-debugging-port=9222 --user-data-dir="$HOME/Library/Application Support/Google/Chrome" &\n\n' + |
There was a problem hiding this comment.
The connection-error fallback tells users to relaunch Chrome with --user-data-dir="$HOME/Library/Application Support/Google/Chrome", which is the default profile directory and is rejected by modern Chrome for remote debugging. On first-run failures this advice loops users back into the same error instead of enabling CDP.
Useful? React with 👍 / 👎.
1 participant
Description
This PR updates the website docs and skill structure around AI onboarding for Module Federation.
It makes AI a more visible starting point in the Chinese docs, changes the quick start entry to guide users toward letting their agent read the docs first, and updates the AI/Skills pages to reflect the current unified
mfskill model.It also consolidates the previous MF skills into a single
skills/mfdirectory, folds the browser capture helper into the mainmfskill, and updates runtime troubleshooting guidance soRUNTIME-001/RUNTIME-008can use built-in browser capture while other runtime codes fall back to docs lookup.Documentation changes included:
/mfentrymfskill structure/mf integrate2.3.0as the version boundary for vagueRUNTIME-008reportingRelated Issue
N/A
Types of changes
Checklist