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

@voodeng/uppacks

v0.3.1

Published

Pack your folder, up version use some cli tools

Downloads

3

Readme

@voodeng/uppacks

There has Some documentation and packaging tools

Maybe these tools are not perfect, but they can make your build process more convenient.

Intro

npm i -D @voodeng/uppacks

now, u can use two cli-tools: uparchive & upversion

uparchive

this pack is use archiver, it can archive target floder to target path.

  • create folder if not exits.
  • create .gitignore in folder.
  • generate version.json with git repo info to dist folder.
  • archive dist to the target folder.
Usage: 
npx uparchive --dist [DIST] --target [TARGET]

Options:
  -h, --help     Show help                                             [boolean]
  -d, --dist     Production env compiled folder. `/dist`
  -t, --target   Target folder, place the archive file. `/Archives`
  -v, --version  Show version number 

in package.json

{
  "scripts": {
    "archive": "uparchive --dist ./build --target ./Archives"
  }
}

upversion

this pack is base on standard-version, so you can use same options.

other, you can:

  • Replace the log default file header
  • Copy log file to target path
  • add a package.json field name updateTime to current time
  • default skip commit and tag
Usage: 
npx upversion --infile [CHANGELOG] --noskip --release-as [BUMP] --first-release --dry-run

Options:
  --infile       Changelog.md file pathname. `./ptah/filename`
  --noskip       all standard version default flow.
  --release-as   Package.json version bump type. `| major | minor | patch |
                 premajor | preminor | prepatch | prerelease
                 [--preid=<prerelease-id>] | from-git`
  --cpto         Copy to target file pathname. `./path/filename`
  --header       Replace log file header. `--header "# HEAD STRING\n\n descstring some"`

in package.json

{
  "scripts": {
    "version": "upversion --cpto ./doc/log.md --header '# HEAD STRING\n\n descstring some'"
  }
}