UNPKG

@onboardbase/cli

Version:

[![Version](https://img.shields.io/npm/v/@onboardbase/cli.svg)](https://www.npmjs.com/package/@onboardbase/cli) [![Downloads/week](https://img.shields.io/npm/dw/@onboardbase/cli.svg)](https://www.npmjs.com/package/@onboardbase/cli) [![License](https://img

19 lines (18 loc) 953 B
/** * Incase you're wondering why I'm passing a `HOME` environment variable? * * Here's why... * * Some unix OS like MacOS changes the `HOME` variable to /var/root once it's * being called from a LaunchDaemons/LaunchAgent plist file. * * This is because naturally, plist files have their own `HOME` directory/env which * is /var/root so nodejs `os.homedir()` basically depends on `process.env.HOME` meaning * once `process.env.HOME` is changed to another path, then `os.homedir()` just returns * that path be it the path that we need or not. * * Now to make sure we have access to the correct `HOME` directory where the `.onboardbase` * files are located, we need to manually override the `onboardbase.application.plist` file * and pass our own custom `HOME` path which is `os.homedir()` that is, the OS that compiled the CLI. */ export default function (ONBOARDBASE_WORKING_DIRECTORY: string, ONBOARDBASE_SERVICE_FILE: string): string;