Reverted changes to the test file as requested. The package already has
@types/react in devDependencies, so the original tests should work.

The tests were looking for React types in the root node_modules, but after
sinking React packages, they're only available in the local package context.
Updated the ThirdPartyExtractor to use packageRoot instead of projectRoot.

Force a fresh CI run to avoid potential cache issues.

Resolves CI build failure where @module-federation/sdk and other workspace
dependencies could not be found during TypeScript compilation.

Ensures proper module resolution for workspace dependencies in CI environment.

Remove explicit path mappings to rely on workspace dependency resolution,
matching the pattern used by other packages like enhanced.

… config

Prevents bundling workspace dependencies and instead relies on runtime resolution,
fixing TypeScript module resolution issues in CI environment.

- Remove tsconfig.lib.json file (not present on main branch)
- Update project.json to use tsconfig.json instead of tsconfig.lib.json
- Revert rollup.config.js to original state
- This matches the main branch configuration and avoids TypeScript resolution issues

- Added @nx/next to Next.js apps to fix server resolution errors
- Added React dependencies to runtime-demo apps
- Added React types for TypeScript compilation

Fixes CI failures from moving React packages from root.

- Added React and React types to all manifest-demo apps:
  - 3009-webpack-provider
  - 3010-rspack-provider
  - 3011-rspack-manifest-provider
  - 3012-rspack-js-entry-provider
  - webpack-host

Fixes "Cannot resolve 'react'" errors in e2e-manifest and e2e-runtime tests.

- Added React dependencies to bundle-size, reactStorybook, reactRemoteUI apps
- Added react-router-dom to webpack-host, react-ts-host, reactStorybook apps
- Fixes remaining "Cannot find module 'react'" and "Cannot find module 'react-router-dom'" errors

Should resolve remaining e2e-runtime, e2e-manifest, and Devtools failures.

- Switch rsbuild-plugin compiler from swc to tsc to fix module resolution errors
- Add explicit module paths in tsconfig for workspace dependencies
- Remove @module-federation/utilities dependency from example apps (3000, 3001, 3002)

- Update lockfile after dependency changes
- Sync with latest package.json changes

- Update bridge-react package dependencies to match workspace versions
- Add require.resolve aliases in vitest config for React modules
- Fix module resolution for tests after moving React to individual packages

- Use vitest.config.ts from main for bridge-react
- Use tsconfig.json from main for rsbuild-plugin

- Switch from vitest to @nx/jest executor for consistency with monorepo
- Convert test files from vitest to jest syntax
- Use monorepo jest dependencies instead of package-specific ones
- Fix TextEncoder/TextDecoder not defined in Node.js environment
- Update mocks to work with jest.mock() instead of vi.mock()
- Add jest.config.ts and tsconfig.spec.json for proper test configuration
- Fix TypeScript errors in test files

…19 build

… issues

This fixes the React 19 compatibility issue where the legacy bridge-react
would throw an error when detecting React 19 in remote5.

- Revert remote5 to use React 19 to match main branch
- Revert host React types version to match main branch
- Revert remote5 test content to match main branch expectations

- Change jsx from 'react-jsx' to 'preserve' to match main branch
- This was causing build failures in the React sinking process

- All e2e tests now passing (15/15)
- Remote5 correctly loads React 19 component in React 18 host
- Module federation cross-version compatibility restored