跳至內容

State of JavaScript 2023

Meta-Frameworks

Frameworks focused on rendering and serving your application

Meta-Frameworks Ratios Over Time

Next.js
Nuxt
Gatsby
Remix
Astro
Eleventy
SvelteKit
Docusaurus
SolidStart
Deno Fresh

Mode:

View:

0%
20%
40%
60%
80%
100%
2018
2019
2020
2021
2022
2023
0%
20%
40%
60%
80%
100%

Meta-Frameworks Experience & Sentiment

Group by:

Sort by:

1

57.1%
41.8%
20,828
2

23.5%
66.9%
9.7%
20,806
3

23%
63.3%
13.7%
20,774
4

19.1%
59.6%
21.3%
20,777
5

17.8%
64.8%
17.5%
20,755

Experience

  • Used it: Respondents who have used an item.
  • Heard of it: Respondents who have heard about an item, but haven't used it.
  • Never heard of it: Respondents who have never heard about an item.

Sentiment

  • Positive: Respondents who are interested in learning more about a technology; or are willing to use it again.
  • Neutral: Responents who did not indicate any sentiment about a technology.
  • Negative: Respondents who are not interested in learning more about a technology; or have used it and had a negative experience.
“Used” average:17%
“Positive” average:36%
“Negative” average:32%
💡
點選技術的名稱後，可以看到更多細節，並深入檢視相關資料。

Other Meta-Frameworks

0%
8%
16%
24%
32%
41%
1

78
2

38
3

34
4

30
5

27
6

26
7

19
8

14
9

13
10

12
11

Other Answers

174
0%
8%
16%
24%
32%
41%
% 問題回應者
428
2%
We asked members of the JavaScript community to share their “pick of the year”

My 2023 Pick: Pocketbase

My pick of the year is the Pocketbase project - an open-source SQLite powered backend. Its JavaScript SDK gives web developers everything needed to build a serious application, and amazingly, can be deployed as a single binary to any $5 server.
We asked members of the JavaScript community to share their “pick of the year”

Fireship

Google developer expert, data enthusiast, and YouTuber

Meta-Frameworks Happiness

0
1
2
3
4
2022
2023
0
1
2
3
4
平均
20,075
85%
2.4
2
On a scale of 0 (very unhappy) to 4 (very happy), how happy are you with the current state of meta-frameworks?

Meta-Frameworks Pain Points

0%
15%
31%
46%
62%
77%
1

Next.js issues

Answers matching “Next.js issues” 383
2

Excessive complexity

3

Choice overload

4

Lack of documentation

5

Deployment

6

Version changes

7

SSR

8

Speed of change

9

10

Performance

0%
15%
31%
46%
62%
77%
% 問題回應者
2,656
11%
What pain points have you encountered when using meta-frameworks?
(自由填答問題)

推薦資源

Introduction to Next.js 13+, v3
Scott Moss
Superfilter AI

Introduction to Next.js 13+, v3

In this course, you'll learn server-side rendering, static site generation, data fetching, building API endpoints, creating pages, and new features in Next 13+, like using the app router, server and client components, and server actions!
Build an AI-Powered Fullstack Next.js App, v3
Scott Moss
Superfilter AI

Build an AI-Powered Fullstack Next.js App, v3

Create a full-stack AI-powered Journal app from scratch in Next.js. See how all the pieces of Next.js/React fit together: client components, server components, static and dynamic routing, server actions, middleware, and layouts.
感謝贊助我們的伙伴！ 深入瞭解。