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

@react-native-healthkit/core

v16.0.0

Published

Shared types, helpers and native code for the react-native-healthkit packages

Readme

@react-native-healthkit/core

Shared foundation for the react-native-healthkit packages:

You do not use this package directly, and you do not need to install it: both packages above depend on it at an exact version, so your package manager brings in the matching copy. It holds what they have in common:

  • TypeScript types that both packages expose (AuthorizationStatus, UpdateFrequency, Device, SourceRevision, DateFilter, EmitterSubscription, …). Both packages re-export them, so import from the package you use.
  • Expo config plugin building blocks (@react-native-healthkit/core/plugin): the HealthKit entitlements and Info.plist usage descriptions each package's app.plugin.js composes.
  • Native code (ReactNativeHealthkitCore pod): the shared HKHealthStore, sample and anchored queries, anchor (de)serialization, predicate and metadata helpers, Objective-C exception catching, and the launch-time background-delivery observer registration.

Installation

Nothing to do: installing @kingstinct/react-native-healthkit or @react-native-healthkit/health-records installs the exact matching version of this package, and Expo autolinks it through that dependency.

The one exception is a bare React Native app, where the React Native CLI only autolinks packages listed in the app's own package.json:

bun add @react-native-healthkit/core

This package shares its version with the two packages above. All three are released together on the same number, and their podspecs require a core pod of exactly their own version, so any mismatched or mixed-version combination fails at pod install rather than during the Swift build or at runtime. Upgrade them together.