riley/rust-react-ssr

Fork 0

Known limitations? #1

New issue

Open

opened 2024-09-25 23:25:36 +00:00 by Schachte · 7 comments

Schachte commented

2024-09-25 23:25:36 +00:00

(Migrated from github.com)

Aside from being a toy project, any known limitations with this current approach for doing SSR with React in Rust?

Been having server side hydration issues with various node APIs in my approach when using deno_core, so might just roll with V8. Thanks for making this public!

Aside from being a toy project, any known limitations with this current approach for doing SSR with React in Rust? Been having server side hydration issues with various node APIs in my approach when using deno_core, so might just roll with V8. Thanks for making this public!

rileyseaburg commented

2024-09-26 02:27:50 +00:00

(Migrated from github.com)

@Schachte I ended up running into a lot of the same issues that deno had at the time, because deno was using rust-ssr under the hood.

Implementing V8 itself was very resource intensive because it need to compile the whole c++ linker and that was brought into the code.

As far as the the ssr implementation, I just pushed some code I found in my working directory.

Overall it has an issue with webpack and static exporting not registering properly.

I'm sure it's a skill issue, because I did have it working at one point, but I ran into hydration issues.

I ended up rolling my own version of react and doing more of an island architecture with each page loading it's own react bundle.

@Schachte I ended up running into a lot of the same issues that deno had at the time, because deno was using rust-ssr under the hood. Implementing V8 itself was very resource intensive because it need to compile the whole c++ linker and that was brought into the code. As far as the the ssr implementation, I just pushed some code I found in my working directory. Overall it has an issue with webpack and static exporting not registering properly. I'm sure it's a skill issue, because I did have it working at one point, but I ran into hydration issues. I ended up rolling my own version of react and doing more of an island architecture with each page loading it's own react bundle.

👍 1

rileyseaburg commented

2024-09-26 02:28:25 +00:00

(Migrated from github.com)

It's time to revisit this because deno has come out with a 2.0

👀 1 🎉 1

Schachte commented

2024-10-11 06:41:54 +00:00

(Migrated from github.com)

@RileySeaburg Just got back from holiday, will take another peek. Cheers!

👍 1

Schachte commented

2024-10-12 05:11:44 +00:00

(Migrated from github.com)

@RileySeaburg Rolled an alternative using the v8 bindings from Deno. Basically just a POC right now, but SSR and clientside hydration is working.

https://github.com/Schachte/kaffe-rs

Lots of fiddling with bundle oriented things.. I'll just have to think about making it more generic and reusable

@RileySeaburg Rolled an alternative using the v8 bindings from Deno. Basically just a POC right now, but SSR and clientside hydration is working. https://github.com/Schachte/kaffe-rs Lots of fiddling with bundle oriented things.. I'll just have to think about making it more generic and reusable

👀 1 🚀 1

rileyseaburg commented

2024-10-14 13:44:39 +00:00

(Migrated from github.com)

@Schachte

This looks great!

Looks like deno_core started building their v8 export right around the time I stopped working on this, which is great because compiling v8 was crazy rough.

I'm gonna test your project out and let you know what I get!

@Schachte This looks great! Looks like deno_core started building their v8 export right around the time I stopped working on this, which is great because compiling v8 was crazy rough. I'm gonna test your project out and let you know what I get!

Schachte commented

2024-10-14 15:37:03 +00:00

(Migrated from github.com)

@Schachte

This looks great!

Looks like deno_core started building their v8 export right around the time I stopped working on this, which is great because compiling v8 was crazy rough.

I'm gonna test your project out and let you know what I get!

Sweet! I've been changing things quite a bit, so curious on your thoughts.

I basically want a simple SSG where the focus is Markdown and not code or configuration, but with the support of embedding interactive React components if needed.

> @Schachte > > > > This looks great! > > > > Looks like deno_core started building their v8 export right around the time I stopped working on this, which is great because compiling v8 was crazy rough. > > > > I'm gonna test your project out and let you know what I get! Sweet! I've been changing things quite a bit, so curious on your thoughts. I basically want a simple SSG where the focus is Markdown and not code or configuration, but with the support of embedding interactive React components if needed.

codetether[bot] commented

2026-06-04 16:22:56 +00:00

(Migrated from github.com)