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

@becomap/react-native

v0.1.6

Published

React Native SDK for Beco indoor mapping and wayfinding

Downloads

100

Readme

@becomap/react-native

Indoor maps and wayfinding for React Native.

📖 Documentation

Install

npm install @becomap/react-native react-native-webview

Requires React Native 0.76+ (New Architecture), iOS 15.1+, and Android.

Expo: needs a development build — Expo Go is not supported.

npx expo prebuild
npx expo run:android   # or: npx expo run:ios

npx expo install react-native-webview resolves against Expo's SDK compatibility table, and on Expo SDK 55 that table pins 13.16.0 — older than this SDK's >=14.0.0 peer range. Satisfying the peer range makes expo-doctor and expo install --check report a mismatch:

✖ Check that packages match versions required by installed Expo SDK

❗ Major version mismatches

package               expected  found
react-native-webview  13.16.0   14.0.1

This is a disagreement between Expo's compatibility table and this SDK's peer range, not a build or runtime failure — on an Expo SDK 55 + RN 0.83.10 app, pod install succeeded, the iOS build reported zero errors, Gradle reported BUILD SUCCESSFUL, and the map rendered on both an iOS simulator and an Android emulator with no SDK runtime errors. To silence both checks, exclude the package from Expo's version check in your own package.json:

{ "expo": { "install": { "exclude": ["react-native-webview"] } } }

See expo.fyi/dependency-validation.

Bare React Native: run cd ios && pod install. Autolinking handles the rest.

Usage

import { useRef } from 'react';
import { StyleSheet } from 'react-native';
import {
  BecoMapView,
  createBCMapInitOptions,
  createBCMapSiteOptions,
} from '@becomap/react-native';
import type { BecoMapViewHandle } from '@becomap/react-native';

export default function App() {
  const map = useRef<BecoMapViewHandle>(null);

  return (
    <BecoMapView
      ref={map}
      style={StyleSheet.absoluteFill}
      onMapReady={() => {
        map.current?.initialiseMap(
          createBCMapInitOptions({
            clientId: 'YOUR_CLIENT_ID',
            clientSecret: 'YOUR_CLIENT_SECRET',
            siteIdentifier: 'YOUR_SITE_IDENTIFIER',
          }),
          createBCMapSiteOptions()
        );
      }}
    />
  );
}

Your client ID, client secret, and site identifier come from Beco. Read them from your app's own configuration at runtime — don't commit them.

That's the whole setup. Everything else — floors, search, selection, camera, routing, events, errors — is in the documentation.

Notes

  • Network is required the first time a map loads.
  • The SDK renders the map only — floor pickers, search bars, and loading states are yours to build.

License

MIT — see CONTRIBUTING.md if you'd like to contribute.