Atom Package Install Fails (apm Error)

How to fix it

// try these in order, the most common fix is first

1. FIX 1Read the real error

   Copy steps
   1. 01Run apm install <package> in a terminal
   2. 02Look at the first npm ERR! line
   Did this fix it? Yes No

2. FIX 2Fix environment issues

   Copy steps
   1. 01Install Git and required build tools
   2. 02On Windows close antivirus or retry after clearing the temp folder for EPERM
   3. 03Check proxy settings
   Did this fix it? Yes No

3. FIX 3Install from GitHub

   Copy steps
   1. 01Run: apm install owner/repo
   2. 02Useful when the registry returns errors
   Did this fix it? Yes No

4. FIX 4Use Pulsar instead

   1. 01Pulsar has a new package repository backend and clearer install errors
   Did this fix it? Yes No

Symptoms

Installing a package from Settings or apm install shows an error, timeout, EPERM or HTTP 500.

Why it happens

• C-01The original Atom package backend is no longer maintained
• C-02Network, proxy or SSL timeouts (ETIMEDOUT)
• C-03Windows EPERM file permission errors during rename
• C-04Missing Git or build tools (python, gyp) for native packages

// this guide also covers

• atom can't install packages
• apm install failed
• atom package install error
• atom packages not installing

The same problem in other apps

All not loading, error messages & connection guides →

• VS Code Python Interpreter Not Found (VS Code)
• Pulsar ppm Install Error (Pulsar)
• Sublime Text Package Control Error 12029 and 12057 on Windows (Sublime Text)
• Zed Vulkan Error on Linux (NoSupportedDeviceFound) (Zed)
• Vim Requires Python 3 Support Error (YouCompleteMe) (Vim)

Other Atom errors

• Atom Shut Down: What to Use Instead
• Is Atom Editor Dead? Can You Still Use It
• How to Migrate From Atom to VS Code
• How to Migrate From Atom to Pulsar
• Atom Not Opening or Won't Start
• Atom "The Editor Has Crashed" Error
• Atom "Failed to Load" or "Failed to Activate" Package Error
• Why Is Atom So Slow or Using High CPU