#SSR

Matthias AndraschPerformance-Minded Development with Nuxt 3 <a href="https://youtu.be/dtpKrqvwUTU" rel="nofollow noopener" translate="no" target="_blank">https://youtu.be/dtpKrqvwUTU</a> <a href="https://social.tchncs.de/tags/nuxt" class="mention hashtag" rel="nofollow noopener" target="_blank">#nuxt</a> <a href="https://social.tchncs.de/tags/nuxtjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#nuxtjs</a> <a href="https://social.tchncs.de/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> <a href="https://social.tchncs.de/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a>

Matthias Andrasch(Finally) getting a better understanding of useFetch(), useLazyFetch() (or useAsyncData()) in <a href="https://social.tchncs.de/tags/nuxt" class="mention hashtag" rel="nofollow noopener" target="_blank">#nuxt</a> <a href="https://social.tchncs.de/tags/nuxtjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#nuxtjs</a> <a href="https://social.tchncs.de/tags/SSR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSR</a>. First Page Load vs. <Nuxt> client side navigation with injected and (automatic) window.__NUXT__ payload cache for fetch data confused me a little bit at first. 🤓 Plus: Lot's of composables to choose from 😁🤯Now wondering how performance optimization works.

Ayo AycoLast Thursday I have one engineer talk about ssr & web components at the AmsterdamJS meetup. Click-baity title, but I promise we tried to give the full picture. :)<a href="https://social.ayco.io/tags/webcomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomponents</a> <a href="https://social.ayco.io/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> <a href="https://social.ayco.io/tags/amsterdamjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#amsterdamjs</a>

MaikSSR Streaming: Existe la expectativa de la introducción de Streaming en Server-Side Rendering en la versión 20. 🚀 Un avance significativo en la percepción de carga y performance. <a href="https://mastodon.social/tags/SSR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSR</a> <a href="https://mastodon.social/tags/Streaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Streaming</a>Esto seria muy interesante 👀

Maik- Estabilización de Event Replay en SSR: Se robustece el mecanismo de replay de eventos en Server-Side Rendering, buscando un comportamiento más predecible y consistente. 🔄 <a href="https://mastodon.social/tags/SSR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSR</a>- Nuevas APIs: `resource` y `rxResource`:Se incorporan nuevas APIs para la gestión de recursos y operaciones HTTP reactivas, integrándose con el modelo de Signals. 🧰 <a href="https://mastodon.social/tags/Signals" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signals</a> <a href="https://mastodon.social/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a>Adios Rxjs??

Maik- SSR Mejorado El Server-Side Rendering recibe optimizaciones para mejorar los tiempos de carga inicial y el posicionamiento SEO de las aplicaciones. 🚀 <a href="https://mastodon.social/tags/SSR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSR</a>

Matthias AndraschMh, that's funny. When I navigate from <a href="https://mandrasch.dev/" rel="nofollow noopener" translate="no" target="_blank">https://mandrasch.dev/</a> via link in footer to <a href="https://mandrasch.dev/ssr-test" rel="nofollow noopener" translate="no" target="_blank">https://mandrasch.dev/ssr-test</a> - the build time is still shown. When I reload the page, the real server time is shown (as expected). 🤔 Although I set `export const prerender = false;` here <a href="https://github.com/mandrasch/mandrasch.dev/tree/main/src/routes/ssr-test" rel="nofollow noopener" translate="no" target="_blank">https://github.com/mandrasch/mandrasch.dev/tree/main/src/routes/ssr-test</a>. But I retrieve data from layout.server, need more time to learn about SvelteKit router I guess. Btw: Currently hosted on <a href="https://social.tchncs.de/tags/coolify" class="mention hashtag" rel="nofollow noopener" target="_blank">#coolify</a>. <a href="https://social.tchncs.de/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> <a href="https://social.tchncs.de/tags/sveltekit" class="mention hashtag" rel="nofollow noopener" target="_blank">#sveltekit</a> <a href="https://social.tchncs.de/tags/svelte" class="mention hashtag" rel="nofollow noopener" target="_blank">#svelte</a>

Sebastian LasseWait github user? You asked if you could react positively at issues? On behalf of fedi cause you love Public Broadcasters so much too?Off course you can! just try it out: <a href="https://github.com/wearenewpublic/demos/issues/8" rel="nofollow noopener" translate="no" target="_blank">https://github.com/wearenewpublic/demos/issues/8</a> <a href="https://digitalcourage.social/tags/activitypub" class="mention hashtag" rel="nofollow noopener" target="_blank">#activitypub</a> <a href="https://digitalcourage.social/tags/zdf" class="mention hashtag" rel="nofollow noopener" target="_blank">#zdf</a> <a href="https://digitalcourage.social/tags/cbc" class="mention hashtag" rel="nofollow noopener" target="_blank">#cbc</a> <a href="https://digitalcourage.social/tags/radiocanada" class="mention hashtag" rel="nofollow noopener" target="_blank">#radiocanada</a> <a href="https://digitalcourage.social/tags/srg" class="mention hashtag" rel="nofollow noopener" target="_blank">#srg</a> <a href="https://digitalcourage.social/tags/srf" class="mention hashtag" rel="nofollow noopener" target="_blank">#srf</a> <a href="https://digitalcourage.social/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> <a href="https://digitalcourage.social/tags/rtbr" class="mention hashtag" rel="nofollow noopener" target="_blank">#rtbr</a>

