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-net

v0.0.3

Published

Create .NET and other projects from NetCoreTemplates GitHub repositories

Readme

create-net

Create .NET and other projects from NetCoreTemplates GitHub repositories.

Usage

npx create-net <repo|ls> [ProjectName]

Commands

List available templates:

npx create-net ls [org]

Create a project:

npx create-net <repo> [ProjectName]

If ProjectName is not specified, the script will use the current directory name and extract the template into the current directory (which must be empty).

Examples

List all available templates:

npx create-net ls

Shows all templates from NetCoreTemplates and NetFrameworkTemplates organizations.

List templates from a specific organization:

npx create-net ls NetFrameworkTemplates

Create a project in a new directory:

npx create-net nextjs MyProject

This downloads from: https://github.com/NetCoreTemplates/nextjs and creates a MyProject folder.

Create a project in the current directory:

mkdir my-project
cd my-project
npx create-net nextjs

This uses the current directory name (my-project) and extracts the template into the current directory.

Create a project from a different organization:

npx create-net NetFrameworkTemplates/web-netfx MyProject

This downloads from: https://github.com/NetFrameworkTemplates/web-netfx

What it does

  1. Downloads the GitHub repository archive from the specified repository
  2. Extracts the archive into a folder named <ProjectName> (or current directory if no ProjectName specified)
  3. Replaces all variations of MyApp with variations of your <ProjectName> (or current directory name):
    • My_AppYour_Project
    • My AppYour Project
    • my-appyour-project
    • my_appyour_project
    • myappyourproject
    • my.appyour.project
    • MyAppYourProject
  4. Renames files and folders containing MyApp variations
  5. Runs npm install in all directories containing package.json

Requirements

  • Node.js >= 14.0.0

Testing

Two test scripts are provided to verify the functionality:

Automated Tests

Run automated tests that verify all scenarios and clean up afterwards:

./test.sh

This tests:

  • Creating a project with repo name and ProjectName
  • Creating a project with organization/repo and ProjectName
  • Creating a project without ProjectName (current directory)
  • Error handling for existing directories
  • Error handling for non-empty directories

Manual Tests

Run manual tests that leave the results for inspection:

./test-manual.sh

This creates test projects in test-manual/ for manual verification. Clean up with rm -rf test-manual/ when done.

Publishing

Automated Publishing (Recommended)

The package is automatically published to npm with provenance when a new GitHub release is created:

  1. Update the version:

    npm version patch  # for bug fixes (1.0.0 → 1.0.1)
    npm version minor  # for new features (1.0.0 → 1.1.0)
    npm version major  # for breaking changes (1.0.0 → 2.0.0)
  2. Push changes and tags:

    git push && git push --tags
  3. Create a GitHub release at https://github.com/ServiceStack/create-net/releases/new

    • The GitHub Action will automatically run tests and publish to npm with provenance

Security Features:

  • Uses OIDC authentication for secure publishing
  • Generates provenance attestations for supply chain security
  • Published with --access public flag

Manual Publishing

To publish manually:

npm login
npm publish --access public

Note: You need to configure the NPM_TOKEN secret in GitHub repository settings for automated publishing. See .github/workflows/README.md for details.

License

MIT