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

atco

v1.0.13

Published

The tool that provide powerful additional options for Typescript Compiler

Readme

Atco

The tool that provide powerful additional options for Typescript Compiler

Requirements

  • nodejs >= v12.16.0
  • npm >= v6.14.0 (or yarn >= v1.22.0)

Installation

using npm

npm install --save-dev typescript atco

Or using yarn

yarn add --dev typescript atco

Usage

  • Navigate to project root

  • Create tsconfig.json, inside it you have to specific the output directory using compilerOptions.outDir and specific the target directory using include, like the following example

{
  "compilerOptions": {
    "outDir": "./dist"  
  },
  "include": ["./src/**/*"]
}
  • In package.json add these two scripts
{
  "scripts": {
    "start:dev": "atco -w --exec \"node ./dist/index.js\"",
    "start:prod": "atco && node ./dist/index.js"
  }
}
  • To start app in development mode run the following command
# Using npm
npm start:dev
# Or using yarn
yarn start:dev
  • Or start it in production mode using
# Using npm
npm start:prod
# Or using yarn
yarn start:prod

Examples

The Additional Options (API)

| AdditionalOption | Type | Default | Description | | -------------- | ---- | ------- | ----------- | | --copyOthers | boolean | true | Copy files (which doesn't end with extension .js or .ts) and directories (which doesn't contain any file end with extension .js or .ts) | --cleanOutDir | boolean | true | Remove all files and directories in output directory before start running | --exec | string | | Execute the given command when compiling (and copying if --copyOthers set to true) done successfully

NOTE: if output directory not exists atco will automatically create it, the puropse of --cleanOutDir is clean the output directory if it was exists

The other options except (--project, -p, --version,--help) will be forward to Typescript Compiler (take a look at typescript compiler options)

Known Problems

The following problems is currently happening however we will try to fix it in the future

  • In watch mode atco doesn't track remove event (so if you remove file or directory you have to rerun command)