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

create-lesa-app

v0.0.11

Published

Create a new project from the lesa Expo SDK 57 template

Readme

create-lesa-app

Launcher for the lesa Expo template. One slug in — schemes, bundle ids, Android packages and a first commit out.

npm downloads license

Expo SDK React Native expo-router Reanimated Uniwind TanStack Query Zustand TypeScript

English · 한국어

⚗️ Everything here is experimental. Built for me (LESA).

[!WARNING] This is mine. It is shaped around my taste and my workflow, and every choice in it is experimental. No stability, no backwards compatibility, no support — the structure changes without notice.

Read it, borrow from it. But do not ship it as-is — verify it yourself.

pnpm install && npm link
create-lesa-app my-new-app
  ┌  create-lesa-app
  │
  │  ◇ App name
  │    lesa-app
  │
  │  ◇ Display name
  │    Lesa App
  │
  │  ◆ Apple Team ID
  │  ╭────────────────────────────────────────────────╮
  │  │ › ▌                                            │
  │  ╰────────────────────────────────────────────────╯
  │    optional · iOS only · Enter to skip
  │
  └  Enter skip or continue · Esc cancel

[!NOTE] The template is fetched from LESANF/react-native-template-lesa at a pinned tag, so the same command gives the same project tomorrow. A local copy wins when present — lookup order is --template <path> → $LESA_TEMPLATE_DIR → a sibling lesa-expo-template → GitHub.

Derived from one slug

| field | development | preview | production | | ---------------------- | ---------------------------- | --------------------- | ------------- | | name · slug | <slug> — every environment | | | | scheme | <slug>-dev | <slug>-preview | <slug> | | bundleId · package | com.<slug*>.development | com.<slug*>.preview | com.<slug*> | | version | 0.0.1 build 1 | | |

<slug*> drops hyphens. Android package names allow only letters, digits and underscores between periods, so lesa-app becomes com.lesaapp — URL schemes do allow hyphens and keep them.

A name that is not lowercase ASCII becomes the display name, and a slug is asked separately. It is never romanized: that value ends up as the Xcode project name, the scheme and PRODUCT_NAME, and transliteration loses too much.

Not asked

API and OTA urls, universal-link hosts, Android signing, icons, firebase/ files. None are knowable at creation time. Every spot the project has to fill in is marked TODO(앱), and the closing screen prints the grep for it.

Notes

  • Stage new template files. Copying is driven by git ls-files, so build output and local state are excluded by definition — and a file you just created is not copied until it is git added.
  • npm link follows your Node version. Re-run it after switching with nvm, or skip linking and run pnpm start ../my-new-app from this repo.
  • The prompt is testable without a TTY. useInput needs one, so the step machine lives in src/flow.ts instead. pnpm test drives the whole flow.
  • Failures clean up. A failed run deletes the directory it created. Ctrl+C leaves a partial tree alone rather than removing it silently.

Commands

| | | | ----------------------- | --------------------------------- | | create-lesa-app <dir> | create a project | | --template <path> | point at a template explicitly | | --help · --version | usage · version | | pnpm test | step machine and derivation tests | | pnpm type-check | tsc --noEmit | | pnpm bake-intro | re-bake the ASCII wordmark frames |

License

MIT — use it however you like.