Vite Reviews

node-http-proxy Reviews

Vite mentions (486)

• History of JavaScript: Browser wars, ECMAScript, Node.js, TypeScript, and React

  This idea led to the creation of Vite (French for "fast" — Ed.). Unlike traditional tools, Vite's development server didn't waste time bundling the entire project at startup. Instead, it sent source files directly to the browser like ES modules do, while using esbuild, a Go-based bundler, to pre-bundle dependencies from node_modules. As a result, the time required to initiate these large projects was reduced to... - Source: dev.to / about 2 months ago

• Dead Code kills silently

  This article presents a bunch of ways how to find unused code, remove it, and configure tools and bundler to prevent dead code in the future. Sections for bundler are based on set of Vite, which under the hood delegates to Rollup in production. - Source: dev.to / 2 months ago

• TanStack Start vs Next.js: The Server Components Showdown That Actually Matters [2026]

  As Tanner Linsley, creator of TanStack, has explained, TanStack Start and its server components are designed to be "additive" to React — not a replacement for its core primitives. They're framework-agnostic and built on Vite. You opt into server-side capabilities when you need them, not because the framework demands it. - Source: dev.to / 4 months ago

• Zero-config Cesium.js in Vite — introducing vite-plugin-cesium-engine

  If you've ever tried to use CesiumJS with Vite, you know the ritual. Before you can render a globe you have to:. - Source: dev.to / 5 months ago

• VoidZero is driving the unification of the Javascript ecosystem

  VoidZero launch week is drawing to a close, and the world of Javascript development has just been given a significant boost. If you follow developments in build tools, you’ll know that fragmentation is rife, and that it’s difficult to stay at the cutting edge without using the best tool for each task. With the latest announcements regarding Vite, Oxlint and Vitest, Evan You team is taking a major step towards the... - Source: dev.to / 6 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