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

dotnet-modular-react-template

v1.0.15

Published

CLI template factory for bootstrapping a .NET + React modular-monolith product repository.

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

oxfaceoxface

Keywords

dotnetreacttemplatemodular-monolithaspire

Readme

dotnet-modular-react-template

Template factory for a domain-neutral .NET + React modular-monolith product repository.

The generated-product payload lives under template/. Root files maintain the factory: bootstrap automation, factory verification, release notes, and maintainer documentation.

Use The Template

After publication, install and run the bootstrap CLI like any other npm tool:

pnpm add --global dotnet-modular-react-template

dotnet-modular-react-template --product-name "Acme Desk" --output ../acme-desk

For one-off use without a global install:

pnpm dlx dotnet-modular-react-template -- --product-name "Acme Desk" --output ../acme-desk

When developing the factory locally, use the root script:

pnpm template:bootstrap -- --product-name "Acme Desk" --output ../acme-desk

The output path may be missing or may already be an existing repository. The template payload does not include README.md or LICENSE, so repository-host defaults can remain in place. Bootstrap stops if any generated path would replace an existing file or directory.

To test the installable package before publication, pack it and run the tarball:

mkdir -p /tmp/dotnet-modular-react-template-pack
pnpm pack --pack-destination /tmp/dotnet-modular-react-template-pack
pnpm dlx /tmp/dotnet-modular-react-template-pack/dotnet-modular-react-template-0.0.0.tgz -- --product-name "Acme Desk" --output /tmp/acme-desk

The bootstrap command accepts one display-oriented product name and derives the .NET namespace/project prefix, npm scope, local service slugs, database names, and visible display text.

Maintain The Factory

Use Node 24 and pnpm 10.33.x for factory maintenance.

Useful maintenance commands:

  • pnpm verify
  • pnpm pack
  • pnpm scripts:lint
  • pnpm template:verify
  • pnpm template:verify:full

Factory maintenance documentation lives under docs/:

  • docs/README.md indexes factory-maintainer docs.
  • docs/template-decisions.md records durable template-factory decisions.
  • docs/testing.md records release and bootstrap validation steps.

Generated-product documentation lives under template/docs/; generated-product agent and OpenSpec context starts at template/AGENTS.md, template/docs/governance.md, template/docs/openspec.md, and template/openspec/config.yaml. Generated-product implementation progress is indexed under template/docs/current-state/.