Lit.js migration roadmap

[clemgbld]

Today:

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.

(Easy) components to migrate (most of the code is html element creation):

• [x] legend component (see https://github.com/NodeSecure/cli/pull/546)
• [x] bundlephobia component (see https://github.com/NodeSecure/cli/issues/547)
• [x] expandable component (see https://github.com/NodeSecure/cli/pull/551)
• [x] file-box component
• [x] gauge component
• [x] report component (easy but is blocked by the migration of the popup component)
• [x] files component (blocked by expandable)
• [x] licenses component (easy but blocked by fill-box)
• [x] vulnerabilities

(Medium) Tougher components to migrate (because of their interaction with other components)

• [x] popup component
• [x] locker component
• [x] scripts component

(Hard) hard component to migrate (because of the inherent complexity of the component itself and its interaction with other components)

• [ ] navigation component
• [ ] wiki component
• [ ] settings component
• [ ] search component
• [x] maintainer component
• [ ] package (container)
  • [ ] header
  • [ ] pannels/overview
  • [ ] pannels/scorecard
  • [ ] pannels/warnings
  • [ ] code-fetcher

(Hardest)

• [ ] searchbar (probably more rewrite than a migration see https://github.com/NodeSecure/cli/issues/423)
• [ ] home

(Icon migration)

setup a new icon system (see https://github.com/NodeSecure/cli/issues/556)

[!NOTE] The estimated migration difficulty for each component is provided as a general indication and may prove to be easier or more complex in practice than stated