跳到内容

Web 组件

制作和使用 Web 组件

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?

通过...分组:

根据此项排序:

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

经验

  • <span aria-hidden="true">🤓</span> 用过: 使用过此项目的受访者。
  • <span aria-hidden="true">👀</span> 有听说过: 听说过此项目,但没有使用过此项目的受访者。
  • <span aria-hidden="true">🤷</span> 没听说过: 从未听说过此项目的受访者。

情绪(态度)

  • 积极: 有兴趣了解此技术,或者愿意再次使用它的受访者
  • 中立: 未对此技术发表看法的受访者
  • 消极: 对此技术不感兴趣,或者使用此技术有糟糕体验的受访者

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?
(自由提问)
多选
总体上最主要的痛点主题。

视图:

不为“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%
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.
感谢合作伙伴对我们的支持! 了解更多。