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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@emacs-eask/cli

v0.12.0

Published

A set of command-line tools to build Emacs packages

Readme

Eask

CLI for building, running, testing, and managing your Emacs Lisp dependencies

License: GPL v3 Emacs Version Release Discord

Eask was originally designed as a package development tool for Elisp projects. However, it has since expanded to support a wide range of Emacs Lisp tasks. It can now be used in three major ways:

  1. As a development tool for Elisp packages.
  2. For managing dependencies in your Emacs configuration.
  3. To run Elisp programs for a variety of purposes (essentially functioning as a runtime).

With these capabilities in mind, what sets Eask apart from other build tools like Cask, makem.sh, and Eldev?

Great question! Eask has evolved beyond just a build tool—it serves multiple purposes! Here’s what Eask aims to be:

  • Consistent: Provides a reliable sandboxing environment across all systems.
  • Versatile: Includes commonly used Emacs commands like byte-compilation, checkdoc, and more.
  • Robust: Delivers useful results even when user errors occur.
  • Lightweight: Runs on any platform without dependencies.

📝 P.S. See Why Eask? for more detailed information.

🔗 Links

💡 node is not required to use Eask!

🧪 Testing

We have incorporated a range of tests to ensure Eask remains stable throughout its release cycle.

Documentation

| Description | Done | Status | |----------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------| | Keep the documentation page up to date | ✔ | Docs |

Development

| Description | Done | Status | |--------------------------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------| | Compile source and check redefined | ✔ | Compile | | Compatibility check for each Emacs version | ✔ | Compat | | Build executables | ✔ | Build |

Commands

| Description | Done | Status | |----------------------------------------------|------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Test commands in global (~/.eask/) mode | ✔ | Global | | Test commands in config (~/.emacs.d/) mode | ✔ | Confg | | Test commands in development (./) mode | ✔ | Local | | Test install packages | ✔ | Install | | Test link packages | ✔ | Link | | Test analyze command / Eask-file checker | ✔ | Analyze | | Test docker command | ✔ | Docker | | Test exec command | ✔ | Exec | | Test emacs command | ✔ | Emacs | | Test search packages | ✔ | Search | | Test upgrade and check outdated packages | ✔ | Outdated_Upgrade | | Test upgrade-eask command | ✔ | Upgrade Eask |

Options

| Description | Done | Status | |----------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------| | Test option switches | ✔ | Options |

Test

| Description | Done | Status | |---------------------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Test ert command | ✔ | Test ert | | Test ert-runner command | ✔ | Test ert-runner | | Test buttercup command | ✔ | Test buttercup | | Test ecukes command | ✔ | Test ecukes |

Others

| Description | Done | Status | |-------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Webinstall | ✔ | Webinstall | | Exit Status | ✔ | Exit Status |

⚜️ License

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/.

See COPYING for details.