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

@syntropysoft/syntropyfront

v0.4.8

Published

One line of code to capture frontend errors and user actions. Low cost, no per-seat pricing. Saves time, money, and reputation.

Readme


What it does

When something breaks in production, you get what broke and what the user did before it. No giant platform, no per-seat pricing. One import and it starts capturing:

  • Errors — uncaught exceptions and unhandled promise rejections
  • Clicks — on buttons, links, and interactive elements (throttled)
  • HTTPfetch calls (URL, method; no sensitive headers)
  • Breadcrumbs — timeline you can extend with addBreadcrumb()

Optional: PII masking, sampling, offline retry (IndexedDB), and sending to your endpoint or onError callback. That’s it. It’s not a full APM; it’s enough to stop debugging blind.


Why use it

| Who | What they get | |-----|----------------| | Developers | One import, no config. No excuse to ship with zero visibility. | | PM / Tech Lead | Visibility from day one. No long “observability” projects. | | Management | Low cost, no SaaS lock-in. Fewer outages, less firefighting. |

Network: Data is sent only to the endpoint or callback you configure. No third parties, no telemetry. See SECURITY.md.


Quick Start

pnpm add @syntropysoft/syntropyfront

In your app entry (e.g. main.jsx or index.js):

import syntropyFront from '@syntropysoft/syntropyfront';
// Done. Errors and breadcrumbs go to the console by default.

To send to your backend or handle in code:

syntropyFront.configure({
  endpoint: 'https://your-api.com/errors',
  headers: { 'Authorization': 'Bearer YOUR_TOKEN' },
  // optional: samplingRate, batchSize, batchTimeout, usePersistentBuffer, onError
});

Main API

| Method | Description | |--------|-------------| | configure(config) | Set endpoint, headers, sampling, batching, onError, etc. | | addBreadcrumb(category, message, data?) | Add a step to the timeline. | | sendError(error, context?) | Send an error manually (e.g. from catch). | | getBreadcrumbs() | Current breadcrumbs. | | clearBreadcrumbs() | Clear the list. | | getStats() | Queue length, retry status. | | flush() | Send pending data now. | | destroy() | Stop capturing and clean up. |


Optional: PII masking

Sensitive data is masked before leaving the client (emails, tokens, cards, SSN/phone patterns). You can add custom rules via configure({ maskingRules: [...] }). See the full config example below.


Advanced configuration

syntropyFront.configure({
  endpoint: 'https://your-api.com/v1/telemetry',
  headers: { 'Authorization': 'Bearer token', 'X-Environment': 'production' },
  samplingRate: 0.1,           // send 10% of events
  batchSize: 10,
  batchTimeout: 5000,
  usePersistentBuffer: true,   // retry when offline (IndexedDB)
  onError: (payload) => {
    console.warn('Error captured:', payload.type);
    return payload;
  },
  context: { device: true, window: ['url', 'title'], storage: false }
});

Context fields (when enabled): device, window, network, session, ui, performance, storage. See docs in the repo for the full list.


Design (short)

Built to be predictable and safe: SOLID-style modules, pure functions where it matters, PII masking by default. Data goes only to your endpoint or callback—see SECURITY.md.


Quality

  • 87% test coverage
  • Zero runtime dependencies
  • Mutation testing (Stryker) >71%

Examples

examples/README.md — Overview and how to run each demo.

| Example | Description | |---------|-------------| | basic-usage.html | Vanilla HTML, no build. Run pnpm run build then open file:// or use a static server. | | HTML demos | More: circular-references, worker, presets, proxy-tracking, lazy-loading, lazy-initialization, custom-objects. | | react-example | React 18. cd react-example && pnpm install && pnpm start | | vue-example | Vue 3 + Vite. cd vue-example && pnpm install && pnpm run dev | | svelte-example | Svelte 4 + Vite. cd svelte-example && pnpm install && pnpm run dev |

Contributing / local dev

git clone https://github.com/Syntropysoft/syntropyfront.git
cd syntropyfront
pnpm install
pnpm test
pnpm run build

License

Apache-2.0 — use in commercial and open-source projects.

Developed for a clearer and more stable web.