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

moo-types

v1.0.0

Published

The objective of this project is to demonstrate how a Typescript project can be used to build an NPM module that can be published to the NPM registry so that it can be used from other Typescript projects without the need to install additional typings.

Downloads

1

Readme

Typescript 1.8.10 NPM Module Seed

The objective of this project is to demonstrate how a Typescript project can be used to build an NPM module that can be published to the NPM registry so that it can be used from other Typescript projects without the need to install additional typings.

Pre-requisites

This project needs Typescript, to install Typescript:

npm install -g typescript

The project also used Gulp:

npm install -g gulp

TSLint is also required:

npm install -g tslint

Mocha:

npm install -g mocha

Typings:

npm install -g typings

Cloning the project

After cloning this project and ensuring global dependencies are installed, execute:

npm install
typings install

This will install all the dev dependencies of the project.

Building the project from Visual Studio Code

To build the project from Visual Studio Code, Press Cmd + Shift + B (or Control + Shift + B on Windows). This will build the project and execute the test cases.

Debugging the project from Visual Studio

To debug the project from Visual Studio Code, set a break point in a Mocha spec file, then Press Cmd + Shift + D (or Control + Shift + D on Windows). Then select "Run mocha" from the debug menu and start debugging. This will hit your breakpoint and stop.

Building the project from command line

To build the project:

gulp pack

The above command will generate a package file that is ready to be consumed by another Typescript project.

Using the binary in a separate project

  • Go to your home directory (or another directory of your choice) and copy the generated file from npm pack to this new directory
cd ~
mkdir moduletest
cd moduletest
cp ../tsc-seed/tsc-seed-1.0.0.tgz .
  • Now initialize a package.json file
$ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.

See `npm help json` for definitive documentation on these fields
and exactly what they do.

Use `npm install <pkg> --save` afterwards to install a package and
save it as a dependency in the package.json file.

Press ^C at any time to quit.
name: (moduletest) 
version: (1.0.0) 
description: 
entry point: (index.js) 
test command: 
git repository: 
keywords: 
author: 
license: (ISC) 
About to write to /Users/nocturne/moduletest/package.json:

{
  "name": "moduletest",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "author": "",
  "license": "ISC"
}


Is this ok? (yes) 
  • Initialize the Typescript project file
$ tsc --init
  • Install the package
$ npm install tsc-seed-1.0.0.tgz

Now, the module can be used from a new file. Create a file called index.ts in Visual Studio Code:

import * as MyModule from "tsc-seed";

const calculator = new MyModule.Arithmetic.Calculator();
console.log(calculator.add(1, 2));
  • Compile the file through the command line
$ tsc
  • Execute the generated .js file
$ node index.js

The output should be:

3