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

awm

v0.1.0

Published

Alfred Workflow Manager, using packal.org

Downloads

30

Readme

awm npmV npmDown

Alfred Workflow Manager, using packal.org by Shawn Patrick Rice

Install

To install awm from npm, run:

$ npm install -g awm

Usage

$ awm -h

Usage: awm [options] [command]

  Commands:

    search <keyword>       Search workflows by keyword.
    info <bundleID>        Workflow general information.
    open <bundleID>        Open specified workflow's directory.
    home [bundleID]        Opens the workflow's Packal URL. Or Packal home if none specified.
    list                   List installed workflows.
    outdated               List outdated workflows.
    install <bundleID>     Install specified workflow.
    update                 Update the manifest file from packal.org.
    upgrade [bundleID]     Upgrade the specified package or all outdated ones if none specified.
    remove <bundleID>      Remove specified workflow.
    cleanup                Remove all cached downloads.
    reset                  Reset the manifest file from packal.org.

  Options:

    -h, --help     output usage information
    -V, --version  output the version number

Todo

  • Add tests
  • Support real install workflow (not download and open .alfredworkflow file).
  • Support real upgrade workflows (not download and open .alfredworkflow file).
  • Support upgrade ALL outdated.
  • ~~Support remove workflows.~~
  • Support bundle installing.

Note: one thing to consider when implementing real install and update is the previous stripping and migration of hotkeys and keywords.

Development

Pull requests are happily accepted. I have little time to finish the TODO list for the moment.

To link the awm command for development you'll need to fork and clone this project:

$ git clone https://github.com/<your-github-username>/awm

Then make npm link the awm command to the local project destination:

$ cd awm
awm$ npm link

This way you can invoke the awm command in the shell reflecting your local work.

If you wish to unlink from the local project:

$ npm r awm -g

I know, unlink should do the trick but no. (https://github.com/npm/npm/issues/4005)

License

Copyright (c) 2014 Jonathan Wiesel

MIT License

Contributors :heart: