Integrating Shoelace Web Components into Your Design System
Writing UI components from scratch is expensive. Every button, input, or dialog requires design, markup, accessibility testing, and cross-browser validation. If your project spans multiple frameworks (React, Vue, Angular), effort scales linearly. Shoelace (now Web Awesome) solves this: a ready library of 50+ Web Components, framework-agnostic. It customizes via CSS variables and parts, supports dark theme, and meets WCAG standards.
Our team has implemented Shoelace in 30+ projects — from startups to enterprise systems. Below we break down how integrating Shoelace speeds up development by 3–5x and why it beats custom development.
Why Shoelace Cuts Development Time by 3–5x
Let's compare: writing a single 'Select' component from scratch takes 3–5 days including testing and a11y. Shoelace gives a ready <sl-select> with keyboard support, ARIA attributes, and dark theme. You only need to override brand colors via CSS variables. Result: 2–4 days for the entire library instead of 2–3 months for your own.
Comparison of costs:
| Characteristic |
Custom components |
Shoelace |
| Development time (50 components) |
2–3 months |
2–4 days |
| Number of components |
10–20 |
50+ |
| Accessibility (a11y) |
Requires separate work |
Built-in (WCAG 2.1 AA) |
| Theme support |
Need to implement |
Built-in via CSS variables |
| Updates and bugfixes |
Self-managed |
Community and authors |
| Annual cost of ownership |
High |
$0 (free license) |
Development savings exceed 60% already on the first project. Migrating to Shoelace pays off through reduced development time and lower maintenance costs.
How to Integrate Shoelace with React
Integrating Shoelace with React requires minimal code:
- Install the package:
npm install @shoelace-style/shoelace
- Register the needed components in a separate file (e.g.,
shoelace-setup.ts). We use cherry-pick imports with tree-shaking to reduce the bundle by 10x compared to full import.
- Import the theme and configure the asset path.
Example of a typed React modal component:
import { useRef } from 'react'
import type SlDialog from '@shoelace-style/shoelace/dist/components/dialog/dialog.js'
import '../shoelace-setup'
export function ContactModal() {
const dialogRef = useRef<SlDialog>(null)
const openDialog = () => dialogRef.current?.show()
const closeDialog = () => dialogRef.current?.hide()
const handleSubmit = async (e: React.FormEvent) => {
e.preventDefault()
// обработка формы
closeDialog()
}
return (
<>
<sl-button variant="primary" onClick={openDialog}>
Написать нам
</sl-button>
<sl-dialog ref={dialogRef} label="Контактная форма">
<form onSubmit={handleSubmit}>
<sl-input label="Имя" required placeholder="Иван Иванов" style={{ marginBottom: '16px' }} />
<sl-input label="Email" type="email" required placeholder="[email protected]" style={{ marginBottom: '16px' }} />
<sl-textarea label="Сообщение" rows={4} required />
</form>
<sl-button slot="footer" variant="default" onClick={closeDialog}>Отмена</sl-button>
<sl-button slot="footer" variant="primary" type="submit">Отправить</sl-button>
</sl-dialog>
</>
)
}
For JSX typing, add module declarations for all components. These can be generated via custom-elements.json shipped with the library.
Customization for Your Brand
Shoelace is built on design tokens. Override colors, fonts, radii, and other CSS variables — and the whole library changes appearance. For precise styling, use CSS parts (::part()). We also prepare a styling guide with examples for your team.
/* Global tokens */
:root {
--sl-color-primary-600: hsl(262, 75%, 45%);
--sl-font-sans: 'Inter', system-ui, sans-serif;
--sl-border-radius-medium: 8px;
--sl-transition-medium: 200ms ease;
}
/* Single button styling */
sl-button::part(base) {
font-weight: 700;
text-transform: uppercase;
letter-spacing: 0.02em;
}
sl-button[variant="primary"]::part(base) {
background: linear-gradient(135deg, #7000ff, #b600ff);
border: none;
}
Dark Theme in 5 Minutes
Theme switching is implemented by adding the sl-theme-dark or sl-theme-light class to <html>. We connect the saved theme from localStorage and respect prefers-color-scheme. The entire initialization code is 10 lines.
Learn more about theming in the official Shoelace documentation: https://shoelace.style/getting-started/themes
Implementation Process
| Stage |
Duration |
| Analysis of design system and requirements |
1–2 days |
| Shoelace setup and cherry-pick imports |
1 day |
| Brand customization (CSS variables, parts) |
1–2 days |
| React/Vue integration and testing |
1–2 days |
| Documentation and team training |
1 day |
| Support and warranty |
within a month |
What's Included
- Shoelace setup with cherry-pick imports (tree-shaking) — bundle size reduced 10x.
- Customization of all components to your design system.
- Integration with your framework (React, Vue, Angular).
- Dark and light theme support.
- Usage and customization documentation.
- Team training (2–3 hours).
- Compatibility guarantee and free updates for one month.
Typical Mistakes and How to Avoid Them
- Importing the entire library instead of cherry-pick — increases bundle 10x.
- Ignoring CSS variables — styling via parts without tokens leads to code duplication.
- Missing TypeScript types — without declarations, components won't work in JSX.
We have prepared an integration checklist that we will share with you after the audit.
Request a consultation — we'll analyze your design system and propose a Shoelace implementation plan with cost savings calculation. Get a free audit of your current UI and an estimate of development time reduction. Save resources — use ready-made components.
Frontend Development with React: From Audit to Production
Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.
Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.
Why is Next.js the Standard Choice for SEO?
React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.
But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.
How Does TypeScript Prevent Bugs in Production?
TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.
Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.
Vue 3 + Nuxt 3 — An Alternative SSR Stack
Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.
Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.
Performance: Metrics and Tools
Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.
Dynamic imports for heavy components:
const RichEditor = dynamic(() => import('@/components/RichEditor'), {
ssr: false,
loading: () => <EditorSkeleton />,
});
Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.
Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.
State Management: Without Overengineering
For most applications, it's enough to have:
-
React Query / TanStack Query — for server state (API data, caching, invalidation)
-
Zustand — for global client state (lightweight, no Redux boilerplate)
-
React Hook Form — for forms
Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.
How to Choose the Right CSS and Design System?
Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.
React DevTools Profiler — the official tool from the React team.
Testing
| Level |
Tool |
What We Test |
| Unit |
Vitest |
Utilities, hooks, pure functions |
| Component |
Testing Library |
Render, interactions |
| E2E |
Playwright |
Critical user flows |
| Visual |
Chromatic (Storybook) |
UI regression |
E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.
What's Included in the Scope (Deliverables)
Every frontend project we deliver includes:
-
Source code in Git with full commit history and branching strategy
-
Architecture document — component tree, data flow, routing decisions
-
Component documentation – Storybook with stories for all reusable components
-
CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
-
Access to staging environment during development and after launch
-
Team training – 2‑3 live walkthrough sessions with your developers
-
3‑month warranty on any bugs found in production
-
Performance report – LCP, TTI, TTFB, bundle size before/after
We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.
Estimates and Scope
| Task |
Timeline |
| SPA (dashboard, CRM interface) |
8–16 weeks |
| Next.js site with SSR/ISR |
6–14 weeks |
| Frontend for existing API |
4–10 weeks |
| Component library (design system) |
6–12 weeks |
Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.
What Does a Typical Performance Audit Reveal?
A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.
Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.
We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.
What Stack to Choose for Frontend Development with React?
We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.
Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.