Peter KrönerWhat at least I *really* need is a unified DX for two types of component: 100% CSR or 100% SSR. None of that isomorphic garbage, but also no (huge) delta between the component models. This should be doable 💪 <a href="https://mastodon.social/tags/webcomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomponents</a> <a href="https://mastodon.social/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a>

Peter KrönerI'm starting to believe that <a href="https://mastodon.social/tags/SSR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSR</a> for <a href="https://mastodon.social/tags/webcomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomponents</a> is not really a well-defined concept. Unless the entire App is a react-like pure function, you'd really need to pre-render entire pages with JSDOM, Puppeteer or similar because components could possibly depend on (or modify everything on) any given page.

Matthias AndraschThis week I learned that full html page caching for <a href="https://social.tchncs.de/tags/SSR" class="mention hashtag" rel="nofollow noopener" target="_blank">#SSR</a> <a href="https://social.tchncs.de/tags/nodejs" class="mention hashtag" rel="nofollow noopener" target="_blank">#nodejs</a> (without static pre-rendering on build time) needs some custom work. E.g. setting up a cloudflare worker + cloudflare cache in front - or writing a redis response cache, use varnish, etc.My naive thought was that this is already baked into <a href="https://social.tchncs.de/tags/SvelteKit" class="mention hashtag" rel="nofollow noopener" target="_blank">#SvelteKit</a>, <a href="https://social.tchncs.de/tags/NuxtJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NuxtJS</a>, <a href="https://social.tchncs.de/tags/NextJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NextJS</a>, etc. Guess I'm a bit spoiled by Blitz Cache for CraftCMS (PHP) which just takes care of caching html responses + redirecting 🤓 <a href="https://social.tchncs.de/tags/caching" class="mention hashtag" rel="nofollow noopener" target="_blank">#caching</a> <a href="https://putyourlightson.com/plugins/blitz" rel="nofollow noopener" translate="no" target="_blank">https://putyourlightson.com/plugins/blitz</a>

Brian LeRoux 💚example using package.json for IaC with Hono and Enhance/SSR <a href="https://github.com/brianleroux/arc-example-hono-enhance-ssr/tree/main" rel="nofollow noopener" translate="no" target="_blank">https://github.com/brianleroux/arc-example-hono-enhance-ssr/tree/main</a><a href="https://indieweb.social/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> <a href="https://indieweb.social/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a> <a href="https://indieweb.social/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> <a href="https://indieweb.social/tags/webcomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomponents</a>

Brian LeRoux 💚The entire point of server-side (ssr) rendering is to return fully rendered content. (?)If you don't want the fully rendered interpreted result and instead want the higher level templating and instructions for the client to interpret that's called client-side rendering (csr).You can preserve the raw code for additional client render steps in Enhance. But for most elements you won't need to. And yes it can all be shadowdom also if you want to (but again yagni).<a href="https://indieweb.social/tags/webcomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomponents</a> <a href="https://indieweb.social/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> <a href="https://indieweb.social/tags/csr" class="mention hashtag" rel="nofollow noopener" target="_blank">#csr</a>

Brian LeRoux 💚Wordpress Plugin for server-side rendering Web Components anyone?<a href="https://github.com/enhance-dev/enhance-wordpress-plugin" rel="nofollow noopener" translate="no" target="_blank">https://github.com/enhance-dev/enhance-wordpress-plugin</a><a href="https://indieweb.social/@ryanbethel" class="u-url mention" rel="nofollow noopener" target="_blank">@ryanbethel</a> continues to go beast mode porting Enhance to anything that can run WASM. <a href="https://indieweb.social/tags/webcomponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcomponents</a> <a href="https://indieweb.social/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> <a href="https://indieweb.social/tags/html" class="mention hashtag" rel="nofollow noopener" target="_blank">#html</a> <a href="https://indieweb.social/tags/php" class="mention hashtag" rel="nofollow noopener" target="_blank">#php</a> <a href="https://indieweb.social/tags/wordpress" class="mention hashtag" rel="nofollow noopener" target="_blank">#wordpress</a>

Andreas SanderI did what every – exaggerating – <a href="https://toot.cafe/tags/webdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#webdev</a> has to do:Rewriting the own <a href="https://toot.cafe/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> and <a href="https://toot.cafe/tags/website" class="mention hashtag" rel="nofollow noopener" target="_blank">#website</a> after some years. New website, same URL, all posts should keep working under same URI.More stuff to come, I just had a few days and a few hours of free time to switch from custom static site renderer (<a href="https://andi1984.dev/posts/my-static-site-generator" rel="nofollow noopener" translate="no" target="_blank">https://andi1984.dev/posts/my-static-site-generator</a>) to <a href="https://toot.cafe/tags/nextjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#nextjs</a> with <a href="https://toot.cafe/tags/ssr" class="mention hashtag" rel="nofollow noopener" target="_blank">#ssr</a> and more dynamic content (planned).More to come for sure...<a href="https://andi1984.dev" rel="nofollow noopener" translate="no" target="_blank">https://andi1984.dev</a> <a href="https://andi1984.dev/rss.xml" rel="nofollow noopener" translate="no" target="_blank">https://andi1984.dev/rss.xml</a>

Recent searches

Search options

Administered by:

Server stats: