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

@kentickets/kencommon

v1.0.15

Published

- To store the common/shared code for several services - Pushed to NPM registry. Write in TS but publish as as JS

Downloads

3

Readme

Common

  • To store the common/shared code for several services
  • Pushed to NPM registry. Write in TS but publish as as JS

Dev-Dependencies

  • typescript
  • del-cli

Steps to push to NPM registry

  1. Register NPM accont
  2. Open a new project for the code
  3. git commit the project, no need push
   git init
   git add .
   git commit -m "initial commit"
  1. login (npm login)

Convert TS to JS

  1. Add script into file package.json.

"build":"tsc"

  1. Need to specify the configuration to convert to JS in tsconfig.json

"declaration": true: Generate .d.ts files from TypeScript and JavaScript files in your project. "outDir":"./build": Specify an output folder for all emitted files.

  1. Add fields into file package.json

main: "./build/index.js" : Defining exactly what file we export. It indicates what file we tried to reach into when write out the import statement in other services.

types: "./build/index.d.js" : Tell TypeScript what the main type definition file inside of our project is.

files:["build/**/*"] : Tell NPM what set of files inside of our project want to make sure 100% gets included inside the final published version of the package. So, it is the everything inside the build directory

Update NPM Pacakge Changes

  1. git status to check any changes
  2. git add .
  3. git commit -m <comment>
  4. Add increment to the version
    • Add manually in package.json
    • Run command npm version patch. It willa automatically add the number of the version. For example, 1.0.0 --> 1.0.1

How to import/include all the common/shared code in index.ts

Remember install all the dependencies

Method 1: Cons: Have to know about different directories and different files inside of our project. Pros: Easy to do and access. Example: import {BadRequestError} from "@sgticketing/common/errors/bad-request-error"

Method 2: Export everythings from the folders Example: export * from "./errors/bad-request-error";