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 🙏

© 2025 – Pkg Stats / Ryan Hefner

dockerize-aspnetcore

v1.0.1

Published

CLI tool to add docker config files to asp.net core project

Downloads

2

Readme

Dockerize your asp.net core application

A simple CLI tool to dockerize ASP.NET Core application

Usage:

Install module globally

npm i -g dockerize-aspnetcore
cd /path/to/app
dockerize-aspnetcore <WEB_PROJECT_NAME>

where <WEB_PROJECT_NAME> (e.g. MyApp.Web) is a name of a folder with asp.net core project in your solution.

As a result, you'll see ready-to-use Dockerfile and .dockerignore files in your web project folder.

If you are against global installation, you can install it locally:

cd /path/to/app/frontend/folder
npm i dockerize-aspnetcore
cd /back/to/app
npx dockerize-aspnetcore <WEB_PROJECT_NAME>

The global installation is still recommended as your source code doesn't have to know about this module - the Dockerfile is enough.

Some extra details:

It is assumed that your app was created using the standard dotnet new syntax.

If your app is SPA - it's also supported. Please check Dockerfile (line 2) for details - npm installation is already in place. The implementation is pretty simple there - Docker build process relies on dotnet publish command, which does all the needed stuff. It's reasonable - as both Angular- and React-based asp.net core templates come up with such configuration out-of-the-box.

If you have a bit more complex setup with your frontend and backend apps - please take a look on the Multi-Stage Docker builds