-
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
fix(js): node executor should always log error #17622
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 15, 2023 17:18
ba6a2cc
to
ef3670e
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 15, 2023 17:22
ef3670e
to
8af0851
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 15, 2023 17:25
8af0851
to
3fd6ec6
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
2 times, most recently
from
June 15, 2023 17:38
3bfc7e9
to
0198de4
Compare
mandarini
commented
Jun 15, 2023
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 09:38
0198de4
to
dbf8505
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 10:08
dbf8505
to
e74c18b
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 12:16
cb63166
to
e05bf5a
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 12:18
e05bf5a
to
7f7a815
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 12:25
7f7a815
to
179893e
Compare
meeroslav
reviewed
Jun 16, 2023
meeroslav
approved these changes
Jun 16, 2023
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
jaysoo
approved these changes
Jun 16, 2023
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 13:47
179893e
to
4a6c86c
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 13:56
4a6c86c
to
75c980b
Compare
mandarini
commented
Jun 16, 2023
mandarini
commented
Jun 16, 2023
This was
linked to
issues
Jun 16, 2023
jaysoo
approved these changes
Jun 16, 2023
mandarini
force-pushed
the
fix/js-node-throw-error
branch
2 times, most recently
from
June 16, 2023 15:16
541b33c
to
5c6248c
Compare
mandarini
force-pushed
the
fix/js-node-throw-error
branch
from
June 16, 2023 15:55
5c6248c
to
1f6011c
Compare
ndcunningham
approved these changes
Jun 16, 2023
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Current Behavior
When using the
nx/js:node
executor, error is swallowed unless you're inwatch
mode.Expected Behavior
Error should always be logged.
Also, we should infer the
outputFileName
from themain
entrypoint as set in build options.Related Issue(s)
Fixes #17595 #17627 #17083