Description

This PR fixes a bug where errors occurring during Hash.prototype.write() were silently swallowed instead of being surfaced.

Problem

In lib/internal/crypto/hash.js, the _transform implementation did not check the return value of this[kHandle].update(). While the synchronous update() method correctly throws ERR_CRYPTO_HASH_UPDATE_FAILED on failure, the streaming interface continued execution even if the underlying ncrypto binding returned false. This resulted in incorrect hash outputs without any error notification to the user.

Solution

Updated Hash.prototype._transform to check the return value of the internal update() call. If it returns false, the error is passed to the stream callback, triggering an 'error' event as expected for a stream.Transform instance.

Validation

• Added a regression test test/parallel/test-crypto-hash-stream-error.js.
• The test mocks the internal handle using kHandle to simulate an update failure and verifies that an 'error' event with ERR_CRYPTO_HASH_UPDATE_FAILED is emitted.
• Verified that the test fails without this change and passes with it.
• Verified that existing crypto tests (test/parallel/test-crypto-hash.js) still pass.

Checklist

• make lint-js passes
• make test-parallel (relevant to crypto) passes
• Commit message follows the Node.js guidelines

Fixes: #63258