Skip to main content

Graphql-request vs Urql

Side-by-side NPM package comparison

Quick Verdict

Smallest Bundle

Urql

1.9 KB gzipped

Most Popular

Graphql-request

7.3M weekly downloads

Best Maintained

Urql

100/100 maintenance score

Highest Quality

Graphql-request

50/100 quality score

Overall Pick

Urql

Best all-around based on popularity, size, maintenance & quality

graphql-request icon

graphql-request

Very Popular

Version 7.4.0

0
73
Good

Minimal GraphQL client supporting Node and browsers for scripts or simple apps.

Weekly Downloads
7.3M
↓8%
Bundle (gzip)
123.0 KB
Updated
Vulns
0

Health Score Breakdown

Maintenance
60
Popularity
100
Quality
50
Security
100
Stability
70
urql icon

urql

Popular

Version 5.0.1

0
83
Excellent

A highly customizable and versatile GraphQL client for React

Weekly Downloads
600.8K
↓10%
Bundle (gzip)
1.9 KB
Updated
Vulns
0

Health Score Breakdown

Maintenance
100
Popularity
90
Quality
50
Security
100
Stability
70

Choosing between Graphql-request and Urql? Here's a data-driven comparison based on real npm data — downloads, bundle size, health scores, and more — to help you decide which package fits your project best.

Downloads & Popularity

Graphql-request leads with 7.3M weekly downloads — roughly 12.2x more. Urql has 600.8K weekly downloads. Higher download counts generally indicate broader community adoption and a larger ecosystem of tutorials, plugins, and support.

Bundle Size

Urql has the smallest gzipped bundle at 1.9 KB. Graphql-request comes in at 123.0 KB. A smaller bundle size means faster page loads, which improves user experience and Core Web Vitals scores.

Health Score Comparison

Urql has an overall health score of 83/100 (very good), with strong maintenance, security, popularity scores. Graphql-request has an overall health score of 73/100 (good), with strong security, popularity scores. Health scores are calculated from maintenance activity, code quality, security posture, popularity, and stability metrics.

When to Choose Each

Choose Graphql-request if you value large community support, strong security track record. Choose Urql if you value minimal bundle footprint, actively maintained, strong security track record.

Our Verdict

Both Graphql-request and Urql are solid choices for JavaScript development. Urql has the edge in overall health score (83/100), while each package brings unique strengths to the table. Evaluate them based on your project's priorities — whether that's community size, bundle efficiency, or maintenance activity — and choose the one that aligns best with your requirements.

Frequently Asked Questions

Is graphql-request better than urql?
It depends on your needs. Graphql-request has a health score of 73/100 while Urql scores 83/100. Graphql-request has more weekly downloads (7.3M), suggesting broader adoption. Consider your specific requirements — bundle size, community support, and feature set — to decide which is the better fit.
Which has a smaller bundle size, graphql-request or urql?
Urql has the smaller gzipped bundle at 1.9 KB. A smaller bundle means faster load times for your users, which can positively impact SEO and user experience.
How many developers use graphql-request vs urql?
Based on npm download statistics, Graphql-request has approximately 7.3M weekly downloads and Urql has approximately 600.8K weekly downloads. These numbers reflect package installations, not unique developers, but they indicate relative adoption levels.
Which is better maintained, graphql-request or urql?
Urql currently has the higher overall health score at 83/100. Graphql-request has a maintenance score of 60/100 and Urql scores 100/100 on maintenance.

Related Comparisons

Apollo-client vs Urql

The 2026 JavaScript Stack Cheatsheet

One PDF: the best package for every category (ORMs, bundlers, auth, testing, state management). Used by 500+ devs. Free, updated monthly.