Hans Raaf
Hans Raaf
@nevkontakte I guess for us, it comes down to generics support and newer Go compilers. This is what makes rewriting the code impossible for us. And you are right: We...
I can still compile to WASM with that branch and no changes to my pretty complex setup, makes me happy ;-)
Well. This seems to be quite odd. We did not yet encounter a SIGILL from using go-app (and we use it quite extensive). Is there nothing you can get out...
Lol. Sorry about laughing, but why don't you use go-app as it is meant to work? I don't think that evaluation of some jQuery (I think) code that changes the...
This is what https://go-app.dev/states can be used for.
@krustowski I actually do not understand the problem? The local store belongs to the user. We use https://docs.nats.io/using-nats/developer/connecting/creds for authorization mostly. But if you have something on the frontend that...
I can confirm that our current most important App is compiling without any problems when I use this branch through a 'go.work' directive.
@maxence-charriere this is exactly the basis of what happens when using the NATS distrbuted authentication scheme I linked above.
@suntong you can call all your JS code from WASM, no need to GopherJS for that. The pre-compressed files problem IMHO is a GitHub pages problem and can't be solved...
Yes, the `go-app.dev` page is a thing of its own. I guess that there is too limited time for the developer to create such a search. I never used the...