nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 Are you sunsetting Wasm support for nostrlib? I’m currently using the TinyGo/Wasm build, but I’m wondering if it’s time to move away from it.
Discussion
Did I sunset it? I would like to keep it but I thought my rewrite had already screwed it up so I just removed that last file.
I didn't have the time to test it or use it in any way.
Are you telling me it still works? How do I test it again? I'll bring it all back if I can.
Yeah, it still works, but at the cost of removing several dependencies and making the codebase a bit of a mess for TinyGo. Standard Wasm should run it without any hassle. However, since I use the tinygo branch for both TinyGo/Wasm and Go/Wasm, I can't provide a minimal diff for standard Go/Wasm alone.
You can test the tinygo branch with:
GOOS=js GOARCH=wasm tinygo test
And for standard Go, use wasmbrowsertest:
GOOS=js GOARCH=wasm go test
No need to worry about this if you are not interested in Wasm. I might be the only one actually using it right now.