The @m3e/react package provides idiomatic React bindings for all M3E Web Components. Each component is exposed as its own React module, offering typed props, event mappings, and seamless integration with the React rendering model.
"use client" boundary.
npm i @m3e/react
After installation, import the React module for any component you want to use. Each module wraps the
corresponding @m3e/web module and exposes a familiar React component API.
For example:
import { M3eButton } from "@m3e/react/button";
React modules automatically register their underlying Web Component, so no additional side-effect imports from
@m3e/web are required.
Alternatively, import the @m3e/react/all module to load every React binding at once.
This option is convenient when you want full access to the M3E component suite without managing individual
modules.
import "@m3e/react/all";
Each React module mirrors the structure of its Web Component counterpart, ensuring a consistent mental model across both ecosystems. Use individual modules for tree-shaking and minimal bundles, or the aggregated module for rapid prototyping and full-suite development.
M3E does not provide a dedicated Angular bindings package. Angular provides first-class support for Web Components, allowing all M3E components to be used directly in Angular templates without additional wrappers.
However, Angular requires the CUSTOM_ELEMENTS_SCHEMA to recognize custom elements. Add it to your
module definition:
import { NgModule, CUSTOM_ELEMENTS_SCHEMA } from "@angular/core";
@NgModule({
declarations: [...],
imports: [...],
schemas: [CUSTOM_ELEMENTS_SCHEMA],
})
export class AppModule {}
M3E does not provide a dedicated Vue bindings package. Vue provides first-class support for Web Components, allowing all M3E components to be used directly in Vue templates without additional wrappers.
See Vue and Web Components for more information.