Skip to content
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

Apr2018 node versions #110

Merged
merged 1 commit into from Jun 4, 2018
Merged

Apr2018 node versions #110

merged 1 commit into from Jun 4, 2018

Conversation

stash
Copy link
Collaborator

@stash stash commented Apr 30, 2018

Support Node 10.x and 9.x

@stash stash requested a review from ruoho April 30, 2018 20:57
@stash
Copy link
Collaborator Author

stash commented May 28, 2018

Re-tested with v10.2.1 locally and still works fine

@BridgeAR
Copy link
Contributor

@stash this fix is actually not correct. The message was never tested on older Node.js versions. The behavior is also documented: https://nodejs.org/api/assert.html#assert_assert_throws_block_error_message. The message would have been used in case no error would have been thrown.

The reason why Error instances work in Node.js >= 10 supports validation objects and errors are accepted as such as well (the non-enumerable properties message and name will also be validated instead of only using all enumerable properties in case errors are passed through).

I opened #113 to address this in a backwards compatible way.

@stash stash mentioned this pull request Jun 4, 2018
@stash stash merged commit 6171f70 into master Jun 4, 2018
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.

None yet

2 participants