Soft.xyz is an independent, data-driven platform that compares 232+ developer tools across 69 categories by real metrics — GitHub activity, npm downloads, actual pricing, DX scores, and community sentiment. Unlike pay-to-play review sites, every ranking on Soft.xyz is based on publicly verifiable data pulled from GitHub, npm, and official pricing pages.

How does Soft.xyz collect data?

Soft.xyz pulls data from public APIs including GitHub (stars, forks, commits, open issues, last commit date), npm (weekly download counts), and official pricing pages. Community sentiment data comes from Reddit and Hacker News mention tracking. All metrics are refreshed weekly and timestamped so you can see exactly when data was last updated.

Is Soft.xyz free to use?

Yes, Soft.xyz is completely free to use. All tool pages, comparisons, benchmarks, DX scores, pricing analysis, and category rankings are available at no cost. For teams that need a deeper analysis, we offer a paid Stack Audit report ($199) that evaluates your entire tech stack with personalized recommendations. An API is also available for programmatic access to our dataset.

How many tools does Soft.xyz track?

Soft.xyz tracks 232 developer tools across 69 categories including databases, hosting, authentication, payments, analytics, CI/CD, monitoring, search, CMS, and more. Each tool page includes real-time GitHub metrics, npm download counts, pricing breakdowns, and side-by-side comparisons with alternatives in the same category.

Home / Migrations / Vite 5 → Vite 6

Vite 5 → Vite 6

easy

Vite 6 is mostly backwards-compatible. The Environment API is opt-in. Main breaking change is dropping Node 16/17.

Estimated: 1-3h · 5 steps

Progress0%

Step 1: Update Node

Vite 6 requires Node 18, 20, or 22. Drop Node 16/17 from CI.

Step 2: Update Vite and plugins

npm install vite@6 @vitejs/plugin-react@latest

Step 3: Switch Sass to modern API

If using Sass, the default API changed to 'modern' in Vite 6.

css: { preprocessorOptions: { scss: { api: 'modern-compiler' } } }

Step 4: Audit ssrLoadModule usage

If you use ssrLoadModule directly, plan migration to the new Environment API. Most apps don't touch this.

Step 5: Run build

✓ Production build succeeds. Dev server starts. No new warnings.