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

@common-ticketing-microservices/common

v1.0.39

Published

1- Tener una cuenta y haber creado la oganizacion en npmjs.com

Downloads

100

Readme

Pasos para crear una libreria

1- Tener una cuenta y haber creado la oganizacion en npmjs.com

2- Crear un proyecto vacio con:

    npm init

3- Debes editar el nombre del paquete:

    @<nombre_organizacion>/<nombre_paquete>

4- Debe logearse usando el comando:

npm login

Aqui te pedira use, password y luego un codigo que te va a enviar al correo

5- Para publicar este paquete necesitamos correr este comando

npm publish --access public

6- Devemos correr typescript init para que cree el archivo de configuracion:

npx tsc --init

7- Luego debemos instalar ciertas cosas necesarias:

npm i typescript del-cli --save-dev

8- Debes configurar un script para hacer el build de la libreria:

 "scripts": {
    "build": "tsc"
  },

9- Debemos habilitar ciertas configuraciones de typescript

    {
        "declaration": true,
        "outDir": "./build",
    }

10- Debemos configurar que archivos seran los que se van a publicar dentro del package.json

  "files": [
    "./build/**/*"
  ]

11- Debemos tambien cambiar la ruta del archivo main dentro del package.json

    "main": "./build/index.js",

12- Debajo del main debemos agregar otra opcion que es types, que no es mas para decir cuales seran lo tipos de nuestra libreria en caso de que se use typescript

    "types": "./build/index.d.ts",

13- No olvidar usar .gitignore para evitar que se suban cosas como el node_module o la carpeta build

    node_modules
    build

14- Para hacer la publicacion cada vez deberiamos correr los siguientes comandos:

npm version patch ->para subir el numero de la version
npm run build ->para compilar nuestro codigo
npm publish --access public ->publicar en publico