-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
feat(webpack): create build log for remotes to help debug errors #22539
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
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.
One comment duplicated just, but LGTM
import { fork } from 'node:child_process'; | ||
import { join } from 'node:path'; | ||
import { createWriteStream } from 'node:fs'; |
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.
Will we run into issues with this style of import for users on older versions of Node?
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.
It's supported since Node 16, and we already use it in a few places.
import { fork } from 'node:child_process'; | ||
import { basename, dirname, join } from 'node:path'; | ||
import { createWriteStream, cpSync } from 'node:fs'; |
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.
Same as above
Merging this sine the failure is related to The failing |
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. |
This PR adds a log file for users to inspect whenever the remotes fail to build.
Users will see an error like this when serving host fails at the build step:
Current Behavior
Errors are swallowed since
run-many
is logging to stdout.Expected Behavior
Errors should be surfaced, in this case, via a build log file.
Related Issue(s)
Fixes #