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

typescript_module_example

v1.0.0

Published

An example / test case of importing typescript modules located in a node_modules folder.

Downloads

2

Readme

typescript_module_example

An example / test case of importing typescript modules located in a node_modules folder.

Explanation

This project shows a simple example of importing 3 types of TypeScript (external) modules.

  • First is a normal module declared in a file called file_module.ts
  • Next is a module located in node_modules called index_module which has index.ts as its main entry point.
  • Finally there is package_module which uses a package.json file to declare its TypeScript entry point using the typings property.

Note that for published modules you should use a d.ts file for the typings property as you don't want your module consumers to recompile your module, just consume its typings.

Expected Result

The project should compile without errors. Running the example would display

$ node app.js
hello from file_module
hello from index_module
hello from package_module

Current output with TypeScript 1.8.0-dev.20151104

$ tsc --version
message TS6029: Version 1.8.0-dev.20151104

$ tsc app.ts --module commonjs --moduleResolution node

$