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

5082

v1.0.8

Published

Automated mitigation for NPM issue #5082.

Downloads

39

Readme

5082

Summary

NPM issue #5082 will break your repository and there is absolutely nothing you can do about except republish. This code automates detection and resolution. For background read the issue: https://github.com/npm/npm/issues/5082

Tested in production with package prettydiff starting with version v1.16.34. Package is written in vanilla JS works cross-OS.

Installation

Make these changes to your project's package.json:

  • Include 5082 as a devDependency
  • Add this path to scripts.publish NPM script, example: "publish": "node node_modules/5082/5082.js"
  • Add options (not required) to a new property config5082

Once that is complete run npm install within your project to install 5082 as a devDependency local to your package.

Options

There are three supported options:

  • beautify - A boolean indicating whether the
  • files - an array to store paths for additional files in your repo that may contain version numbers that might also need to be bumped. The files should be a relative path from your project's package.json file. No need to include package.json in this list. It will be corrected anyways. If you do include it by accident it will not be processed twice.
  • options - An object storing configurations for beautification. The supported beautifier is Pretty Diff.

Execution path

  1. Get the options from your package.json file
  2. Remove the temporary directory specified in the next step (just in case it is already there)
  3. mkdir ../packageName5082/node_modules
  4. cd ../packageName5082/node_modules
  5. npm install packageName
  6. fs.readFile("package.json") gather version and main
  7. fs.readdir(packageName) see if main file is present
  8. If main file is present then remove ../packageName5082 directory and exit
  9. If main file is absent the bump version number in package.json
  10. Bump the version number in other specified files and write them to disk
  11. Optionally beautify package.json before writing to disk
  12. Write package.json to disk
  13. publish package
  14. run this application again recursively (let's hope you don't get a 5082 error twice in a row)

License

MIT License