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

npm-js-alver

v1.0.2

Published

I don't know what to write for the first commit

Downloads

2

Readme

random-names

Whenever I start a new project, I don't know what to write for the first commit. After doing a “git init” there is technically nothing there...

Install

npm i npm-js-alver

Usage

random-names

Simular una instalacion

npm i react --dry-run

Forzar una instalacion

npm i -D webpack

Intalar una version especifica

npm i [email protected]

Visualizar el arbol genealogico de los paquetes instalados

npm list

Actualizar paquetes

Revisar que paquetes disponen de nuevas versiones

npm outdate

Para ver un output más detallado

npm outdate --dd

Actualizar los paquetes que no están en la ultima versión

npm update

Actualizar un paquete especifico

npm install json-server@latest

Eliminar paquetes

Eliminar un paquete de node_modules y del archivo package.json

npm uninstall json-server

Desinstalar un paquete de todo node_modules pero no del archivo package.json

npm uninstall webpack --no-save

Versionado 2.24.0

"moment": "^2.24.0"
2 => Major:
  • breaking change
24 => Minor (caret ^):
  • backwards compatible functionality.
  • old functionality deprecated, but operational.
  • large internal refactor
0 => Patch (tilde ~):
  • Bug fixes

Debug stack trace npm commando

npm run build --dd
Analizar dependencies con vulnerabilidad
npm audit

Revisar el log en modo json

npm audit --json

Actualizar una dependencies vulnerable a nivel de profundidad 2 donde tambien actualiza sus dependencias

npm update eslint-utils --depth 2

Actualizar todas las dependencies vulnerables

npm audit fix

Establecer una version

npm version patch, minor or major

Contributing

If someone wants to add or improve something, I invite you to collaborate directly in this repository: randon-names

License

randon-names is released under the MIT License.