fix: increase the maximum possible file size that jest-haste-map can handle

[lanpai]

Summary

Currently, the read file is decoded using UTF8 regardless of whether the worker needs to or not. This bottlenecks the maximum file size that the worker can hash to ~536MB (maximum length of a string) which causes a hard crash if exceeded. For files that don't need to be decoded and are only hashed, this change allows the worker to hash the file without decoding it, leaving it as a buffer. Since buffers have a maximum size of ~2GB on 64-bit systems, this increases the maximum possible file size significantly.

For files that were already successfully decoded in previous steps (eg. JSON files), the worker will continue to hash the already decoded content string instead of rereading the file.

Test plan

Tests for the hashing are already handled in jest-haste-map/src/__tests__/worker.test.js

[SimenB]

cool, works for me!

[SimenB]

https://github.com/facebook/jest/releases/tag/v29.0.0-alpha.3

[SimenB]

https://github.com/facebook/jest/releases/tag/v29.0.0

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.