bytecodealliance / bytecodealliance/ComponentizeJS

Reproducible builds

オープン
#321 コメント 0 件 リアクション 1 件 担当者 0 名 GitHub で見る
主要言語
Rust
スター
391
フォーク
53
平均マージ
3日 5時間
マージ済み PR(30日)
1

説明

I have used ComponentizeJS in 3 different projects

I'm seeing with every project that the wasm file output is not reproducible from one build to the next

For example: https://github.com/rhodey/lock.host-wasm-js

I have `npm run bundle` and `npm run build`

I run `sha256sum dist/bundle.js` and determine the same js bundle is being produced

I run `sha256sum dist/bundle.wasm` and determine the wasm file is different with every run of `componentize-js`

It is not hard to imagine that more than 1 thing would need to change to get reproducible builds

A first thought is I think from what I have read that ComponentizeJS is doing something like snapshot of the JS Runtime memory in order to get faster boots. And so that is suspicious as an area of non determinism.

I will much appreciate any help with achieving reproducible builds and if it can be achieved quicker by disabling some features and losing some speed it would be acceptable for my purposes

Thanks!!

コントリビューションガイド

このリポジトリのコントリビューションガイドは索引されていません

評価

この issue はまだ評価されていません。

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。