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

doton

v0.1.8

Published

CLI tool to initialize development configurations for Cursor IDE and more

Downloads

20

Readme

Doton

Test and Publish npm version License: MIT Buy me a coffee

English | 한국어

A CLI tool to easily initialize development configurations.

Features

  • Cross-platform support (macOS, Linux, Windows)
  • Interactive CLI interface
  • Multiple configuration templates
  • Easy installation and usage with npx
  • Written in TypeScript

Installation

No installation required! Simply use npx:

npx doton init

Or install globally:

pnpm install -g doton
doton init

Usage

  1. Run the initializer:

    npx doton init
  2. Choose a configuration type from the menu:

    Choose which config to initialize:
    > cursor - Cursor configuration
    > vscode - VSCode configuration
  3. Enter the target directory where you want to save the configuration:

    Enter target directory: ./my-config
  4. The configuration files will be copied to your specified directory!

Available Configurations

  • cursor - Cursor configuration
  • vscode - Visual Studio Code configuration

Development

Requirements

  • Node.js 18.0.0 or higher (LTS version recommended)
  • pnpm 10.0.0 or higher

Setup

This project uses pnpm as the package manager. If you don't have pnpm installed, you can install it with:

npm install -g pnpm

Then, you can set up the project:

# Install dependencies
pnpm install

# Build the project
pnpm build

# Run in development mode with watch
pnpm dev

# Run tests
pnpm test

# Lint the code
pnpm lint

CI/CD

This project uses GitHub Actions for continuous integration and deployment.

Pull Request Checks

When a PR is created or updated, the following checks run automatically:

  • Linting
  • Tests on current LTS Node.js versions (18.x, 20.x)

Publish Process

When code is merged or pushed to the main branch:

  1. Tests are run to ensure everything is working
  2. If tests pass, the package version is checked against npm
  3. If the current version is less than or equal to the published version, a patch version bump is applied
  4. The package is built and published to npm

Status Badge

The CI status badge at the top of this README shows the current status of the Test and Publish workflow from the main branch. If you fork this repository, make sure to update the badge URLs in the README with your username.

Adding Your Own Configurations

To add your own configuration files to use with this tool:

  1. Create a new directory in the project root with your configuration name
  2. Add your configuration files inside that directory
  3. Update the configurations object in src/index.ts to include your new configuration

License

MIT

Support

If you find this tool helpful, you can buy me a coffee!