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

typespace

v0.1.10

Published

Converts import/require-style TypeScript directories into a unified namespace output.

Readme

Typespace

Converts import/require-style TypeScript directories into a unified namespace output.

Why?

AMD, CommonJS, UMD, and the like are wonderful dependency managers that you should strongly consider using in your project. However, in some browser applications, it's useful to have a single smaller file without the overhead of exports or require.

  • Video games that require extremely rapid startup times
  • Older applications that haven't moved to something like require.js

That's where Typespace comes in. It takes a full set of directories containing TypeScript files that reference each other using import and/or require, and combines them into a single .ts output file.

Sources:

// src/Foo.ts
export var value = true;
// src/Bar.ts
import { Value } from "./Foo";
console.log(`Value: ${value}`);

Output:

namespace MyProject.Foo {
    export var Value = true;
}

namespace MyProject.Bar {
    import Value = MyProject.Foo.Value;
    console.log(`Value: ${Value}`);
}

(in the future, these will be combined and optimized for a reduced file size)

Usage

You can use Typespace via require/import or on the command-line. There's also a gulp plugin.

Required arguments/flags:

  • namespace (-n/--namespace) - name of the root namespace

Optional arguments/flags:

  • config (-c/--config) - input tsconfig.json file path to load files from
  • outFile (-o/--outFile) - output .ts file path
  • pathPrefix (-p/--pathPrefix) - directory root to ignore from module paths
  • root (-r/--root) - root path to search for files under
  • target (-t/--target) - module resolution target, as "none" or "commonjs"

CLI

First install Typespace with npm install typespace.

You can then specify files from a TypeScript config file:

typespace --directory . --root src --outFile dist/combined.ts --config tsconfig.json

Code

const Typespace = require("typespace");

const settings = {
    config: "tsconfig.json",
    directory: ".",
    outFile: "dist/combined.ts",
    root: "src"
};

const converter = new Typespace(settings);
converter.convert()
    .then((fileContents: string): void => {
        console.log(`Printed to ${settings.outFile}:\n${fileContents}`);
    });

Building

Typespace is built using Gulp.

npm install -g gulp-cli
npm install
gulp

The primary Gulp tasks are:

  • tslint - lints source code with TSLint
  • tsc - compiles source code with TypeScript
  • test - runs tests
  • watch - runs Gulp whenever a source or test file changes

Compilation

Source files are in TypeScript and primarly rely on async/await programming. Babel is used for Node compatibility.

Tests

Tests files are in JavaScript and run with Mocha. Test coverage for unit tests is computed with Istanbul.