mf-perf

mf-context

$ARGUMENTS

--context

node scripts/performance-check.js --context '<MFContext-JSON>'

results

context.bundler.name

dev.disableAssetsAnalyze

• Disabling bundle size analysis during local development significantly improves HMR speed
• Add to the Rsbuild config:
  js

  dev: { disableAssetsAnalyze: true }

splitChunks

bundler.name

rspack

rsbuild

• Setting

  splitChunks.chunks

  to

  "async"

  reduces initial bundle size and speeds up first-screen loading
• Add to the build config:
  js

  output: { splitChunks: { chunks: 'async' } }

typescript

• If type generation (DTS) is the main bottleneck, options include:
  1. Temporarily disable DTS: set

     dts: false

     in the

     @module-federation/enhanced

     config
  2. Switch to

     ts-go

     for significantly faster type generation

"Would you like me to automatically try switching to

ts-go

and verify compatibility?"

1. Backup — copy the current generated type output directory (e.g.

   @mf-types/

   ) to a timestamped backup path such as

   @mf-types.bak.<timestamp>/

2. Configure — set

   dts.generateTypes.compilerInstance = "tsgo"

   in the Module Federation config
3. Install — install the required package:
   bash

   npm install @typescript/native-preview --save-dev

   (use the project's actual package manager from MFContext)
4. Regenerate — run:
   bash

   npx mf dts

5. Verify — diff the newly generated type output against the backup:
   • If the output is identical: inform the user that

     ts-go

     is compatible and the switch is safe; offer to remove the backup
   • If the output differs: revert the config change, restore the backup, and explain clearly what differs (e.g. missing declarations, changed signatures) so the user can decide whether the difference is acceptable