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 🙏

© 2024 – Pkg Stats / Ryan Hefner

react-native-template-rebolt

v0.0.4

Published

> This is a React Native application developed in Reason.

Downloads

9

Readme

HelloWorld

This is a React Native application developed in Reason.

Installation

To get started, add the following scripts to your package.json:

"scripts": {
  "start": "node node_modules/react-native/local-cli/cli.js start",
  "build": "bsb -make-world -clean-world",
  "watch": "bsb -make-world -clean-world -w"
}

Next, run watch and start scripts from the command line so that both processes are running at the same time. This can be done with yarn (e.g. yarn watch) or npm (e.g. npm run watch).

The first script compiles you Reason code in a watch mode, meaning that every change is instantly recompiled.

Second one is a React Native packager that serves the compiled Reason code to the React Native client.

Hiding .bs.js files

Bucklescript compiles your Reason files to Javascript in source, meaning that App.re will result in App.bs.js file generated next to it.

These are build files and are by default ignored from the git repository.

If you are using VSCode, you can add the following to your workspace settings to hide them automatically:

{
  "files.exclude": {
    "**/*.bs.js": true
  }
}

Breakdown of existing files

The react-native init command generates a lot of boilerplate with files that might be not needed for your particular use case. Below is a breakdown of all top-level files to help you decide:

  • .babelrc - required, for transpiling Javascript files to supported by the mobile engine Javascript version
  • .buckconfig - optional, configuration files for Buck. Can be safely removed in most cases unless you are planning on using it
  • .flowconfig - optional, used to configure Flow, which is a type checker for Javascript. Can be removed as we are writing our code in Reason now
  • .watchmanconfig - optional, configuration for Watchman, which is a Facebook tool for listening to file system changes. This file is not needed, unless you plan on extending its configuration right now
  • app.json - optional, usually generated when you eject from an Expo or create-react-native-app project. Can be removed without any issues

For more detailed instructions, please check the docs