npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@embedworkflow/react

v0.2.0

Published

React components for embedding EmbedWorkflow UI.

Readme

@embedworkflow/react

React components for embedding EmbedWorkflow UI into your own app. Thin wrappers over the EWF runtime (loaded from the CDN) — React and the runtime are not bundled.

Install

npm i @embedworkflow/react

react >= 17 is a peer dependency.

Prerequisites

The EWF loader script must be on the page, and auth established once (sign the JWT server-side). Prefer the exported load() over window.EWF.load — it retries through the loader's brief startup gap so a fast call isn't dropped:

import { load } from "@embedworkflow/react";
load(pkToken, { jwt });

See the embedding guide. Components wait for the runtime internally — no readiness code needed.

Components

One component per embeddable renderer:

| Component | Renders | Key props | | --- | --- | --- | | EwfApp | The full workflow builder / app | basePath | | EwfSettingsForm | A workflow's client settings form | workflowId | workflowKey | | EwfConnections | The managed connections UI | — | | EwfField | A single field from a workflow's form | workflowId|workflowKey, fieldId, defaultValue; emits onChange |

All accept className and style.

EwfField

import { EwfField } from "@embedworkflow/react";

<EwfField
  workflowId="wf_123"        // or workflowKey="onboarding"
  fieldId="slack"            // field name or id in the workflow's form
  onChange={(e) => console.log(e.value, e.option)}
/>;

onChange receives EwfChangeDetail — { fieldId, value, option? }.

EwfApp

<EwfApp basePath="workflows" style={{ height: "calc(100vh - 60px)" }} />
  • basePath has no leading slash (the renderer adds it).
  • Give it an explicit, non-percentage height (a % height collapses to 0).
  • The app does client-side routing under basePath, so add a catch-all route in your router for /{basePath}/* (e.g. React Router path="/workflows/*").

EwfEmbed — escape hatch / forward-compat

Embed any renderer by name, including ones this package version has no typed component for yet. It works for whatever the loaded CDN runtime supports, so a renderer newly shipped in the SDK is usable without upgrading this package.

import { EwfEmbed } from "@embedworkflow/react";

<EwfEmbed name="reports" data={{ "base-path": "reports" }} onChange={...} />;
// → <div class="EWF__reports" data-base-path="reports">
  • name — renderer class suffix ("reports" → EWF__reports).
  • data — keys map to data-<key>.

Prefer the named components when they exist; reach for EwfEmbed for dynamic names or renderers the package predates. (The named components are built on top of EwfEmbed via createEmbed, also exported if you want a typed façade.)

License

MIT