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

@flayyer/ping-react

v1.1.0

Published

Monitor and pre-render Flayyer URLs - React component and hook

Downloads

2

Readme

@flayyer/ping-react

Monitor and pre-render Flayyer URLs - React component and hook.

This script will only work on pages where a <meta> tag is present and related to og:image or twitter:image and has for content a Flayyer URL. In other cases this will result in a no-op.

Install

This module supports TypeScript and JavaScript.

npm install --save @flayyer/ping-react

# or with yarn:
yarn add @flayyer/ping-react

Usage

React Hook

We recommended using this library with React Hooks.

Add this to public pages where you have a Flayyer URL in your <meta> tags for dynamic og:images.

import { useFlayyerPing } from "@flayyer/ping-react";

function App() {
  useFlayyerPing();
  // ...
}

Next.js

See https://nextjs.org/docs/advanced-features/custom-app

If you are using Next.js you probably want to add this hook to your /pages/_app.js file.

// /pages/_app.js

import Head from "next/head";
import Flayyer from "@flayyer/flayyer";
import { useFlayyerPing } from "@flayyer/ping-react";

const flayyer = new Flayyer({
  tenant: "tenant",
  deck: "deck",
  template: "template",
  variables: {
    title: "Hello world!",
  },
});

function MyApp({ Component, pageProps }) {
  useFlayyerPing();

  return (
    <>
      <Head>
        <meta property="og:image" content={url} />
      </Head>
      <Component {...pageProps} />
    </>
  );
}

export default MyApp

React component

If you are not using React Hooks, you can active this script by mounting a <FlayyerPing /> component. Make sure to mount it only one time per page.

The same rules described above applies here: this will only work on pages where you have a Flayyer URL in your <meta> tags for dynamic og:images. Ideally only on public pages.

This component has no effect on your DOM since it always renders null.

import { FlayyerPing } from "@flayyer/ping-react";

function App() {
  return (
    <div>
      <FlayyerPing />
      // ...
    </div>
  )
}