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

@devsito/prismapackagetest

v1.0.8

Published

## Correr docker

Downloads

80

Readme

@devsito/prismapackagetest

Correr docker

docker run -d --name tkstestdb -p 5555:5432 -e POSTGRES_PASSWORD=pass postgres

Flujos de trabajos

Modificación de la base de datos

Pasos a seguir cada vez que se modifica o altera la base de datos:

0- Modificar el schema.prisma con las nuevas implementaciones

1- Crear una nueva migración con doppler run yarn migrate:dev apuntando al entorno requerido

2- Commitear los cambios de la modificación del schema con su migración

3- Correr el script para publicar una nueva versión del paquete (se necesita tener limpio los cambios de git):

./publish.sh

Publicación de Nuevas Versiones

  1. Asegúrate de tener una cuenta en npm y estar autenticado:
npm login

2- Crear una nueva versión del paquete:

npm version patch
  1. Luego de cada modificación, asegúrate de hacer un commit y pushear tus cambios:
git add 
git commit -m "Descripción de la modificación"
git push

4- pushear los cambios incluidos los tags de versiones:

git push origin main --tags
  1. Buildear el paquete (se utiliza el dist/index.js como punto de entrada):
npm run build
  1. Publicar el paquete:
npm publish
  1. Actualiza el paquete en los repositorios donde se utiliza:
npm update @devsito/prismapackagetest