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

transactions-mfe

v1.0.2

Published

Microfrontend de Transacciones — publicable como paquete npm y ejecutable como app Next.js standalone

Readme

transactions-mfe

Microfrontend de Transacciones — paquete dual:

  • App Next.js standalone en :3001 para desarrollo aislado del MFE.
  • Librería npm que un host Next.js puede instalar e importar como componentes React (sin iframe, sin multi-zone).

Instalación (como librería en un host)

npm install transactions-mfe

react, react-dom y next son peerDependencies — los provee el host.

Uso desde el host

// app/dashboard/transactions/page.tsx
import { TransactionsListPage } from "transactions-mfe";
import "transactions-mfe/styles.css";

export default function Page() {
  return <TransactionsListPage />;
}

Componentes exportados:

| Export | Origen en el repo | |-----------------------|------------------------------| | TransactionsListPage| app/page.tsx | | NewTransactionPage | app/new/page.tsx | | EditTransactionPage | app/edit/[id]/page.tsx | | Sidebar | app/components/Sidebar.tsx | | EmbeddedShell | app/components/EmbeddedShell.tsx |

Variables de entorno requeridas en el host

NEXT_PUBLIC_API_URL=http://localhost:3000

El MFE llama a ${NEXT_PUBLIC_API_URL}/api/transactions.


Desarrollo local (modo standalone)

npm install
npm run dev      # levanta el MFE en http://localhost:3001

Sigue funcionando como app Next.js completa, con sidebar/topbar propios.


Empaquetado y publicación

npm run build:lib     # tsup → /dist (ESM + CJS + d.ts) + styles.css
npm run pack:dry      # ver qué entraría al tarball
npm publish           # publica al registry configurado

prepublishOnly corre build:lib automáticamente, así que npm publish nunca sube código sin compilar.

Estructura del tarball publicado

transactions-mfe-1.0.0.tgz
├── dist/
│   ├── index.js        ESM
│   ├── index.cjs       CommonJS
│   ├── index.d.ts      tipos
│   └── styles.css      Tailwind compilado
├── package.json
├── README.md
└── LICENSE