Conversation
Contributor
Author
|
Link to nitro issue: nitrojs/nitro#2283 I'll take care of this tomorrow |
This was referenced Mar 21, 2024
Contributor
Author
|
Should I close this as fixed upstream or keep it for extra runtime security? |
Member
|
i would suggest to keep for safety 👍🏼 |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Types provided by nitro don't reflect the situation on the shape of nitro tasks options. Here,
Object.entries(undefined)throws an error.I will update the types on Nitro after this PR.
Note: this PR doesn't need to be merged if the fix is provided upstream on nitro, this is just a patch in the meanwhile