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

ts-publish

v3.0.0

Published

Typescript project compiler - integrates compiler and linter.

Downloads

27

Readme

Downloads per Month NPM Version Shields.io License

ts-publish

This package provides a collection of node scripts to aid in the deployment of typescript projects.

Configuration

You may provide a configuration file called ts-publish.json. This file has the following structure:

[
  {
    "name": "project-name",
    "files": [
      "src/file1.ts",
      "src/file2.ts"
    ],
    "libraries": [
      "files/to/always/be/included.ts"
    ],
    "compilerOptions": {
      "outDir": "./build/lib",
      "declaration": true
    }
  },
  {
    "name": "build-tools",
    "files": [
      "build-tools/ts-hook.ts",
      "build-tools/karma.config.ts",
      "build-tools/webpack.config.ts"
    ],
    "compilerOptions": {
      "outDir": "./build"
    }
  }
]

In the above example we have an array declaring two projects. One is the main project and the other one is a "build-tools" project which is in charge of compiling all of our project tools. Note that on the "build-tools" project we did not include the "libraries" option. This is optional and should only be used if you want certain files to always be included in the transpilation. One example of such files would be files that contains declarations.

At the moment all the paths are set relative to the root directory. We should also note that each ts-publish.json file reads the tsconfig.json file to look for the compilerOptions. These options should be general enough to fit every project.

ts-compile

This is meant to be a replacement for tsc. To use it we need to make sure to have a ts-publish.json file available.

To compile all the files for build-tools do

ts-compile build-tools

If the configuration file has a different name we can specify it

ts-compile build-tools --config path/to/config-file.json