I had a deeper look at https://fresh.deno.dev and it actually looks perfect for a project like this.
You can do server-side rendering by default, but also have the ability to easily load partials asynchronously afterwards (e.g. for loading interaction kinds like comments, reactions, etc.).
I had a deeper look at https://fresh.deno.dev and it actually looks perfect for a project like this.
You can do server-side rendering by default, but also have the ability to easily load partials asynchronously afterwards (e.g. for loading interaction kinds like comments, reactions, etc.).
Could also be useful for #6.
raucao
added the idea label 2024-11-18 11:46:39 +00:00
raucao
changed title from Port to Fresh to Port app to Fresh2024-11-18 11:46:52 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I had a deeper look at https://fresh.deno.dev and it actually looks perfect for a project like this.
You can do server-side rendering by default, but also have the ability to easily load partials asynchronously afterwards (e.g. for loading interaction kinds like comments, reactions, etc.).
Could also be useful for #6.
Port to Freshto Port app to FreshAllegedly, Fresh 2.0 will be released soon. Waiting for that to avoid porting.
Stable release goal is September. But we can try the alpha (or beta later):
https://deno.com/blog/an-update-on-fresh
https://deno.com/blog/fresh-and-vite
The init/setup there is still broken for me. Waiting for next beta.