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

@ng-native/expo

v0.4.0

Published

Expo modules as Angular services for Angular Native, plus registerExpoView for a module's native view.

Readme

@ng-native/expo

Expo's native modules as Angular services, and Expo's native views as elements.

Alpha: APIs may change before 1.0.

Install

npm install @ng-native/expo
npm install @angular/core expo

Every Expo module (expo-haptics, expo-clipboard, expo-file-system, and the rest) is an optional peer dependency: install only the ones the app actually uses.

Example

import { Clipboard } from '@ng-native/expo/clipboard';
import { FileSystem } from '@ng-native/expo/file-system';
import { Haptics } from '@ng-native/expo/haptics';

export class Notes {
  private readonly clipboard = inject(Clipboard);
  private readonly files = inject(FileSystem);
  private readonly haptics = inject(Haptics);

  protected async save(text: string): Promise<void> {
    this.files.write(this.files.document('notes.txt'), text);
    await this.clipboard.write(text);
    this.haptics.notify('success');
  }
}

One entry point per module, so importing haptics does not bundle the file system. Nothing is provided anywhere - injecting a service is the whole setup, and a service nobody injects is never constructed. See Using a module for how the exports map and the runtime fallback behind each service work.

What's in the package

  • Device state - Battery, Brightness, Network, Orientation, Locale, the sensors, Fonts, AppInfo, KeepAwake.
  • Feedback - Haptics, Clipboard, Notifications, StoreReview.
  • Storage and files - Storage, SecureStorage, FileSystem, database(), assets().
  • Media and camera - ImagePicker, DocumentPicker, ImageEditor, MediaLibrary, the Camera directive, videoPlayer()/audioPlayer().
  • Location and identity - Location, Biometrics, Sign in with Apple, Tracking, Crypto, ScreenCapture, Browser.
  • App lifecycle - splashScreen, Updates, BackgroundTask.
  • Native views - registerExpoView()/registerExpoViews(), and the @expo/ui SwiftUI and Jetpack Compose controls.
  • Permission - the getXPermissionsAsync/requestXPermissionsAsync pair any module exposes, as one class.

Docs

License

MIT