رفتن مستقیم به محتوا

Web Components

Despite JavaScript frameworks being used more widely than ever, there is still a need for native solutions. Yet Web Components currently fall short of addressing developer pain points effectively, with Web Components APIs and especially Shadow DOM dominating the top 10 of worst experiences across all HTML-related technologies.

This indicates that there is still significant work to be done before they can truly enhance HTML's extensibility and become a strong alternative to framework components. However, the ongoing activity in this area leaves me hopeful.

Web Components Experience & Sentiment

Group by:

Sort by:

1

42.9%
36.2%
20.7%
13,553
2

37.7%
28.1%
33.9%
13,575
3

32.5%
40.3%
26.9%
13,515
4

27.2%
45.3%
27.2%
13,489
5

22.6%
26.7%
50.4%
13,405

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.

Other Web Component Features

0%
11%
22%
33%
45%
56%
1

<slot> element

4,109
2

2,610
3

CSS ::part() pseudo-element

1,621
4

::slotted() CSS pseudo-element

1,198
5

customElements.get()

1,111
6

1,110
7

customElements.getName()

916
8

customElements.whenDefined()

649
9

🚫 None

6,756
0%
11%
22%
33%
45%
56%
% of question respondents
Which of the following web component features have you used?

Web Components Libraries

0%
18%
36%
55%
73%
91%
1

782
2

3

384
4

232
5

6

135
7

126
8

92
9

10

0%
18%
36%
55%
73%
91%
% of question respondents
Have you used any Web Components libraries?

Using Web Components Pain Points

0%
17%
35%
52%
69%
87%
1

Styling & customization

2

Browser support

3

SSR

4

5

Framework compatibility

Answers matching “Framework compatibility” 77
6

Reliance on JavaScript

7

Framework compatibility

8

Excessive complexity

9

Accessibility

10

Lack of documentation

11

Other Answers

Answers matching “Other Answers” 1,147
0%
17%
35%
52%
69%
87%
% of question respondents
What are your biggest pain points around consuming web components?
Freeform

Making Web Components Pain Points

0%
22%
43%
65%
87%
109%
1

Browser support

2

3

Styling & customization

4

Excessive complexity

5

Reliance on JavaScript

6

Excessive boilerplate

7

SSR

8

Accessibility

9

Excessive verbosity

10

Lack of documentation

11

Other Answers

Answers matching “Other Answers” 1,613
0%
22%
43%
65%
87%
109%
% of question respondents
What are your biggest pain points around making web components?
Freeform

Recommended Resources

Web Components
Dave Rupert
Paravel

Web Components

Learn where to find excellent Web Components to build web apps. You’ll also learn how to create your own custom components using JavaScript and libraries like Lit that will help you make them faster!
Thanks to our partners for supporting us! Learn more.