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

sample-typescript-lib

v1.0.3

Published

The idea to create a typescript library it's based on some code from a project, we identified that it could be better to extract some files as libraries so it can be installed as dependency on some microservices, preventing code duplication and easy maint

Downloads

10

Readme

Typescript library generation

The idea to create a typescript library it's based on some code from a project, we identified that it could be better to extract some files as libraries so it can be installed as dependency on some microservices, preventing code duplication and easy maintainance.

This is an example librar that could help you on a similar scenario as above.

Installation

Libraries are generated the same way as a Node project

npm init

Configuracion package.json

Add some building scripts

"scripts": {
    "build": "tsc",
    "build:check": "tsc --noEmit",
  },  
  "main": "lib/index.js",
  "types": "lib/index.d.ts",
  "files": [
    "lib/**/*"
  ]

Neccesary dependencies installation

Since we are writing a typescript library we would need to install some depenendencies:

Typescript

npm i typescript

Types/node

npm i @types/node

Generating out project as a TS project : tsconfig.json

tsc --init

Directives created by the previous command can be updated as desired, these directives will be used at compiling time were mostly of the we tell what kind of verifications do we need over our code.

{
  "compilerOptions": {
    "target": "es5",
    "module": "commonjs",
    "moduleResolution": "node",
    "esModuleInterop": true,
    "resolveJsonModule": true,
    "lib": ["es6", "es2015"],
    "types": ["node"],
    "declaration": true,
    "outDir": "lib",
    "rootDir": "src",
    "strict": true,
  },
  "exclude": [
    "lib",
    "node_modules",
    "src/**/*.spec.ts"
  ],
  "include": [
    "src"
  ]
}
Doubts about tsconfig.json directives? => https://www.typescriptlang.org/tsconfig

Usage

export function helloSpace(spaceName:string) {
    console.log(`Hello space ${spaceName}`);
}

Type to compile out new library

npm run build

Previous commando will generate a new folder /lib were it is going to host some autogenerated .js and .d.ts files, were these types file are going to be neccesary for our TS project.

Working on testing our library on a local environment over other project

npm link

After running the above command over our library root folder, it will be available globally & locally to be consumed as a dependency on any of our local project just before publishing it to NPM.

In order for the library to be used on any of our local project, just run the below command

npm link library-name

This way the library will be included inside our node_modules folder to start using it.