Lit.js migration roadmap
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 385
- Forks
- 52
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
Context
Today, the project consists of a set of pseudo-components fully managed in Vanilla JavaScript without any external libraries.
Goal
Implement Lit.js to maintain a primarily Vanilla approach while structuring our components more effectively.
Utility modules (styles, view-models, constants, barrel exports, core helpers) are excluded from this list — they do not need to be migrated.
Standalone components
- bundlephobia
- expandable
- file-box
- gauge
- icon
- items-list
- legend
- locked-navigation
- locker
- network-breadcrumb
- npm-avatar
- popup
- root-selector
- navigation
- wiki
Search command
Package panel
- package (container)
- header
- pannels/files
- pannels/licenses
- pannels/scripts
- pannels/vulnerabilities
- pannels/overview
- pannels/scorecard
- pannels/warnings
- pannels/warnings/code-fetcher
Views
Contributor guide
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 comparing an unchecked component such as public/components/navigation/navigation.js with the checked component links in the roadmap. Review the target component and its surrounding imports before choosing one migration unit. Done means the selected component is migrated consistently and its checklist entry can be marked complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100