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

gulp-ts-compile

v1.0.1

Published

A minimal gulp-typescript replacement built directly on the TypeScript Compiler API's stable, public surface.

Readme

gulp-ts-compile

A minimal gulp TypeScript plugin, built directly on the typescript package's stable, public Compiler API - no version-sensitive internal APIs, no JSON-style option strings to translate.

Why

gulp-typescript has been stuck on an alpha release for years and calls typescript.convertCompilerOptionsFromJson, an internal API that TypeScript removed - so any project still using it breaks the moment typescript is upgraded past whatever version that function last existed in. gulp-ts-compile uses only ts.createProgram, ts.createCompilerHost, program.emit(), and ts.getPreEmitDiagnostics - all long-standing, documented, public Compiler API functions - and does zero option translation of its own, so there's nothing here to break the same way again.

Note: TypeScript 7's Go-based rewrite ("tsgo") removed the classic JS Compiler API entirely - [email protected]'s package no longer exports createProgram, ScriptTarget, or any of the rest of it, replacing it with a different, explicitly unstable API surface. No tool built on the classic API - this one included - can support [email protected] yet. This package's peerDependencies range (>=5.0.0 <7.0.0) reflects that.

Install

npm install --save-dev gulp-ts-compile typescript

Usage

import { dest, src } from 'gulp'
import ts from 'typescript'
import { tsCompile } from 'gulp-ts-compile'

export const typescript = () => {
  const result = src('src/**/*.ts').pipe(tsCompile({
    declaration: true,
    target: ts.ScriptTarget.ES2015,
    module: ts.ModuleKind.ES2020,
    moduleResolution: ts.ModuleResolutionKind.Node10
  }))
  result.dts.pipe(dest('dist'))
  return result.js.pipe(dest('dist'))
}

tsCompile(options) returns a transform stream you pipe .ts/.tsx vinyl files into (matching how gulp-typescript's ts(options) worked), which exposes two further vinyl streams once compilation finishes:

  • .js - the compiled JavaScript output
  • .dts - the emitted .d.ts declaration files (only populated if declaration: true is set)

Both streams preserve each input file's original directory structure relative to its base, so piping either into dest('dist') mirrors src/'s layout under dist/.

Options

options is passed straight through as real typescript.CompilerOptions values - e.g. target: ts.ScriptTarget.ES2015, not target: 'es6'. This is deliberate: the calling project already depends on typescript directly, so it can always resolve the right enum values for whatever version it's actually using, and gulp-ts-compile never has to guess or translate.

Error handling

Like tsc itself, compilation still emits output even when there are type errors - diagnostics are printed to the console (in the same format tsc uses) and a summary line reports the error count, but the task doesn't fail outright. If you want strict, error-blocking behavior, check the compiled output yourself downstream.