Package Exports

@httptoolkit/osx-find-executable

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (@httptoolkit/osx-find-executable) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

osx-find-executable

Part of HTTP Toolkit: powerful tools for building, testing & debugging HTTP(S)

Find an app's executable on Mac.

This is a fork of https://github.com/juliangruber/osx-find-executable, which appears to now be unmaintained.

Key differences:

This fork includes a fallback (manually searching the apps in /Applications) if Spotlight is disabled, instead of just claiming that all apps can't be found.
This fork can also find an executable given a path to an app folder, not only using bundle id.
This fork returns promises throughout, and doesn't use callbacks.
This fork includes type definitions for TypeScript.

Installation

$ npm install @httptoolkit/osx-find-executable

Usage

const { findExecutableById } = require('@httptoolkit/osx-find-executable')

findExecutableById('com.google.Chrome').then((exec) => {
  // => /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
});

For more detailed examples, take a look at the tests in test.js

API

findExecutableById(id)

Takes a bundle id (like com.google.Chrome), finds the corresponding bundle on disk, and returns a promise for the path to the executable within.

findExecutableInApp(appPath)

Takes a path to an app bundle (a .app directory, like /Applications/Google Chrome.app), and returns a promise for the path to the executable within.

License

MIT