使用 Lit 替代原生的 Web Components 提高可维护性
Open
Nobody has claimed this yet.
enhancement
good first issue
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
如题
随着组件数量和复杂度的提高，对于响应式组件和可复用性需求做实现的成本会不断提高。
因此，引入 Lit 和 lit-html 作为构建 Web Components 组件库显然更符合长远需求。依托其生态也可以获得更好的性能和开发效率。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the existing TypeScript Web Components implementation and the project's component build and test setup; the issue does not identify specific files or tests. Define the migration scope and acceptance criteria for responsive, reusable components before changing code. Done means the agreed component library uses Lit and lit-html with verified behavior and maintainability.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100