Is there any terminal package that works for macOS?

[stefaniecg]

I've tried a few terminal packages, but they do not work in my macOS Pulsar.
They do work in my Linux Pulsar though.

[savetheclocktower]

If you haven't yet, can you follow the instructions on this page and make sure that everything works properly?

If so, you should be able to install x-terminal-reloaded.

If that doesn't work, please copy and paste the error message you got when it failed to install so we can troubleshoot why it's not working.

[stefaniecg]

x-terminal-reloaded worked great !
thank u so much !

[froggygbs]

Followed https://docs.pulsar-edit.dev/getting-started/dependencies-for-some-community-packages/#tell-ppm-about-the-path-to-your-version-of-python

Still couldn't install x-terminal-reloaded (macOS Tahoe 26.3)

Got the following messages:

ppm install x-terminal-reloaded
Installing x-terminal-reloaded to /Users/haraldhollmann/.pulsar/packages ✗

npm ERR! prepareGitDep 1>
npm ERR! prepareGitDep > @pulsar-edit/node-pty@1.0.0-beta34-pulsar install /Users/haraldhollmann/.pulsar/.apm/_cacache/tmp/git-clone-830c4ffe
npm ERR! prepareGitDep > node-gyp rebuild
npm ERR! prepareGitDep
npm ERR! prepareGitDep
npm ERR! prepareGitDep TOUCH Release/obj.target/node_modules/node-addon-api/node_addon_api_except.stamp
npm ERR! prepareGitDep CXX(target) Release/obj.target/pty/src/unix/pty.o
npm ERR! prepareGitDep SOLINK_MODULE(target) Release/pty.node
npm ERR! prepareGitDep CXX(target) Release/obj.target/spawn-helper/src/unix/spawn-helper.o
npm ERR! prepareGitDep LINK(target) Release/spawn-helper
npm ERR! prepareGitDep
npm ERR! prepareGitDep > @pulsar-edit/node-pty@1.0.0-beta34-pulsar postinstall /Users/haraldhollmann/.pulsar/.apm/_cacache/tmp/git-clone-830c4ffe
npm ERR! prepareGitDep > node scripts/post-install.js
npm ERR! prepareGitDep
npm ERR! prepareGitDep > Cleaning release folder...
npm ERR! prepareGitDep > Moving conpty.dll...
npm ERR! prepareGitDep SKIPPED (not Windows)
npm ERR! prepareGitDep
npm ERR! prepareGitDep > @pulsar-edit/node-pty@1.0.0-beta34-pulsar prepare /Users/haraldhollmann/.pulsar/.apm/_cacache/tmp/git-clone-830c4ffe
npm ERR! prepareGitDep > npm run build
npm ERR! prepareGitDep
npm ERR! prepareGitDep
npm ERR! prepareGitDep 2> npm WARN install Usage of the --dev option is deprecated. Use --also=dev instead.
npm ERR! prepareGitDep npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@3. I'll try to do my best with it!
npm ERR! prepareGitDep npm WARN deprecated eslint@6.8.0: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm ERR! prepareGitDep npm WARN deprecated tar@6.2.1: Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm ERR! prepareGitDep npm WARN deprecated glob@10.5.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm ERR! prepareGitDep npm WARN deprecated glob@8.1.0: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm ERR! prepareGitDep npm WARN deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm ERR! prepareGitDep npm WARN deprecated glob@7.2.3: Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me
npm ERR! prepareGitDep npm WARN deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
npm ERR! prepareGitDep ../src/unix/pty.cc:136:30: warning: missing field 'filter' initializer [-Wmissing-field-initializers]
npm ERR! prepareGitDep 136 | struct kevent change = {0};
npm ERR! prepareGitDep | ^
npm ERR! prepareGitDep ../src/unix/pty.cc:156:31: warning: missing field 'filter' initializer [-Wmissing-field-initializers]
npm ERR! prepareGitDep 156 | struct kevent event = {0};
npm ERR! prepareGitDep | ^
npm ERR! prepareGitDep 2 warnings generated.
npm ERR! prepareGitDep sh: npm: command not found
npm ERR! prepareGitDep npm ERR! code ELIFECYCLE
npm ERR! prepareGitDep npm ERR! syscall spawn
npm ERR! prepareGitDep npm ERR! file sh
npm ERR! prepareGitDep npm ERR! errno ENOENT
npm ERR! prepareGitDep npm ERR! @pulsar-edit/node-pty@1.0.0-beta34-pulsar prepare: npm run build
npm ERR! prepareGitDep npm ERR! spawn ENOENT
npm ERR! prepareGitDep npm ERR!
npm ERR! prepareGitDep npm ERR! Failed at the @pulsar-edit/node-pty@1.0.0-beta34-pulsar prepare script.
npm ERR! prepareGitDep npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! prepareGitDep
npm ERR! prepareGitDep npm ERR! A complete log of this run can be found in:
npm ERR! prepareGitDep npm ERR! /Users/haraldhollmann/.pulsar/.node-gyp/.npm/_logs/2026-03-02T17_22_45_309Z-debug.log
npm ERR! prepareGitDep
npm ERR! premature close

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/haraldhollmann/.pulsar/.apm/_logs/2026-03-02T17_22_45_329Z-debug.log

This is what I get when I type:
ppm --version
ppm 2.7.0
npm 6.14.19-pulsar2
node 20.11.1 arm64
pulsar 1.131.1
python 3.13.12
git 2.50.1

Can anyone please help?

[savetheclocktower]

This is because of node-pty incorrectly assuming that it can run npm and it will be present. Some users will have npm installed, but many others won't.

One workaround would be to install Node globally, even if only temporarily; this would allow the npm command to work. Another would be to make a dummy npm script and put it somewhere in your PATH so that a call to npm will just silently succeed rather than error.

The first option is better if you're a novice; the second option is sillier, but probably more appealing if you're comfortable with the command line.

If you need help with either one, reply on this answer and I'll walk you through it.

We hope to ship a built-in terminal package very soon in order to make all of this easier.