Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe State of JavaScript 2024 survey points to a mixed picture: respondents reported broad use of newer language features and enthusiasm for tools such as Vite and Vitest, while also identifying architecture, state management, and dependency management as persistent workflow pain points. These are results from a self-selected survey—not a census of all JavaScript developers—and should be read as a snapshot of participating developers’ experiences.
What the State of JavaScript 2024 survey can tell you
Devographics collected responses from November 13 through December 10, 2024, and published results on December 16. The survey received 14,015 responses. Its stated aim is to identify emerging trends that can help developers make technology choices, with an emphasis on what may be coming rather than a complete accounting of what is already popular. Devographics’ 2024 survey overview describes the collection period, approach, and limitations.
Anyone could participate online; there was no screening or selection process. Respondents came largely from people reached through earlier surveys, mailing lists, and social media, and the organizers note that a technology’s own audience may be more likely to respond. Questions were optional. That makes the results useful as a view into the participating community, but not a representative estimate of usage across every developer, company, country, or codebase.
Figures below are the 2024 results as reported in Matthew Tyson’s January 22, 2025 InfoWorld analysis. “Used and liked,” “would use again,” positive sentiment, and retention are distinct measures; they should not be treated as interchangeable popularity scores.
#1 Best Overall
What AI coding tools did respondents report using?
Fourteen percent of respondents said they used no AI code generator. For named assistants, the article reports the following shares:
| Assistant | Share reported |
|---|---|
| ChatGPT | 67% |
| GitHub Copilot | 48% |
| Claude | 23% |
| Gemini | 14% |
The categories are not established as mutually exclusive, so these percentages should not be added together or interpreted as market shares. They describe reported use among survey respondents, not adoption across the entire JavaScript developer population.
What did developers find painful or want added to JavaScript?
Respondents identified both language-level gaps and broader workflow problems. The distinction matters: some asks concern the language itself, while others describe the work of building and maintaining applications.
Rank #2
Language features and capabilities
| Feature or capability | Share identifying it |
|---|---|
| A standard library | 43% |
| Signals | 39% |
| Lack of static types as a pain point | 32% |
| A pipe operator | 23% |
Workflow challenges
| Workflow pain point | Share identifying it |
|---|---|
| Architecture | 35% |
| State management | 31% |
| Dependency management | 29% |
| Build tools | 28% |
| Performance | 24% |
The results suggest that dissatisfaction is not limited to JavaScript syntax or type systems: respondents also pointed to decisions and maintenance work that shape an application’s architecture and toolchain.
Which newer JavaScript features had respondents used?
The InfoWorld account reports these feature-use figures among survey participants:
| Feature | Reported use |
|---|---|
| Nullish coalescing | 85% |
Promise.allSettled() |
47% |
Promise.any() |
43% |
Array.toSorted() |
40% |
Object.groupBy() |
33% |
Use of newer Set methods was less widespread: 76% had yet to use the methods covered by the article. Among respondents using them, reported use was 16% for Set.union() and 15% each for Set.intersection() and Set.difference().
Survey use does not establish that a feature is supported in every runtime or appropriate for a particular project. Check the environments your application must support before relying on newer language features.
Which frontend frameworks and meta-frameworks stood out?
Framework results use different sentiment measures, so the reported figures below are best read individually rather than as a direct ranking.
Free tools Windows power users keep installed
One-click scans. No signup required.
Frontend frameworks
- Svelte: 88% said they would use it again.
- Vue: 87% said they would use it again.
- React: 43% were in the “used it and liked it” category, while 24% said they had used it with no sentiment.
- Angular: The article describes positive sentiment and usage recovering in its trend view, without supplying a single comparable score in the cited summary.
The official State of JavaScript 2024 introduction notes that its three leading frontend frameworks had all launched more than a decade earlier. That context helps explain why the results also give considerable attention to tools that support development around established frameworks.
Rank #4
Meta-frameworks
The article describes overall meta-framework usage as increasing while sentiment declined. It reports 94% “would use it again” for Astro and 90% for SvelteKit. Next.js sentiment was 68%, down from prior years, while its usage was steady compared with the preceding year. These are not identical measures, and the trend claims concern survey respondents rather than all users of those frameworks.
Which JavaScript tools received strong sentiment?
The article highlights positive responses for build, package, and testing tools, using the measure stated for each rather than a single common score.
Build and package tools
| Tool | Reported measure |
|---|---|
| Vite | 51% said they had used it and felt positive; retention was 98%. |
| pnpm | 93% positive sentiment. |
| esbuild | 91% approval. |
| SWC | 86% positivity. |
Testing tools
| Tool | Reported measure |
|---|---|
| Vitest | 98% retention. |
| Playwright | 94% said they would use it again. |
| Testing Library | 91% positive sentiment. |
Because the measures and their wording differ, these numbers do not establish a head-to-head ranking. They do show that the survey’s tooling results include strong reported sentiment alongside framework findings.
Which hosting services did respondents report using?
The article lists these hosting-service figures for survey respondents:
| Service | Reported share |
|---|---|
| AWS | 44% |
| Vercel | 40% |
| GitHub Pages | 38% |
| Netlify | 38% |
| Cloudflare | 21% |
| Heroku | 19% |
These are respondent reports, not an exhaustive list of hosting providers or a measure of market share.
How should you use these results when choosing tools?
- Match the metric to your question. Usage tells you what participants say they used; retention and “would use again” express different kinds of continued interest; positive sentiment captures a separate judgment.
- Check your own project constraints. Survey feature use does not settle runtime compatibility, framework fit, team experience, or operational needs.
- Use the figures as signals, not prescriptions. Strong sentiment can identify tools worth evaluating, but it cannot replace a decision based on your application and team.
- Compare like with like. Trend comparisons are most meaningful when editions use the same question, metric, and coverage; changes in survey design can affect the apparent movement.
The 2024 results are now historical. The official site identifies State of JavaScript 2025 as the latest edition found here: it received 13,002 responses and published results on February 3, 2026. Its 2025 library summary says Vite became the second most-used item while remaining the most-loved. Treat comparisons between editions as changes among respondents, not proof of population-wide shifts.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →
