Remove use of optional chaining in client #253
Merged
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.
Despite the optional chaining (
?.
) operator being supported in Node >= 14, I continue to see anecdotal reports from users of other libraries encounteringSyntaxError: Unexpected token '.'
, even when targeting Node.js 20.With all the weird, frustrating compatibility issues throughout the JS ecosystem, I take some comfort in having some control that I can exercise over this one. (Maybe I'm paranoid, but hey — at least I'm consistent about it?)