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

next-speedcurve

v1.0.1

Published

SpeedCurve integration for Next.js applications.

Downloads

4

Readme

next-speedcurve

npm version

SpeedCurve integration for Next.js applications.

Installation

yarn add next-speedcurve

Usage

The SpeedCurve component will inject the SpeedCurve scripts into the document head and initialize RUM at the beginning of each SPA "page view".

The following example shows this being done via the Next.js App component:

import { SpeedCurve } from 'next-speedcurve';

const MyApp = ({ Component, pageProps }) => (
  <>
    <SpeedCurve
      luxId="123"
    />
    <Component
      {...pageProps}
    />
  </>
);

export default MyApp;

RUM API

The useSpeedCurveLUX() hook can be used to interact with the SpeedCurve RUM JS API, for example:

import { useSpeedCurveLUX } from 'next-speedcurve';

useSpeedCurveLUX({
  data: {
    'cart size': 128,
    'experiment A': 'control',
  },
  label: 'my-page',
  samplerate: 20,
});

The following properties are available:

| Property | Description | |----------|-------------| | auto | If set to false, the beacon is not sent at the window load event. | | data | An object containing key value pairs to be added to the beacon. | | debug | If set to true, debug messages are written to the browser console. | | forceSample | Calling LUX.forceSample() changes your session cookie so that on all subsequent page views you will be sampled and should see RUM data being generated. | | label | This is the “page label” used to group RUM data by page type. | | samplerate | This is the sample rate for determining whether the beacon is sent. |

See the SpeedCurve RUM JS API docs for more details about these properties.