Repository navigation
chore!: Normalize repository, dropping Node <22.15.0 - #12
Merged
Merged
Conversation
Contributor
Author
|
Should we just skip node 22 for the failing stream conversion test? I'm trying to parse the exact issue but it's a bit arcane why node 22 is failing but 24 onward does not. |
Member
|
I dropped the test because it was testing a decision that node made in 14-22 where they would throw an unhandlable error if encoding was incorrect. It looks like they finally reversed the decision in 24 but I dropped it anyway. |
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
2 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.
Closes #11