Skip to content

docs(experiments): clarify optimization target defaults #5109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tonoizer wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs(experiments): clarify optimization target defaults #5109

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions apps/website-new/docs/en/configure/experiments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,9 +84,9 @@ The options can be combined. Calling an API for a disabled capability throws an

- Type: `'web' | 'node'`
- Required: No
- Default: Inferred from Webpack's `target` option (usually `'web'`)
- Default: Not set; not inferred from Webpack or Rspack's `target` option

This option defines the `ENV_TARGET` global constant during the build, specifying the intended execution environment.
This option defines the `ENV_TARGET` global constant during the build, specifying the intended execution environment. It is only applied when explicitly set; the plugin does not infer it from the bundler's `target` option.

**Impact:**

Expand All @@ -97,7 +97,7 @@ This option defines the `ENV_TARGET` global constant during the build, specifyin
- Ensures Node.js-specific remote entry loading mechanisms are used (`loadEntryNode`).
- Includes the necessary Node.js-specific functions from the SDK (`createScriptNode`, `loadScriptNode`) in the bundle, allowing the federated application to function correctly in Node.js.

Explicitly setting this value is recommended to ensure the intended optimizations are applied, especially in universal or server-side rendering scenarios.
Explicitly setting this value is recommended to ensure the intended optimizations are applied. For web builds, set `target: 'web'` to enable compile-time elimination of Node.js-specific loader code; set `target: 'node'` for Node.js builds, especially in universal or server-side rendering scenarios.

### Impact of Optimization Flags on `remoteEntry.js` Size

Expand Down
Loading