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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@js-analytics/react

v1.0.13

Published

A monitor for js-analytics to setup monitoring for react projects using error boundaries.

Downloads

17

Readme

@js-analytics/react

@js-analytics/react is a TypeScript library for collecting and reporting errors to https://js-analytics.com.

Installation

Use the package manager npm or yarn to install @js-analytics/react.

npm install -S @js-analytics/react

or

yarn add @js-analytics/react

Usage

The monitor works with react error boundaries. By wrapping your react app with the code you want the monitor to keept rack of you can have all errors reported back to js-analytics. Allowing you to fix them according to how often they occur.


import { JSAMonitor } from '@js-analytics/react';

// more code here

// in your render
return (
  <JSAMonitor pid="<YOUR JS-ANALYTICS PROJECT ID>">
    your react code goes here
    </JSAMonitor>
)

in Next.js I recommend placing is in the pages/_app.tsx file:


import { JSAMonitor } from '@js-analytics/react';

function MyApp({ Component, pageProps, router }) {
return (
  <JSAMonitor pid="<YOUR JS-ANALYTICS PROJECT ID>">
    your react code goes here
    </JSAMonitor>
  );
}

export default MyApp;

This will capture all errors that occur during server-side render and client-side executions and report them to JS-Analytics.

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

License

MIT