Ruby-wasm changed their release filenames

[noahgibbs]

Now it's "3.2" instead of "3_2" everywhere. This is a simple find/replace, so not sure this is 100% correct. It works better with scarpe-wasm, by which I mean it lets me get to the next bug, which isn't with wasify :-)

[noahgibbs]

Hm. Yeah, looks like they changed other things too. This change lets wasify download the release, but it still gets JS errors when it's running, e.g. tmpdir apparently no longer works:

browser.umd.js:1281 Uncaught (in promise) Error: /usr/local/lib/ruby/3.2.0/tmpdir.rb:38:in `tmpdir': could not find a temporary directory (ArgumentError)
/usr/local/lib/ruby/gems/3.2.0/gems/lacci-0.3.0/lib/shoes/constants.rb:16:in `find_lib_dir'
/usr/local/lib/ruby/gems/3.2.0/gems/lacci-0.3.0/lib/shoes/constants.rb:24:in `<module:Constants>'
/usr/local/lib/ruby/gems/3.2.0/gems/lacci-0.3.0/lib/shoes/constants.rb:5:in `<class:Shoes>'
/usr/local/lib/ruby/gems/3.2.0/gems/lacci-0.3.0/lib/shoes/constants.rb:4:in `<top (required)>'
/usr/local/lib/ruby/gems/3.2.0/gems/lacci-0.3.0/lib/shoes.rb:19:in `require_relative'
/usr/local/lib/ruby/gems/3.2.0/gems/lacci-0.3.0/lib/shoes.rb:19:in `<top (required)>'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:85:in `require'
/usr/local/lib/ruby/gems/3.2.0/gems/scarpe-wasm-0.1.0/lib/scarpe/wasm_local.rb:6:in `<top (required)>'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:159:in `require'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:159:in `rescue in require'
<internal:/usr/local/lib/ruby/3.2.0/rubygems/core_ext/kernel_require.rb>:39:in `require'
eval:1:in `<main>'
-e:in `eval'
    at checkStatusTag (browser.umd.js:1281:21)
    at browser.umd.js:1318:11
    at wrapRbOperation (browser.umd.js:1288:18)
    at evalRbCode (browser.umd.js:1316:14)
    at RubyVM.eval (browser.umd.js:1004:18)
    at main (index_button_alert.rb.html:14:8)

[noahgibbs]

Hm. Maybe the way to go would be to download version 2.3.0 (current as of a week ago) instead of 2.4.0 (current today, and broken.) Like, grab 2.3.0 instead of latest.

[noahgibbs]

Closing in favour of #14. But something like this may be necessary in the long term regardless since there's a change in ruby-wasm naming conventions between 2.3.0 and 2.4.0+.