Next.js Reviews

1. Kurslog team

   · Working at Kurslog · 5 months ago

   Next.js has become the de-facto standard for our frontend engineering team when building modern web applications. The Server-Side Rendering (SSR) and Static Site Generation (SSG) are absolutely essential for our product's SEO strategy and fast indexing.

   The transition to the App Router initially required a paradigm shift for our developers, but it ultimately made our architecture much more scalable. We love that the framework handles the heavy lifting—image optimization, code splitting, and routing—allowing our team to focus purely on business logic. It provides a phenomenal Developer Experience that keeps our deployment cycles fast and predictable.

   Competitors: Remix, Nuxt.js, Svelte, Vite

   Pros:    Out-of-the-box ssr and ssg for excellent seo|Superb developer experience with zero-config setup|Built-in optimizations for images, fonts, and scripts|Highly scalable routing via the app router

   Cons:    The app router requires a paradigm shift and learning curve for the team at first|Caching strategies can be tricky to master and debug across a large, dynamic app

node-http-proxy Reviews

Next.js mentions (1145)

• Building a Multilingual Shop with Next.js

  In this article, we’ll look at how to approach these problems in a Next.js application using the App Router. Rather than focusing on the basics of translating strings, we’ll focus on the technical decisions behind the implementation: how the language is detected, how it’s propagated through the application, how translations are loaded on the server and client, and how localized routes are handled. - Source: dev.to / 5 days ago

• What Browserslist Actually Does in Next.js

  We set up three near-identical Next.js 16 projects to answer a simple question: if you set a browserslist target in package.json, does the build change to match it? We tested three targets (ie 11, chrome 116, about 3 years old, and chrome 139, about 1 year old) and compared the compiled output byte by byte. - Source: dev.to / 2 days ago

• We’re all full stack now

  Blurring of the lines. React Server Components (RSC) and associated frameworks such as NextJS involve code executing on both server and client, while HTMX focuses on markup and emphasises use of full-stack/backend templating engines to generate code targetting the browser. Working with these new tools blurs the distinction between the front end and back end skill set. - Source: dev.to / 14 days ago

• The Past Keeps Changing

  What replaced the laptop, before we get to the schema: Health Auto Export now posts straight to a Vercel function on a daily schedule, a scheduled job pulls lifting history from Liftosaur, and both land in TimescaleDB on Tiger Cloud. No files, no iCloud, no Mac. A Next.js app reads it and tells me whether I hit protein, which is a separate post. - Source: dev.to / 16 days ago

• Getting Started with Shadcn Checkbox in React & Next.js

  This guide shows you how to install and use the Shadcn Checkbox component in React and Next.js. - Source: dev.to / about 2 months ago

node-http-proxy mentions (10)

• Is there a way to accept incoming http but outgoing must be https?

  Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper. Source: over 3 years ago

• HTTPS proxy setup with response modification

  I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds... Source: about 4 years ago

• what's the stack for this application?

  What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward. Source: about 4 years ago

• GraphQL is now available on Supabase

  There's several ways to have a blog path contain a separate setup from the marketing/product routes. One is to run a reverse proxy on the root domain to pull in separate routes for various services. https://github.com/http-party/node-http-proxy You can do rewrites at the server level for the root domain Or if the app on the root domain can do the routing for you (have done this before with a Rails app). - Source: Hacker News / over 4 years ago

• Creating and deploying a tiny proxy server on Vercel in 10 minutes

  Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response. - Source: dev.to / over 4 years ago