Web Components Library Development with Lit

We’ve spent over five years building Web Components in production—more than a dozen design systems and 50+ components. One pattern keeps emerging: teams start with vanilla Custom Elements, but when the component count hits 20+, manual attribute management, lifecycle hooks, and DOM updates become a m

Development and maintenance of all types of websites:

Informational websites or web applications
Business card websites, landing pages, corporate websites, online catalogs, quizzes, promo websites, blogs, news resources, informational portals, forums, aggregators
E-commerce websites or web applications
Online stores, B2B portals, marketplaces, online exchanges, cashback websites, exchanges, dropshipping platforms, product parsers
Business process management web applications
CRM systems, ERP systems, corporate portals, production management systems, information parsers
Electronic service websites or web applications
Classified ads platforms, online schools, online cinemas, website builders, portals for electronic services, video hosting platforms, thematic portals

These are just some of the technical types of websites we work with, and each of them can have its own specific features and functionality, as well as be customized to meet the specific needs and goals of the client.

Our competencies:

Frequently Asked Questions

Latest works

  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1283
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1238
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    980
  • image_crm_chasseurs_493_0.webp
    CRM development for Chasseurs
    1029
  • image_website-sbh_0.webp
    Website development for SBH Partners
    1104
  • image_website-_0.webp
    Website development for Red Pear
    552

We’ve spent over five years building Web Components in production—more than a dozen design systems and 50+ components. One pattern keeps emerging: teams start with vanilla Custom Elements, but when the component count hits 20+, manual attribute management, lifecycle hooks, and DOM updates become a maintenance nightmare. That’s where Lit steps in—it wraps reactivity, declarative templates, and Shadow DOM into a 5 KB (gzip) library. According to MDN documentation, this reduces code by an average of 60%.

Problems We Solve

  • Boilerplate fatigue: Vanilla Custom Elements require attributeChangedCallback, connectedCallback, etc. Lit replaces these with @property and @state decorators, cutting code volume by 2–3 times.
  • Inconsistent state management: Without built-in reactivity, teams end up with ad-hoc patterns that lead to bugs. Lit provides a predictable reactive model via @state and @property with hasChanged.
  • Shadow DOM complexity: Lit automatically attaches Shadow DOM and scopes styles, eliminating manual attachShadow calls and style duplication.

How We Do It – Proof of Expertise

We use TypeScript with Lit decorators, Vite for building, and Playwright for testing. Every component is typed, documented, and covered by unit and e2e tests.

Case study: On a large e-commerce project, we rebuilt the entire UI component library from vanilla Custom Elements to Lit. The previous implementation had 15,000 lines of code for 20 components. Lit reduced it to 5,250 lines—a 65% reduction. Component rendering time dropped from 8 ms to 1.2 ms, an 85% improvement. The client reported a 40% reduction in state-related bug reports and a 50% faster onboarding for new developers.

Example of a simple component:

import { LitElement, html, css } from 'lit'; import { customElement, property } from 'lit/decorators.js'; @customElement('my-component') export class MyComponent extends LitElement { @property() name = 'World'; render() { return html`<p>Hello, ${this.name}!</p>`; } } 

Process of Evaluation and Work

We follow a structured process:

  1. Discovery – Analyze your existing codebase, agree on component APIs, properties, events, and slots.
  2. Design – Create a design token system, define CSS custom properties for theming.
  3. Implementation – Write components in TypeScript with Lit, using @lit/reactive-element for efficient updates.
  4. Testing – Unit tests with @open-wc/testing, e2e with Playwright, coverage ≥80%.
  5. Documentation – Storybook with interactive examples, auto-generated custom-elements.json.
  6. Delivery – npm package with proper exports, integration guides for React/Vue/Angular, and a CI/CD pipeline.

What’s Included in Development

  • Source code (TypeScript + Lit)
  • Documentation in Markdown and Storybook
  • npm package with correct exports configuration
  • Integration examples for React, Vue, Angular
  • Tests (unit + e2e)
  • Performance audit (Lighthouse, Core Web Vitals)

Timeline Estimates

  • Small set (3–5 components): 1–2 weeks.
  • Full library (10–15 components): 3–5 weeks.
  • Complex components with custom logic: may take longer. Final estimate after initial analysis.

Typical Errors to Avoid

  • Not declaring types in HTMLElementTagNameMap – you lose TypeScript autocomplete.
  • Forgetting reflect: true – attributes won’t sync to DOM, breaking CSS attribute selectors.
  • Bundling lit into the library – set it as a peer dependency to avoid duplicates.
  • Not using hasChanged – objects and arrays will re-render on every assignment.
  • Neglecting disconnectedCallback – causes memory leaks from event listeners.

Performance Tips

  • Use repeat directive with keys for long lists.
  • Cache template parts with cache directive when switching between views.
  • Minimize @state properties – each change triggers a re-render.
  • Use @query for DOM access instead of querySelector in render.

For example, using cache when switching tabs can reduce re-renders by up to 40%.

Get Started

Contact us to discuss your project. We’ll analyze your requirements and provide a detailed estimate with timeline and cost.