How does WASM fit into the T3 stack?
could someone help me understand where webASM fits into this stack?
If I understand correctly, does NextJS internally do all the work of crunching the frontend into a WASM binary or is this something I need to do additional work to take advantage of?
Thanks for any help I might have some holes in my understanding here.
4 Replies
There is no wasm in the t3 stack
Next js ships Javascript to the client not a wasm binary
ok so it's nextjs that ships the binary to the browser.
no its not a binary
its javascript
