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 🙏

© 2024 – Pkg Stats / Ryan Hefner

dt-init

v1.0.12

Published

Like npm init but for generating TypeScript definitions and tests stubs

Downloads

10

Readme

dt-init

Build Status npm version Dependency Status Development Dependency Status

Like npm init but for generating TypeScript definitions and tests stubs.

Install: npm install -g dt-init

Usage: dt-init module-name [-b|--bower|-d|--def-only gitconfig][-h|--help|-v|--version|
        -c|--configure]

module-name      : Module to generate stubs for.
-b | --bower     : Also generate a bower.json package file for client-side dependencies.
-d | --def-only  : Only generate definition and tests.
gitconfig        : Git configuration file to use for user values (instead of default).
-h | --help      : Display this usage information and exit.
-v | --version   : Display application version and exit.
-c | --configure : Write configuration file and exit (destructive).

Running dt-init module-name -b will generate the stubs (with package.json and bower.json) and retrieve the module you plan to write the definitions and tests for. This results in a directory tree such as:

module-name/
├── bower.json
├── bower_components
├── node_modules
├── module-name.d.ts
├── module-name-tests.ts
├── node_modules
└── package.json

After you have finished your TypeScript definitions and tests, within module-name you can invoke npm test to compile and run them.

Install the TypeScript compiler first if necessary with: npm install -g typescript

If you want to use the -b option, you will need to have Bower installed: npm install -g bower

Specify .gitconfig parameter if you want to use a different Git configuration file to the user's default. These values are used in the generated type definitions stubs.