fix(cloudflare): remove WASM and replace hash to version #594
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.
Related to #470
To support Cloudflare, I had to remove the WASM we had.
The WASM has been moved to this repo if anyone wants to use it: https://github.com/aralroca/wyhash
What I did was that if the runtime wasn't Bun (ex: Node.js), instead of using
Bun.hash
I pulled the same algorithm, where the Bun ZIG code had been moved to WASM. This works well in Node.js, the problem is that Cloudflare does not support WASM instances.The only place that was used was to generate the
VERSION_HASH
, theVERSION_HASH
was the version of Brisa with Hash, where the Brisa files were put as the RPC, etc, so that in new versions when renaming there are no cache problems. However, it was not necessary to have the hash, you can have the Brisa version directly and thus solve this problem with Cloudflare, and at the same time, we get rid of this WASM and clean the code.