// troubleshooting guide · pulsar
Pulsar Packages Not Working
- Status
- Ongoing
- platforms:
- Windows, macOS, Linux
- updated:
- November 15, 2026
- reports:
- 3
- Method
- how we research
RUNBOOK · pulsar/packages-not-working4 FIXES
// quick answer
Packages using native Node modules can break after Pulsar's Electron upgrade. Click the incompatible-packages icon and rebuild, or replace the package.
Most likely fix: Rebuild from the status bar icon
How to fix it
// try these in order, the most common fix is first
FIX 1Rebuild from the status bar icon
- 01Click the incompatible-packages indicator in the status bar
- 02Click Rebuild Packages if enabled
- 03Reload the window or restart Pulsar
Did this fix it?FIX 2Check build tools
- 01Run ppm install --check in a terminal
- 02If distutils is missing install Python setuptools
- 03Rebuild again
Did this fix it?FIX 3Use a maintained fork or replacement
- 01Search the Pulsar package registry for a fork (e.g. hydrogen-next replaces hydrogen)
- 02Disable the old package
Did this fix it?FIX 4Report non-context-aware module errors
- 01If you see 'non-context-aware module in renderer', report it in the Electron 30 megathread on GitHub (issue 1383)
Did this fix it?
Symptoms
A package fails to load, or an incompatible-packages icon shows in the status bar.
Why it happens
- C-01Native Node module built for an old Electron
- C-02Package unmaintained
- C-03Missing build tools
// this guide also covers
- pulsar packages not working
- pulsar incompatible packages
- atom packages not working in pulsar
Still not working?
If Pulsar keeps failing, you're not alone. See every Pulsar problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to us