thanks for making this. I've used this repo as inspiration and incoporated all the logic. However, as the client side app grows in complexity, SSR becomes an issue. For this reason, I've already followed your advice on how to turn of SSR by using:
The app runs fine in development by running make serve but fails at building due to various issues with external libraries (the use of reserved words etc). This can't be fixed manually and I like to entirely get rid of the SSR logic.
I haven't yet understood how react.go handles the JS vms pool. To be honest, I blindly used that code.
Any help to resolve my confusion is greatly appreciated!
Hi,
thanks for making this. I've used this repo as inspiration and incoporated all the logic. However, as the client side app grows in complexity, SSR becomes an issue. For this reason, I've already followed your advice on how to turn of SSR by using:
The app runs fine in development by running
make serve
but fails at building due to various issues with external libraries (the use of reserved words etc). This can't be fixed manually and I like to entirely get rid of the SSR logic.I haven't yet understood how react.go handles the JS vms pool. To be honest, I blindly used that code.
Any help to resolve my confusion is greatly appreciated!