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
fix(core): swap default method for output capture #12535
fix(core): swap default method for output capture #12535
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
BREAKING CHANGE: Swaps from direct-nodejs to pipe for default output capture mechanism. Less accurate for executors that don't use child process, but still works for generic case. Previous behaviour still available through opt-in
833ef9d
to
d975d54
Compare
d975d54
to
d44c097
Compare
d44c097
to
36e7a26
Compare
36e7a26
to
c58a923
Compare
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.
Please check these afterwards
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
@xiongemi The output capture might be wrong here.
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
@xiongemi The output capture might be wrong here
"default": [] | ||
}, | ||
"format": { | ||
"type": "array", | ||
"description": "List of module formats to output. Defaults to matching format from tsconfig (e.g. CJS for CommonJS, and ESM otherwise).", | ||
"description": "Set the output format(s).", |
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.
Double check this
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
@xiongemi Check the output capture of these executors as well
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
Check if this prints correctly
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
@jaysoo Check this output capture
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
The output capture might be wrong here.
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
@xiongemi These output captures might be wrong
@@ -1,4 +1,6 @@ | |||
{ | |||
"version": 2, | |||
"outputCapture": "direct-nodejs", |
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.
Is this output capture correct?
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.
Merging for v15
c58a923
to
1940a08
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. |
BREAKING CHANGE: Swaps from direct-nodejs to pipe for default output capture mechanism. Less accurate for executors that don't use child process, but still works for generic case. Previous behaviour still available through opt-in