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-model-city-app

v1.0.7

Published

Scaffold a Model City front-end city project: a Next.js app consuming the @modelcity/* platform packages, with build-time module selection and per-city overrides.

Readme

create-model-city-app

Scaffolds a Model City city front-end — the npm analogue of the back-end's Maven archetypes. The generated project is a Next.js app that consumes the @modelcity/* platform packages from the npm registry, with build-time module selection (modelcity gen) and a per-city overrides/ extension mechanism.

Usage

npm create model-city-app@latest my-city

Options:

| Option | Effect | | --- | --- | | --name=<name> | npm package name (default: the directory name) | | --modules=<list> | comma-separated feature modules (leisure, engagement, mobility), all or none; skips the prompt | | --yes | accept all defaults, no prompts (CI-friendly) |

What you get

  • package.json with the platform packages pinned to this archetype's release-train version and the exact peer stack (Next, React, Auth0, Stripe, MapLibre) the platform is built against.
  • modules.config.mjs — the city's declaration of contracted modules.
  • Project wiring derived from the platform's reference app at publish time (via sync-template.mjs): next.config.mjs, postcss.config.mjs (Tailwind v4), eslint.config.mjs, jsconfig.json with the overrides fallback, public/ and .gitignore.
  • Static wiring maintained in the archetype itself (not derived from the reference app): Dockerfile, .dockerignore and .env.example.
  • An empty overrides/ directory documenting the extension mechanism.

Links

Author

Created and maintained by Jesús Pérez Melero, author of the Model City platform.

License

MIT — see LICENSE.