Data Sources
Our compatibility database is built from multiple authoritative sources, cross-referenced for accuracy:
- Official Documentation: Primary source for framework capabilities, runtime requirements, and supported integrations. We monitor documentation updates from Next.js, React, Supabase, Vercel, and dozens of other technologies.
- GitHub Repositories: Issue trackers, discussions, and changelogs reveal real-world compatibility problems and their resolutions.
- Release Notes & Changelogs: Breaking changes, deprecations, and new compatibility requirements are tracked across major releases.
- Developer Community: Stack Overflow, Reddit, Discord servers, and developer forums surface edge cases and workarounds.
- Direct Testing: For critical compatibility rules, we verify behavior in isolated test environments.
Research Process
Each technology in our database goes through a structured research process:
1. Initial Research
When adding a new technology, we conduct comprehensive research across dozens of sources. This includes official documentation, GitHub activity, community discussions, and comparative analyses with similar technologies.
2. Compatibility Mapping
We identify all meaningful technology pairs (e.g., Next.js + Prisma, Supabase + Vercel Edge) and document their compatibility status:
- Compatible: Technologies work together without issues.
- Partial: Works with limitations, workarounds, or specific configurations.
- Incompatible: Fundamental conflicts prevent combined use.
- Deprecated: Previously worked but no longer supported.
3. Issue Documentation
For partial and incompatible pairs, we document specific known issues, including root causes, affected versions, and available workarounds. Each issue links to authoritative sources for verification.
4. Periodic Updates
The web development ecosystem moves fast. We periodically re-research technologies to capture:
- New compatibility issues introduced in recent versions
- Previously incompatible pairs that now work
- Deprecated technologies and migration paths
- New workarounds discovered by the community
Data Categories
Our database covers six main technology categories:
- Frameworks: Next.js, Nuxt, SvelteKit, Remix, Astro, Hono, and more.
- Databases: PostgreSQL, MongoDB, Supabase, Firebase, Turso, PlanetScale, and more.
- Hosting Platforms: Vercel, Netlify, Cloudflare, Railway, Render, Coolify, and more.
- Authentication: Clerk, Auth0, NextAuth, Supabase Auth, Firebase Auth, and more.
- AI Coding Tools: Lovable, Bolt.new, Cursor, Claude Code, Windsurf, Replit, and more.
- Utility Tools: ORMs, validation libraries, payment processors, and developer utilities.
Quality Standards
We hold ourselves to high standards for data quality:
- Source Attribution: Compatibility rules cite their sources when based on specific documentation or issues.
- Version Specificity: We note which versions are affected when compatibility varies across releases.
- Workaround Verification: Suggested workarounds are validated before inclusion.
- Regular Audits: We periodically review existing rules to ensure continued accuracy.
Limitations
We believe in being transparent about what we can and cannot guarantee:
- Not Exhaustive: We cannot cover every possible technology combination. We prioritize popular and emerging technologies.
- Point-in-Time: Compatibility can change with new releases. We update our data regularly but cannot guarantee real-time accuracy.
- General Guidance: Our rules reflect common scenarios. Your specific use case may have unique requirements.
- No Substitute for Testing: DevRadar helps you avoid obvious pitfalls, but thorough testing of your specific stack is always recommended.
Report an Issue
Found an inaccurate compatibility rule? Have data that contradicts our findings? We want to know.
Please email us at hey@devradar.dev with:
- The technologies involved
- What our data says vs. what you observed
- Links to supporting documentation or reproductions
We review all reports and update our database accordingly.