Currently there's no way to specify a local copy of the latest ruby-3_2-wasm32-unknown-wasi-full-js.tar.gz, and so it gets downloaded every time. At least in Scarpe-Wasm, that's one of the major delays in the testing cycle.
The current method is to use curl to download https://github.com/ruby/ruby.wasm/releases/latest/download/ruby-3_2-wasm32-unknown-wasi-full-js.tar.gz, which has no way to tell what release is being downloaded -- and they change pretty constantly.
But if you point your browser at https://github.com/ruby/ruby.wasm/releases/latest, it will actually go to (at this moment) 2.2.0. So there's an HTTP redirect there. By following the HTTP redirect, we could find the name of the actual current release and then use a local copy if we've downloaded it before. We should never need more than one available at a time since we'll only ever use latest, so the storage needs aren't excessive. We would need somewhere to put it. Local directory where packaging occurs? Dot-directory in home? Configurable?
Currently there's no way to specify a local copy of the latest ruby-3_2-wasm32-unknown-wasi-full-js.tar.gz, and so it gets downloaded every time. At least in Scarpe-Wasm, that's one of the major delays in the testing cycle.
The current method is to use curl to download https://github.com/ruby/ruby.wasm/releases/latest/download/ruby-3_2-wasm32-unknown-wasi-full-js.tar.gz, which has no way to tell what release is being downloaded -- and they change pretty constantly.
But if you point your browser at https://github.com/ruby/ruby.wasm/releases/latest, it will actually go to (at this moment) 2.2.0. So there's an HTTP redirect there. By following the HTTP redirect, we could find the name of the actual current release and then use a local copy if we've downloaded it before. We should never need more than one available at a time since we'll only ever use latest, so the storage needs aren't excessive. We would need somewhere to put it. Local directory where packaging occurs? Dot-directory in home? Configurable?