Skip to content

Conversation

@andrew-coleman
Copy link
Member

resolves #434

Signed-off-by: andrew-coleman andrew_coleman@uk.ibm.com

Signed-off-by: andrew-coleman <andrew_coleman@uk.ibm.com>
@coveralls
Copy link

Coverage Status

Coverage remained the same at 100.0% when pulling 880a176 on range_error into 66ecc0b on master.

@mattbaileyuk
Copy link
Member

For future context, this is avoiding nodejs/node#27732 whereby the use of the node.js spread function overloads the push() function.

@mattbaileyuk mattbaileyuk merged commit 63b4ffc into master Apr 22, 2020
@mattbaileyuk mattbaileyuk deleted the range_error branch April 22, 2020 09:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Path expression on very large object causes RangeError

4 participants