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

@pachun/use-expo-push-notifications

v0.0.18

Published

Simpler (and more testable) expo-notifications event handling

Readme

npm version

useExpoPushNotifications

yarn add @pachun/use-expo-push-notifications
import React from "react"
import * as Notifications from "expo-notifications"
import useExpoPushNotifications from "@pachun/use-expo-push-notifications"

const App = () => {
  useExpoPushNotifications({
    onNotificationReceived: React.useCallback(
      (notification: Notifications.Notification) => {
        console.log(
          "Notification received",
          JSON.stringify(notification, null, 2),
        )
      },
      [],
    ),
    onNotificationInteraction: React.useCallback(
      (notificationResponse: Notifications.NotificationResponse) => {
        console.log(
          "Notification interaction",
          JSON.stringify(notificationResponse, null, 2),
        )
      },
      [],
    ),
  })

  return <></>
}

Motivation

When you want to test the behavior of your app rather than useEffect and useRef implementations, this can be helpful.

import { renderRouter, screen, waitFor } from "expo-router/testing-library"
import expoPushNotificationsSimulator from "tests/helpers/expo-push-notifications-simulator"

jest.mock("@pachun/use-expo-push-notifications", () => ({
  __esModule: true,
  default: jest.fn(),
}))

describe("receiving push notifications", () => {
  it("displays text received in notifications", async () => {
    // capture your notification handler before you render
    let sendNotification
    jest
      .mocked(useExpoPushNotifications)
      .mockImplementation(({ onNotificationReceived }) => {
        sendNotification = onNotificationReceived
      })

    renderRouter("src/app", { initialUrl: "/" })

    // call your actual notification handler
    sendNotification!({
      request: {
        content: {
          data: {
            text_received_in_notifications: "Hello, world!",
          },
        },
      },
    })

    await waitFor(async () => {
      expect(screen.getByText("Hello, world!")).toBeTruthy()
    })
  })
})

This will allow you to test the actual behavior of your app when receiving notifications.

You can test how it will handle receiving notifications on different screens by rendering the router at different routes.

You can do the same for testing notification interactions, like tapping a notification, or long pressing one to bring up the notification actions menu.

You can log the interaction if you don't know what it will look like in your handler, and then write a test for that format of message and what you'd like to happen when it's received.

Contributing

PRs are exciting 🤟 Bump the version number in package.json and open one.

  • Please do not submit AI generated pull requests.
  • Please keep coverage at or above where it is when you clone the repo (yarn test --collectCoverage).