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

zakarya

v1.0.0

Published

Production-grade frontend framework generator for Next.js App Router with TanStack Query and feature-based architecture

Readme

zakarya

Production-grade frontend framework generator for Next.js (App Router) TanStack Query · Axios · TypeScript Strict · Feature-Based Architecture


Table of Contents

  1. Philosophy
  2. CLI Architecture
  3. Internal Folder Structure
  4. Installation
  5. Commands
  6. Generated Project Architecture
  7. Generator Engine Design
  8. Complete Generated Feature Example
  9. zakarya.config.json Reference
  10. Plugin System
  11. Safety System
  12. Naming Convention Engine
  13. Dependency Rules
  14. Evolution Roadmap

Philosophy

zakarya is not a template copier. It is a frontend framework generation system.

It exists to solve the #1 scaling problem in frontend engineering teams: architectural drift.

When five engineers start five features, they produce five different patterns — different folder names, different query strategies, different error handling approaches, different import paths. Three months later, the codebase is an archaeology site.

zakarya enforces a single, opinionated, machine-verified architecture. Every feature generated by zakarya is:

  • Isolated — cannot import from another feature
  • Predictable — identical internal structure, always
  • Consistent — same naming conventions, same query patterns, same service contract
  • Safe — no accidental overwrites, backup before every mutation
  • Extensible — plugins can add new generator types without touching core

CLI Architecture

zakarya (CLI entry)
│
├── commands/              ← Commander.js command registrations
│   ├── create.ts          ← zakarya create <n>
│   ├── init.ts            ← zakarya init <n> (alias)
│   ├── generate.ts        ← zakarya generate feature|resource
│   └── doctor.ts          ← zakarya doctor (arch validation)
│
├── generators/            ← Core generation logic
│   ├── project.generator.ts   ← Scaffolds full Next.js project
│   ├── feature.generator.ts   ← Generates isolated feature module
│   └── resource.generator.ts  ← CRUD resource with smart presets
│
├── engine/                ← Generation primitives
│   ├── naming.engine.ts   ← All naming conventions (camel/pascal/kebab/…)
│   ├── template.engine.ts ← {{VAR}} interpolation + #if/#each blocks
│   └── injection.engine.ts← Safe code injection into existing files
│
├── templates/             ← Code templates per layer
│   ├── feature/           ← types/service/queries/mutations/hooks templates
│   └── project/           ← shared layer / app / config templates
│
├── config/
│   ├── config.types.ts    ← ZakaryaConfig interface + DEFAULT_CONFIG
│   └── config.resolver.ts ← Reads & deep-merges zakarya.config.json
│
├── plugins/
│   └── plugin.system.ts   ← Plugin contract, registry, loader
│
├── safety/
│   └── safety.system.ts   ← Backup-before-overwrite, confirm gates
│
└── utils/
    ├── banner.ts           ← ASCII art banner
    └── package.ts          ← Reads CLI version from package.json

... (README truncated for brevity)