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

atom-package-manager

v2.6.5

Published

Atom package manager

Downloads

644

Readme

apm - Atom Package Manager

Build Status Dependency Status

Discover and install Atom packages powered by atom.io

You can configure apm by using the apm config command line option (recommended) or by manually editing the ~/.atom/.apmrc file as per the npm config.

Relation to npm

apm bundles npm with it and spawns npm processes to install Atom packages. The major difference is that apm sets multiple command line arguments to npm to ensure that native modules are built against Chromium's v8 headers instead of node's v8 headers.

The other major difference is that Atom packages are installed to ~/.atom/packages instead of a local node_modules folder and Atom packages are published to and installed from GitHub repositories instead of npmjs.com

Therefore you can think of apm as a simple npm wrapper that builds on top of the many strengths of npm but is customized and optimized to be used for Atom packages.

Installing

apm is bundled and installed automatically with Atom. You can run the Atom > Install Shell Commands menu option to install it again if you aren't able to run it from a terminal (macOS only).

Building

  • Clone the repository
  • :penguin: Install libsecret-1-dev (or the relevant libsecret development dependency) if you are on Linux
  • Run npm install; this will install the dependencies with your built-in version of Node/npm, and then rebuild them with the bundled versions.
  • Run ./bin/npm run build to compile the CoffeeScript code (or .\bin\npm.cmd run build on Windows)
  • Run ./bin/npm test to run the specs (or .\bin\npm.cmd test on Windows)

Why bin/npm / bin\npm.cmd?

apm includes npm, and spawns it for various processes. It also comes with a bundled version of Node, and this script ensures that npm uses the right version of Node for things like running the tests. If you're using the same version of Node as is listed in BUNDLED_NODE_VERSION, you can skip using this script.

Using

Run apm help to see all the supported commands and apm help <command> to learn more about a specific command.

The common commands are apm install <package_name> to install a new package, apm featured to see all the featured packages, and apm publish to publish a package to atom.io.

Two-factor authentication?

If you have 2fa enabled on your GitHub account, you'll need to generate a personal access token and provide that when prompted for your password.

Behind a firewall?

If you are behind a firewall and seeing SSL errors when installing packages you can disable strict SSL by running:

apm config set strict-ssl false

Using a proxy?

If you are using a HTTP(S) proxy you can configure apm to use it by running:

apm config set https-proxy https://9.0.2.1:0

You can run apm config get https-proxy to verify it has been set correctly.

Viewing configuration

You can also run apm config list to see all the custom config settings.