Integrate Web Components Across Frameworks: React, Vue, Angular

Implementing Cross-Framework Integration Web Components

We often encounter a situation: a team builds a universal Web Components library, but when integrating into React events are not caught, in Angular there's a schema error, and in SSR components crash. Sound familiar? We solve these problems, guaranteeing compatibility and providing ready-made wrappers for each framework. Our solutions cover React Web Components, Vue Web Components, and Angular Web Components. We can evaluate your project in one day. Our clients save up to 40% integration time (average 35%) thanks to ready-made solutions. Integration packages start from $2,000 per framework, with a 98% satisfaction rate from 50+ completed projects. Typical savings: $800 per framework due to reduced development time.

Problems We Solve

React: Object Passing and Events (Custom Elements React)

For React Web Components, React before version 19 does not pass objects and arrays through attributes — everything is converted to the string [object Object]. Custom DOM events are not automatically caught. Our solution — ref + useEffect to set properties and subscribe to events. React 19 improves support by allowing direct object passing and custom elements React can be enhanced with wrappers like @lit/react. But even in version 19, compatibility checks are required.

Angular: Schema and Two-Way Binding

Angular Web Components require adding CUSTOM_ELEMENTS_SCHEMA to the module or standalone component. For two-way binding (ngModel), a wrapper directive implementing ControlValueAccessor is needed. This adds 1–2 days of development per component.

SSR: Server Knows Nothing About customElements

SSR Web Components break because on the server, there are no global objects customElements, HTMLElement, window. Components that access them in the constructor break SSR. We use lazy loading (dynamic import with { ssr: false }) or Declarative Shadow DOM for server rendering. For example, in Next.js a component can be imported via next/dynamic with the ssr: false option, and in Nuxt via client-only. According to the MDN Web Docs on custom elements, custom elements must be defined with a hyphen in their name.

How We Ensure Compatibility

We use proven patterns and tools for each framework, ensuring seamless web component integration. Example — integrating a Lit element (using Lit elements library) into React via @lit/react:

import { createComponent } from '@lit/react';
import React from 'react';
import { UiButton } from '@company/ui-core';

export const Button = createComponent({
  tagName: 'ui-button',
  elementClass: UiButton,
  react: React,
  events: {
    onUiClick: 'ui-click',
    onUiFocus: 'ui-focus',
    onUiBlur: 'ui-blur',
  },
});

function App() {
  return <Button variant="primary" onUiClick={(e) => console.log(e.detail)}>Click</Button>;
}

This approach provides full typing and correct event handling. For other frameworks we use similar wrappers.

Framework Comparison

Cost-Benefit Analysis Table

Why SSR Is the Main Problem with Web Components

SSR breaks because the server lacks browser APIs. We solve this in two ways: using Declarative Shadow DOM — a specification that allows the server to render Shadow DOM into HTML strings, or dynamic import, loading components only on the client. The choice depends on your requirements for SEO and load time. Additionally, polyfilling the CustomElementsRegistry on the server can help, but it's not recommended due to complexity.

How Vue Simplifies Integration of Vue Web Components

Vue 3 is the most friendly framework: it recognizes custom elements by the presence of a hyphen in the tag. Only configuration of vite.config.js is needed so that Vue does not try to parse these tags as its own components. Object passing works natively via the .prop modifier. This makes integration 2 times faster than in React.

What Is Declarative Shadow DOM?

Declarative Shadow DOM (DSD) is a mechanism for rendering Shadow DOM on the server. The component is output as HTML with <template shadowrootmode="open">. The browser, when loading the page, converts it into a real Shadow DOM. This solves the SSR problem for Web Components but requires browser support and correct implementation. We use DSD for components critical to SEO. As per the Declarative Shadow DOM specification, it integrates seamlessly with server-side rendering pipelines.

Step-by-Step Integration Process

1. Analyze your Web Components library — identify custom element lifecycle hooks, slot usage, form-associated elements, and accessibility (ARIA) integration points.
2. Create Wrappers per framework — using tools like @lit/react, Angular directives, Vue plugins, ensuring property reflection and event mapping.
3. Test in Each Framework — verify object passing, custom event propagation, two-way binding, and SSR behaviour.
4. Implement SSR Handling — choose between Declarative Shadow DOM for critical content or dynamic import for interactive components.
5. Document and Train — provide usage examples, API reference, and a 1–2 hour team training session.

This process reduces integration time by 40% (average 35%) and ensures compatibility across all target frameworks.

What's Included

• Wrappers for React, Vue, Angular, Svelte (on request).
• SSR support via Dynamic import or Declarative Shadow DOM.
• Documentation with examples and API.
• Team training (1–2 hours).
• Technical support for one month.

Why Trust Us with Integration?

Our engineers have 10+ years of experience in UI component library development and cross-framework integration. We have completed 50+ projects with Web Components for clients from Europe and the USA, including over 200 custom elements. We guarantee turnkey compatibility in 3–5 days per framework. Contact us for a consultation — we will assess the complexity of your project. Order integration and get ready-made wrappers turnkey.

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

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

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.