OWASP Nest Frontend Extension Options

[arkid15r]

Framework Comparison: Astro, Gatsby, Next.js, or Remix?

Hi everyone,

I'm exploring various frameworks for building static and dynamic websites and would love to hear your thoughts on the following options based on your own knowledge or experience:

• Astro: Excels at building static, performance-focused websites while allowing you to mix frameworks and load interactivity selectively.
• Gatsby: Ideal for static sites with a heavy focus on content and build-time data aggregation, benefiting from a mature plugin ecosystem.
• Next.js: A versatile, all-rounder framework that supports both SSR and SSG, making it great for dynamic, large-scale applications.
• Remix: Offers a modern, server-rendered experience with robust data loading and error handling, suitable for complex apps that demand reliability.

I’m looking for feedback on:

• Which one(s) should we consider or avoid for our projects?
• Why do you recommend (or not recommend) a particular framework?
• Any specific use cases where one framework stands out?
• Feel free to suggest any other frameworks you think we should consider!

Your input will be invaluable as we decide on the best framework to use moving forward.

Thanks in advance for your insights!

[yashgoyal0110]

I don’t think we need to switch. We’re already using React, which gives us the flexibility to build both static and dynamic applications as needed. With the right optimizations—like code splitting, lazy loading. we can achieve most of what these frameworks offer without adding extra complexity to our stack.

[arkid15r]

So we could do better SEO w/o Next.js? Currently we don't have dynamic data for crawlers and social media preview bots.

[yashgoyal0110]

Better to a certain and limited extent because when it comes to SEO and social media previews, React alone has limitations because it's a CSR framework.

for example options for better SEO without switching to Next.js is using pre-rendering with tools like Rendertron which serves static HTML snapshots to crawlers while keeping our app CSR for users.

[KaranNegi20Feb]

Hey, based on what you’ve described, Next.js sounds like the perfect fit! It’s super flexible and handles both static and dynamic content like a champ. You get server-side rendering (SSR) for those real-time GraphQL queries, static site generation (SSG) for pages that don’t need frequent updates, and some awesome performance perks—think automatic code-splitting, image optimization, and snappy load times. Plus, it pre-renders pages, which is a big win for SEO. React on its own, with its client-side rendering (CSR), just doesn’t stack up as well for search engine rankings. So, if NEST needs real-time data, solid SEO, and room to scale, Next.js is definitely the better pick over plain React.

[Naveen-Pal]

My views are:

Astro is generally used for static sites, but in our case, we are dealing with real-time data. We may mix framework like React and Vue as needed.
Gatsby: Have good customization through plugin ecosystem.

For large sites with frequent content updates, Gatsby's build times can become lengthy, making it less ideal for such scenarios.

-- Copilot

Nest.js - Agreed with @KaranNegi20Feb
Remix: As far as searched, it will work well with Nest as it emphasizes performance, reliability, and leverages server-side rendering.
Its demerits are that it has a smaller community and is still developing features.

[Rajgupta36]

my point of view is that we are migrating for better performance and SEO optimization. Based on my research, both Astro and Next.js are good options. Astro is faster compared to Next.js because it ships zero JavaScript by default, making it ideal for serving static content. As seen in their showcase projects, most examples are static websites.

However, Next.js offers an advantage when managing large and dynamic websites. It supports server-side rendering (SSR), which is useful if we need to serve content via backend APIs. Additionally, Next.js provides features like next/image and next/link, which optimize image size and quality based on page requirements, enhancing performance and SEO.

That's my perspective.

[rishyym0927]

Hey @arkid15r, I think we should go with Next.js since it offers more flexibility and is a full-stack framework, meaning we’ll need to write less backend code. It’s also performance-optimized, so we don’t have to worry much about that. Plus, it works well for SEO, and most people have had a great experience with it.