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

santis-test-template

v1.0.1

Published

testing template

Readme

Custom React Native Template — Setup Guide

This guide walks through creating your own reusable React Native template/boilerplate, similar to santis-world-template.

1. Create the template package

mkdir your-template-name
cd your-template-name
npm init -y

Open the generated package.json and:

  • Remove/modify fields as needed (description, author, license, etc.)
  • Add the following so only the template files are published/used:
"files": [
  "template",
  "template.config.js"
]

2. Create the template config

Create a file named template.config.js in the root:

module.exports = {
  placeholderName: 'SantisWorld',
  templateDir: './template',
};

3. Match the placeholder name

placeholderName should match the name of the project you scaffold in the next step (it doesn't have to match your final project name later — this is just the name used internally when generating the template).

4. Scaffold the React Native app into the template directory

From the project root:

npx @react-native-community/cli init SantisWorld --directory template

This creates a fresh bare React Native app inside ./template.

5. Fix a known CLI/npm issue with .gitignore

Reference: (https://docs.npmjs.com/cli/v11/using-npm/developers)

Keeping files out of your Package

Follow their recommendation OR below

The RN CLI generates a .gitignore inside template/ that can get excluded when packaging, since npm ignores .gitignore files by default when publishing. Rename it so it's preserved:

mv template/.gitignore template/_gitignore

To verify it's there:

ls -la template

Note: when your template generator copies these files into a new project, it should rename _gitignore back to .gitignore at generation time.

6. Build your boilerplate code

Add your actual folder structure, design system, navigation setup, state management, and any other opinionated defaults inside template/ — this is the code every new project scaffolded from this template will start with.