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

tukod

v0.1.1

Published

monorepo mini helper tools

Downloads

25

Readme

tukod

Yarn workspaces/monorepo mini cli helper tools

Installation

npm install -g tukod

or

yarn global add tukod

Usage

Usage
  $ tk <command> [options]

Commands
  generate  Generate a new app
  delete    Remove an app
  init      Create base files in the current directory

Options

  --help  Show help
  --version  Show version
  --no-confirm, Disable confirmation
  --dir, Change the current working directory 

generate
  --template, -t  Template to use
  --name, -n  Name of the app

delete
  --name, -n  Name of the app

init
  --name, -n Monorepo project name 

Examples
  $ tk generate --template=react-app --name=my-app
  $ tk init --name=monorepo-name

Making Templates


To add templates you must add templatesPaths in the tk field of your root package.json. templatesPaths field should contain all your templates directory (can be absolute or relative to monorepo directory).

Templates should have .tkignore so that it will be detected as a template. It should also have a package.json file.

// sample .tkignore

.turbo
dist
!node_modules/*
node_modules

Deleting Apps


To delete apps you need to create an empty .unlock file in the app directory

Configuration


// package.json
{
    "tk": {
        "templates": [
          "path/to/additional/templates_list_1",
          "path/to/additional/templates_list_2",
          "P:/absolute/path/to/additional/templates_list_3"
        ]
    }
}
// or
{
  "workspaces": [
      "apps/*",
      "libs/*"
  ]
}

Roadmap

  • [x] Generate App
    • [x] Template Paths
    • [ ] Remote Templates
  • [x] Delete App
  • [x] Initialize Base
    • [ ] Base Types
  • [x] InkJS Renderer
    • [x] Operations
    • [ ] Replace Inquirer.JS
  • [x] Add Publish Script

License

Distributed under the MIT License. See LICENSE.txt for more information.