doc: mention constructor comparison in assert.deepStrictEqual#60253
Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom Jan 24, 2026
Merged
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 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.
Updated
assert.deepStrictEqualdocs to explicitly mention that object constructors are included in the comparison. This clarifies behavior consistent withutil.isDeepStrictEqualand helps prevent confusion when comparing derived objects or proxy instances.