Skip to content

Web Components

Making & using web components.

Web Components Features

Once again we see declarative solutions prevailing, with declarative custom elements topping the sentiment chart.
Which of the following web component features have you used?

Group by:

Sort by:

1
Web Components
51.3%
36%
11.2%
2
Web Components
46.5%
38%
14.7%
3
Web Components
41.7%
43.4%
14%
4
Web Components
15.1%
32.8%
51.8%
5
Web Components
11.8%
32.3%
55.6%
6
Web Components
8.5%
15.4%
75.9%
7
Web Components
5.3%
21.4%
72.9%

Experience

  • <span aria-hidden="true">🤓</span> Used it: Respondents who have used an item.
  • <span aria-hidden="true">👀</span> Heard of it: Respondents who have heard about an item, but haven't used it.
  • <span aria-hidden="true">🤷</span> 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.

Web Components Pain Points

We know that extending built-in elements is a long requested feature, and these results validate it, as it is the top concrete pain point topic here (after the more abstract ones around complexity, reliance on JS, and accessibility).
What are your biggest pain points around creating or using web components?
(freeform question)
Multiple
Top pain point topics overall.

View:

Items that are not one of “limitations”
0%
20%
40%
60%
80%
100%
01
Cognitive overload
4
02
2
03
Web Components styling & theming
2
04
Web Components syntax issues
05
Competition from frameworks
06
Poor developer experience
07
1
08
Reliance on JavaScript
09
Framework compatibility
1
10
Education
1
11
Reactivity
1
12
Browser vendor issues
1
13
Loading & packaging
14
SSR
15
Ecosystem issues
1
16
Authoring model
17
Custom element attributes and props
1
18
Adoption & momentum
19
Registries & naming
20
Web Components extending built-in elements
21
End-user experience
1
22
Accessibility
23
Form-Associated Custom Elements
24
Content
1
25
0%
20%
40%
60%
80%
100%

Recommended Resources

Vanilla JS: You Might Not Need a Framework
Maximiliano Firtman
Software Engineer & Educator

Vanilla JS: You Might Not Need a Framework

See how you can build rich web apps and websites without depending on libraries or frameworks, using only the core JavaScript language.
Thanks to our partners for supporting us! Learn more.