-
Notifications
You must be signed in to change notification settings - Fork 2.5k
fix(module-federation): ensure the static remotes env var is used for task hashing #21390 #21414
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.
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 25964a2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just left a non-blocking suggestion.
packages/angular/src/migrations/update-18-0-0/add-mf-env-var-to-target-defaults.ts
Show resolved
Hide resolved
6c460fe
to
25964a2
Compare
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
When a remote is built and served via the
module-federation-dev-server
an env var is used point to a single file server, allowing for increased performance benefits locally.However, this env var isn't taken into consideration when the task hash is calculated, leading to false positives.
Expected Behavior
Ensure the env var is added to the executor inputs in target defaults in nx.json.
Related Issue(s)
Fixes #21390