Oh, one more thing! I'd like to share an excerpt from the README to make sure folks considering this approach understand all the cons that I could think of:
```
As with all things in life, there are considerations to take into account before using vite-rs:
It's one more thing to debug when things go wrong.
It'll increase compile time. See the note on compile times for large assets.
For those deploying to embedded devices: it'll increase your binary size.
Shipping frontend with your backend can slow you down as you'll have to wait for your Rust backend to compile everytime you want to release a new build. Similarly, failing CI/CD pipelines pertaining to the backend will also stop your frontend frontend from deploying.
It may be faster or cheaper to deploy your frontend on CDNs instead of serving it.
I used to work at Resemble.ai and we used models that did real-time synthesis. I don’t think it’s particularly difficult anymore, even without sacrificing quality.
I’ve integrated vite with a rust backend[1] and so many people have asked me how I managed to achieve SSR because they equate SSR with render+hydrate but it’s really just classical SSR. I think I can finally make their dreams come true because of this.
I switched from CRA to Vite for create-rust-app[1]. If you ever needed to bundle JS/TS in an SSR framework (language agnostic), vite is a great choice :)
I’ve been working on an OS project to help people get on this bandwagon: create-rust-app [1]. The folks over at shuttle.rs also wrote a blogpost around a similar topic which was a very interesting read as a rust developer. [2]
One of the first requests I got for ‘create-rust-app’ was from a friend of mine regarding ViteJS. At the time, I didn’t know how awesome and fast ViteJS was as opposed to webpack and the name sounded like a JavaScript library so I didn’t really see the point. Upon a second review of the project, I realized the best thing I could do for the rust web dev community was to create an example of how to integrate ViteJS-based SSR in rust. And voilà, here it is. The docs also link to an “awesome list” which references create-rust-app [1].
This integration paves the way for things like adding multiple front end framework choices for the project and potentially doing SSG in rust.
Haha love the name. Sad to see it’s not an actual framework. For those looking for something more akin to a framework, try create-rust-app [1]. I plan to add a templating plugin soon!
I know this is not realistic, but the only thing rust is missing is faster compilation times. To be fair, it’s already super fast.
I was adding a repl[1] to create-react-app[2] (trying to achieve something like RoR’s console) and it took way too long for it to boot simply because the dependencies for something like a full scale web app take long to compile. Even with incremental compilation, that first boot time was too much.
Over the past few months, I've been trying to contribute to the rust ecosystem to enable devs to make webapps comfortably.
The latest challenge I've been addressing is auto generating react hooks to use Rust API endpoints. I'm just about ready to publish it soon. These kinds of things are much easier to do in rust rather than other languages.
```
As with all things in life, there are considerations to take into account before using vite-rs:
```