refactor: inline all bootstrap files and enable asyncStartup everywhere

[ScriptedAlchemy]

Summary

• Inline ~155 bootstrap.* files into their corresponding index/main entry files and delete them
• Add experiments: { asyncStartup: true } to all @module-federation/enhanced webpack/rspack/rsbuild configs
• Add shareStrategy: 'loaded-first' to all Module Federation plugin configs

With experiments: { asyncStartup: true }, Module Federation handles the async boundary internally, making the manual import('./bootstrap') wrapper unnecessary. This removes the indirection across all examples in the repo.

Scope

70+ example projects across the full repo, including:

• advanced-api/* (automatic-vendor-sharing, dynamic-remotes, dynamic-remotes-runtime-environment-variables, dynamic-remotes-synchronous-imports)
• apollo-client/*
• clo/*, cra/*
• cloud/azure-functions-node-v4/*
• complete-react-case/*, comprehensive-demo-react16/*, comprehensive-demo-react18/*
• css-isolation/*, dashboard-admin-react-rspack-material-ui/*
• different-react-versions/* (all variants: base, 16-17-typescript, 16-18, isolated, typescript)
• dynamic-system-host/*, error-boundary/*
• federated-css/* (consumers-react and expose-remotes)
• federated-css-react-ssr/*, federated-library-from-cdn/*, federated-npm/*
• frontend-discovery-service/*, native-federation-react/*, native-federation-tests-typescript-plugins/*
• nested-remote/*, nextjs-host-react-remote/*
• react-16-17-18-ssr/*, react-18-code-splitting/*, react-18-server-2-server/*, react-18-ssr/*
• react-in-vue/*, react-livereload/*, react-manifest-example/*
• react-nextjs/*, react-preact-runtime-typescript/*
• react-sharedworker/* (both main bootstrap and worker bootstrap)
• react-storybook/*, react-webpack-host-vite-remote/*
• redux-reducer-injection/*, rsbuild-vue3-vuex/*
• rspack_hmr/*, rspack-webpack-interop/*, rspack-webpack-offload/*
• runtime-plugins/* (control-sharing, isolate-shared-dependencies, multiple-react-versions, offline-remote, remote-control, remote-router, single-runtime)
• rust-wasm/*, self-healing/*, server-side-rendering/*
• shared-context/*, shared-directory/*, shared-routes2/*, shared-routing/*
• shared-store-cross-framework/*, simple-node/*, third-party-scripts/*
• typescript/*, typescript-monorepo/*, typescript-project-references/*, typescript-react-fallback/*
• typescript-react-monorepo/*, typescript-react-monorepo-test/*
• vue-cli/*, vue2-in-vue3/*
• Config-only changes (asyncStartup/shareStrategy): basic-host-remote/*, i18next-nextjs-react/*, modernjs/*, modernjs-classic-tractor-example/*, modernjs-ssr/*, quasar-cli-vue3-webpack-javascript/*, server-side-render-only/*, vue3-cli-demo/*

Exclusions

• umd-federation/app1 — uses native webpack.container.ModuleFederationPlugin (no asyncStartup support), bootstrap pattern still required
• angular-universal-ssr — server-bootstrap.ts is a server-side Express setup, not an MF async boundary

Test plan

• Verify all affected example e2e tests pass in CI
• Verify no remaining bootstrap.* files exist (except umd-federation/app1 and angular-universal-ssr)
• Verify no remaining import('./bootstrap') references (except exclusions above)

🤖 Generated with Claude Code

To fix the problem, we should remove the unused ReactDOM named import while keeping the createRoot import intact. This eliminates the unused symbol without changing the program’s behavior.

Concretely, in dashboard-admin-react-rspack-material-ui/faq-app/src/index.js, edit the import on line 3 to only import createRoot from 'react-dom/client'. No other code changes are required, as there are no references to ReactDOM elsewhere in the shown snippet. No additional methods, imports, or definitions are needed.

To fix an unused import, remove the import statement if the symbol is never referenced in the file and there are no required side effects. In this case, the lodash default import is not referenced anywhere in federated-npm/app3/src/index.js, and lodash is not being imported for side effects. The best minimal fix is to delete line 4 (import lodash from 'lodash';) and leave the other imports and code intact. No additional methods, imports, or definitions are needed.

In general, to fix this problem you either (a) configure the project to treat this file as TSX (e.g., rename to .tsx and ensure jsx is enabled), or (b) remove JSX syntax from .ts files and use React.createElement / ReactDOM.createRoot (or ReactDOM.render) calls instead. Since we are constrained to editing only this file and cannot rename it or adjust configuration, the best fix is to replace the JSX tree in the ReactDOM.render call with the equivalent React.createElement calls, preserving all existing behavior.

Concretely, in native-federation-react/host/src/app.ts, replace lines 11–13:

  <React.StrictMode>
    <App />
  </React.StrictMode>,

with a React.createElement expression that constructs the same component tree without JSX, e.g.:

  React.createElement(
    React.StrictMode,
    null,
    React.createElement(App)
  ),

This keeps the call to ReactDOM.render intact, preserves the StrictMode wrapper and App rendering, and uses only plain TypeScript/JavaScript syntax. No additional imports or definitions are needed, because React and App are already imported.

To fix the parsing error without relying on JSX support, replace the JSX-based call to ReactDOM.render with an equivalent that uses React.createElement. JSX is syntactic sugar for React.createElement, so this preserves functionality while avoiding the / that the non‑JSX parser misinterprets. Specifically, change the ReactDOM.render call on lines 10–15 from:

ReactDOM.render(
  <React.StrictMode>
    <App />
  </React.StrictMode>,
  document.getElementById('root'),
);

to an explicit React.createElement tree:

ReactDOM.render(
  React.createElement(
    React.StrictMode,
    null,
    React.createElement(App, null),
  ),
  document.getElementById('root'),
);

No new imports are needed because React is already imported and provides createElement. All other parts of the file (date-fns usage and the async IIFE using loadRemoteModule) remain unchanged.

In general, to fix this problem you should make the ReactDOM.render call conform to the syntax rules of the parser used by CodeQL, removing the trailing comma after the last argument so it no longer expects an additional argument or comma.

Concretely, in native-federation-react/host/src/app.ts, locate the ReactDOM.render invocation at lines 10–15. The second argument line currently reads document.getElementById('root'), with a trailing comma. Remove that trailing comma so that the function call has exactly two arguments and ends with document.getElementById('root') followed by the closing parenthesis and semicolon on the next line. No imports, methods, or definitions need to be added; this is purely a minor syntactic adjustment that preserves existing behavior.

In general, to fix this problem you should avoid using JSX syntax in a .ts file that is not configured for JSX, and instead use the appropriate Preact/React API (h, createElement, or render’s overload) to construct elements. This keeps the code valid TypeScript without requiring changes to the build configuration or file extensions.

The best targeted fix here is to replace the JSX <App /> with a non-JSX call that creates the same virtual node. In Preact, render accepts a VNode as its first argument, and App can usually be invoked as a function component: render(App({}), root) or render(h(App, {}), root). Since we want to avoid adding new imports or changing existing ones, we should use App({}) directly, which is valid for function components and does not rely on JSX or extra imports. This leaves behavior effectively unchanged: it still renders the App component into root, but avoids JSX syntax that CodeQL flags.

Concretely, in react-preact-runtime-typescript/remote/src/index.ts, on line 6, replace render(<App />, root); with render(App({}), root);. No additional imports or definitions are required, and no other lines in the snippet need modification.

In general, the error occurs because JSX syntax (<React.StrictMode> and <App />) is not valid in a .ts file parsed as plain TypeScript. To fix this without changing project configuration or file extensions, replace the JSX with equivalent calls to React.createElement. This preserves existing functionality while eliminating JSX syntax so the TypeScript parser (and CodeQL) see only standard TypeScript.

Concretely, in react-preact-runtime-typescript/shell/src/index.ts, lines 8–12 where root.render currently receives a JSX tree should be changed so that root.render instead receives a React.createElement call that constructs the same element hierarchy: React.createElement(React.StrictMode, null, React.createElement(App)). No new imports or other changes are needed, as React and App are already imported. All other lines remain unchanged.

In general, to fix an unused variable warning, either remove the variable declaration (and any associated computation) if it’s not needed, or start using the variable if it was meant to be used. Here, the SharedWorker instantiation is likely needed, but the binding to worker is not, since worker is never referenced.

The best minimal fix is to remove the const worker = part while keeping the new SharedWorker(...) expression. This keeps the side effect of creating the worker while eliminating the unused variable. Concretely, in react-sharedworker/host/src/index.js, change line 5 from const worker = new SharedWorker(new URL('./worker', import.meta.url)); to just new SharedWorker(new URL('./worker', import.meta.url));. No new imports, methods, or additional definitions are required.

---

In general, to fix unused import issues, you either remove the unused bindings or start using them in the code. Here, the best fix without changing functionality is to remove the unused named import Suspense and keep only what is actually used.

Specifically, in rust-wasm/host/src/index.js, line 1 should be changed from import React, { Suspense } from 'react'; to import React from 'react';. No other lines in this file need modification. No additional methods, imports, or definitions are required, because Suspense is not referenced anywhere in the shown code.