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-anywhere

v0.1.0-rc.7

Published

An opinionated environment for building cross-platform react apps

Readme

React Anywhere

An opinionated environment for building cross-platform react apps with no configuration. Inspired by and largely forked from create-react-app.

Getting Started

# Install
npm i -g react-anywhere

# Create Your App
react-anywhere init MyApp
cd MyApp

# Edit ./MyApp.js

# Develop for browsers:
react-anywhere web

# Develop on Android:
react-anywhere android

# Develop on iOS:
react-anywhere ios

# Launch react-native packager, for use when native apps are already installed:
react-anywhere native

Reserved files and warmup

You will notice that react-anywhere needs to put a few extra files and directories into your project before it can run your app.

DO NOT EDIT THESE RESERVED FILES!! They are considered an implementation detail of the environment and aren't really part of your app, so react-anywhere will regularly wipe them out and replace them.

This warmup step can be run independently, and will force a refresh of the reserved files:

react-anywhere init MyApp
cd MyApp
ls
> MyApp.js       node_modules    package.json
react-anywhere warmup
ls
> android           index.android.js    index.ios.js        ios         package.json
> MyApp.js         index.html      index.js        node_modules        web

The files are excluded from git with the default .gitignore file, and will be cleaned up as part of the npm prepublish hook. You can also clean up by hand:

# Run this to clean up the junk that react-anywhere puts in your project root:
react-anywhere clean
ls
> MyApp.js       node_modules    package.json

Anywhere version is defined by your project

In the package.json of your project, you can specify which version of the environment should be used to run your app.

{
  "name": "MyApp",
  "version": "0.0.0",
  "reactAnywhere": {
    "version": "0.1.0"
  }
}

When running react-anywhere inside of MyApp, this specified version gets used. To upgrade to future versions of the react-anywhere environment, bump this version in your package.json and re-run any react-anywhere command.

Using another version of Anywhere

You can always override the version of react-anywhere that gets used to run a command:

react-anywhere init MyApp --react-anywhere-version=0.1.0

This is useful to create an app with a different environment, but it can also be used inside existing apps to experiment with future versions of react-anywhere without commiting to it.

Roadmap & Contributions

We have lots of work to do! Here is what I would like to have supported:

  • Automate Jest testing
  • Automate NPM publishing
  • Automate native builds for play store and app store
  • Allow package.json configuration of app icon and favicon
  • Support "eject" ala create-react-app
  • Support more platforms
  • Support native dependencies
  • Server rendering
  • Make web server more extensible
  • Switch over to react-primitives instead of relying on react-native primitives with react-native-web shim

Any and all contributions are welcome! Before embarking on a big feature, please post an RFC issue to discuss the planned implementation.