Just setup GH Pages workflow to build/deploy the W...
# compose-web
j
Just setup GH Pages workflow to build/deploy the Wasm based Compose for Web app but getting this for some reason. I'm deploying from
compose-web/build/dist/wasm/productionExecutable
....is this correct or is there some additional setup needed?
b
The dir is correct at least
m
I had the same issue on https://wasm.confetti-app.dev/, had to manually copy
Confetti.uninstanciated.mjs
to the
productionExecutable
dir
j
I guess I can add that copy to the GH action for now
I updated action (https://github.com/joreilly/chip-8/blob/main/.github/workflows/build-and-publish-web.yml) to copy over that file....and do see it in brach (https://github.com/joreilly/chip-8/tree/gh-pages) but getting different errors now
hmm, seems to be issue getting that ch8 file....though that seems to be there
m
Copy code
if (te == null) {
    document.getElementById("warning").style.display="none";
} else {
    throw te;
}
I think you can remove that part (or add the matching div)
(for the 1st error)
Ping @Dima Avdeev could we remove that leading
/
and have XHRs that support relative paths? (from the JSResourceImpl)
j
I'm going to do quick test at least deploying code that uses
chip-8/
at start of resource just to see that there's no other issues....
ok works at least with that change (but needs better solution of course) https://joreilly.github.io/chip-8/
still as slow as ever but that's a separate thing I need to look at
m
Also: we need a leadearboard 😉
j
I was just thinking exactly the same thing 😃
m
I've reached level 2 once 😄!
j
I'll add option to select a few more ROMs as well at some point
I ported original JVM based implementation across to be KMP based and did crude update of some the threading code that it was using to allow it to run there.....but probably needs some rework.....that might help address some of the performance issues
but fwiw it certainly runs a lot more smoothly on Compose for Desktop
d
Ping @Dima Avdeev could we remove that leading
/
and have XHRs that support relative paths? (from the JSResourceImpl)
As I correctly understand, we need to fix resource path on JS side ?
I can create an Issue for that
m
Yep, looks like it would work if we just removed the
/
:
Copy code
req.open("GET", path, true)
But maybe there's more to it, I'm not super familiar with that code
Especially, looks like the leading
/
was added on purpose:
"/$path"
. So maybe it's something to do with the XHR API or something else?
d
Ok, thanks! I will create an Issue to understand what we can do with it on JS
thank you color 2
m
Thanks!
d