New:Introducing Socket Scanning for VS Code Marketplace Extensions.Learn more →
Get Started
s

speedsharma.ai

npm

1.45K

total weekly downloads

Packages

Current Co-maintainers

Former Co-maintainers

19 packages

@mfeflow/analytics

Analytics for micro-frontends behind one provider interface: typed events, a tracker that stamps mfe_name, Consent Mode v2, and a Google Tag Manager provider.

@mfeflow/bundler-shared

Bundler-agnostic Module Federation 2.0 settings shared by the mfeflow presets (@mfeflow/rsbuild and @mfeflow/vite): singletons, federation options, head scripts and runtime config.

@mfeflow/contracts

Types, validators and JSON Schemas for mfeflow: mfeflow.app.json ownership manifests, mfeflow.json project state, and the remote registry (entries and index).

@mfeflow/core

The engine behind the mfeflow CLI: project model, change plans with diffs, atomic apply with rollback, and feature resolution.

@mfeflow/event-bus

A typed event bus for micro-frontends on one page: versioned event names, payload types merged by each remote, optional validation, replay for late subscribers, and a React hook.

@mfeflow/http

A small fetch client over @mfeflow/url-factory endpoints: async bearer tokens, timeouts, retries with backoff for idempotent methods only, typed JSON, and errors that carry the status and body but no URL.

@mfeflow/i18n

i18n for micro-frontends: one i18next instance owned by the shell, each remote lazy-loads its own namespace from its own deploy, RTL and persisted language.

@mfeflow/oxlint-config

Type-aware oxlint config for mfeflow micro-frontends: TypeScript 7 rules via oxlint-tsgolint, React, hooks and accessibility.

@mfeflow/registry

The mfeflow remote registry: a static index with gates and rollback, and a self-hosted server with scoped tokens, an audit log and a kill switch.

@mfeflow/route-factory

Typed links between micro-frontends: each remote defines its routes once, and a link to any of them is checked for missing params, missing search params and unknown routes at compile time.

@mfeflow/rsbuild

Rsbuild presets for Module Federation 2.0 micro-frontends: createShellConfig and createRemoteConfig with shared singletons, external runtime, manifests, types and error reporting set up.

@mfeflow/runtime

Runtime for mfeflow micro-frontends: remotes from a registry index, RemoteBoundary with timeout and fallback, error reporting, singleton checks, composeProviders.

@mfeflow/storage

Browser storage namespaced per micro-frontend, SSR-safe, with cross-tab sync and a React hook.

@mfeflow/telemetry

Telemetry for micro-frontends behind one provider interface: a tracer per remote tagged with mfe.name, error reporting wired to remote failures, and an OpenTelemetry web provider loaded after first render.

@mfeflow/testing

Test helpers for mfeflow micro-frontends: renderWithPlatform wraps components in the same providers the shell uses; resetPlatform clears storage, i18n, theme and reports between tests.

@mfeflow/theme

Design tokens as CSS variables for micro-frontends: the shell sets the theme once, every remote inherits it. ThemeProvider, useTheme, persisted choice, no-flash script.

@mfeflow/tsconfig

Strict TypeScript 7 presets for mfeflow micro-frontends: base, react-app, react-library and node.

@mfeflow/url-factory

Typed API URLs for micro-frontends: path params are checked from the template at compile time, base URLs come from runtime config, so one build runs in every environment.

@mfeflow/vite

Vite presets for Module Federation 2.0 micro-frontends: createShellConfig and createRemoteConfig with shared singletons, manifests, types and error reporting set up, on @module-federation/vite.