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-reality-cli

v1.0.0

Published

Command Line utility for react-reality

Downloads

14

Readme

react-reality-cli

Command line interface for react-reality projects

Installation

yarn global add rhdeck/react-reality-cli

or

npm i g rhdeck/react-reality-cli

Usage

init

Create a new react-reality project

react-reality init myproject

or use the short alias:

rr init myproject

Fun Fact You can use rr as an alias for any of your react-native commands. rr run-ios helps, and is shorter!

Templates

Specify the react-reality template you want to use for faster initialization:

react-reality init myproject --template <mytemplate>

or try the short version

rr init myproject -t <mytemplate>

Pre-Built Templates

To help with learning react-reality, some basic apps are available as templates

holokit

Deploys a package designed for use with HoloKit heads-up stereoscopic display.

rr init myproject -t holokit

URL

Any url specified with a file://, http:// or https:// scheme will reference a react-reality template a that location.

rr init myproject -t https://github.com/rhdeck/react-reality-template-holokit

npm scoped project

Any argument prefixed with a @ and containing a slash is assumed to be a scoped npm project, in the form @scope/project. Passes through to npm

rr init myproject -t @myscope/mytemplate

GitHub repository

Any argument containing a slash (that does not start with the @) is assumed to refer to a github repository, and builds a https url to access it.

rr init myproject -t rhdeck/react-reality-template-holokit

NPM projects

Any other string tries to build a URL from NPM with the prefix "react-reality-template-", like a react-native template would.

rr init myproject -t holokit

Note on building templates of your own

Templates parallel the build system from react-native. They must contain:

  1. package.json used for identification only. Should include a name and version.
  2. dependencies.json indicating dependencies that should be added to the project. (should include the react-reality package and react-native-swift at a minimum)
  3. Any other files you want copied into your package that would override the core react-native files. Usually App.js is defined here, since it is the center of the app experience.

Note Templates are installed by first adding then removing from your dependencies. So you will not find them in your project post-install.