Atom Activation Command Precedence When Multiple Packages Register Identical Commands

Answer

When two or more Atom packages register the same activation command, the handler from the package that registers the command last during the activation phase wins; Atom’s command registry stores a single reference per command string, so earlier registrations are overwritten.

Confirmed facts

• Atom’s command registry maps command names to a single handler function.
• Registering a command with an existing name replaces the previous handler.
• Activation order follows the order in which core loads packages at startup.
• Package load order is primarily alphabetical by the package directory name, though internal dependencies can shift it.
• There is no built‑in priority or weight attribute in the standard command registration API.

Likely explanation

Because the registry is a simple map, the last writer wins. The observed precedence therefore mirrors the package loading sequence. If two packages have no dependency relationship, the one whose directory name sorts later alphabetically will typically be loaded after the other and thus take precedence.

Steps to verify or control the behavior

1. Open Atom → View → Developer → Open Dev Tools.
2. In the console, inspect atom.commands.findHandlers('your:command') to see the current handler.
3. Create two test packages that each register the same command and log a message when the handler runs.
4. Reload Atom and note which package’s log appears; that is the winner.
5. To change the outcome, rename one package’s folder so its alphabetical order changes, or add a package dependency via package.json’s activatedCommands or dependencies field to force a load order.
6. If you need deterministic behavior, avoid overriding core commands; instead, call the original handler from within your package or use a unique command name.

Missing diagnostic detail

If you need to predict which package will win without trial‑and‑error, provide the exact list of package directory names (or their package.json names) as they appear in ~/.atom/packages. Knowing the alphabetical order (or any declared dependencies) lets you determine the loading sequence and thus the winning handler.