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

v0.2.0

Published

> This is a React Native application developed in Reason.

Downloads

3

Readme

React Native HelloWorld

This is a React Native application developed in Reason.

Please carefully read instructions below in order to enjoy ReasonML development experience.

Setup

Start a Reason React Native project with this template

react-native init MyApp --template reason

Command line

Install BuckleScript with the following command:

yarn add bs-platform --dev

IDE

To get the best development experience possible, we recommend you to use VSCode with Reason Language Server extension & optionally Flow Language Server extension if you have JavaScript covered by Flow.

If you won't want to use VSCode, at least get a ReasonML editor plugin.

package.json

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

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

Note: you probably have start already.

Development workflow

Note: yarn can be replaced by npm run in all commands below.

Depending on your editor & its ReasonML integration you might need to use:

yarn re:watch

Reminder: this step might be unecessary if your editor can handle ReasonML compilation by its own. Read more.

As soon as .re files are being compiled to .bs.js, you can either start the project on iOS Simulator (included in Xcode) or an Android Emulator (if you are unfamiliar with Android Studio, you might be interested by Genymotion).

yarn start:ios

or

yarn start:android

This commands should open up a virtual device & start React Native metro bundler. This packager will serves the compiled Reason code to the React Native client.

Now you can start coding by editing files in src/!

Read more about starting the project in your environment of choice.

Note: as soon as you have the app installed in a simulator/emulator, you could just run

yarn start

This avoid rebuilding the entire native parts & will just start React Native metro bundler.

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 you are writing our code in Reason
  • .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