mirror of
https://github.com/nodejs/node.git
synced 2025-08-15 13:48:44 +02:00
5a0777776d
This only affects the writable side of LazyTransform and should not change the behavior of any LazyTransform streams (Cipher, Decipher, Cipheriv, Decipheriv, Hash, Hmac). If the user does not set defaultEncoding when creating a transform stream, WritableState uses 'utf8' by default. Only LazyTransform overwrites this with 'buffer' for strict backward compatibility. This was necessary when crypto.DEFAULT_ENCODING still existed. Now that DEFAULT_ENCODING has been removed, defaultEncoding is always 'buffer'. The writable side of LazyTransform appears to treat 'utf8' and 'buffer' in exactly the same way. Therefore, there seems to be no need to overwrite _writableState.defaultEncoding at this point. Nevertheless, because Node.js has failed to hide implementation details such as _writableState from the ecosystem, we may want to consider this a breaking change. Refs: https://github.com/nodejs/node/pull/47182 Refs: https://github.com/nodejs/node/pull/8611 PR-URL: https://github.com/nodejs/node/pull/49140 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com> Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com> |
||
|---|---|---|
| .. | ||
| add-abort-signal.js | ||
| buffer_list.js | ||
| compose.js | ||
| destroy.js | ||
| duplex.js | ||
| duplexify.js | ||
| end-of-stream.js | ||
| from.js | ||
| lazy_transform.js | ||
| legacy.js | ||
| operators.js | ||
| passthrough.js | ||
| pipeline.js | ||
| readable.js | ||
| state.js | ||
| transform.js | ||
| utils.js | ||
| writable.js | ||