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 🙏

© 2026 – Pkg Stats / Ryan Hefner

bestprices-api-client

v1.0.4

Published

Este paquete contiene servicios reutilizables que se pueden consumir desde otros proyectos como React, React Native, etc.

Readme

📦 bestprices-api-client

Este paquete contiene servicios reutilizables que se pueden consumir desde otros proyectos como React, React Native, etc.


🛠️ Pasos para crear, preparar y publicar un paquete en NPM

1. Crear carpeta e inicializar el proyecto

mkdir bestprices-api-client cd bestprices-api-client npm init -y

configuarr typescript

npm install typescript --save-dev npx tsc --init

Archivo ts config

{ "compilerOptions": { "outDir": "./dist", "rootDir": "./src", "target": "es5", "module": "commonjs", "declaration": true, "strict": true, "esModuleInterop": true }, "include": ["src"] }

Crear la estrucutra de carpetas

mkdir src touch src/api.ts touch index.ts

api.ts

export const getPosts = async () => { const res = await fetch('https://jsonplaceholder.typicode.com/posts'); return res.json(); };

#index.ts

export * from './src/api';

#package.json

{ "name": "bestprices-api-client", "version": "1.0.0", "main": "dist/index.js", "types": "dist/index.d.ts", "scripts": { "build": "tsc" }, "keywords": [], "author": "", "license": "MIT" }

#compilar

npm run build

iniciar sesion con npm

npm login

publicar paquete publico ⚠️ Importante: --access=public es obligatorio si usas scopes como @empresa/paquete.

npm publish --access=public

  1. Instalar el paquete desde otro proyecto

npm install bestprices-api-client

así se utiliza

import { getPosts } from 'bestprices-api-client';

getPosts().then(posts => console.log(posts));

actualizar versión

npm version patch # 1.0.1 npm version minor # 1.1.0 npm version major # 2.0.0

#Volver a compilar y publicar

npm run build npm publish --access=public

recomendación usar un scope para evitar conflictos

{ "name": "@tuequipo/bestprices-api-client", "version": "1.0.0" }

1. Agrega "private": true o publica con un scope

##Los paquetes privados normalmente se publican con un scope (nombre de usuario o empresa). ##Ejemplo de package.json:

{ "name": "@tuequipo/bestprices-api-client", "version": "1.0.0", "main": "dist/index.js", "types": "dist/index.d.ts", "scripts": { "build": "tsc" }, "license": "MIT" }

publicar

npm publish --access=restricted

📄 Alternativa: Usar .npmrc local

@tuequipo:registry=https://registry.npmjs.org/ //registry.npmjs.org/:_authToken=TU_TOKEN_AQUI

publicar con versión del readme

npm version patch npm publish --access=public