Storing in /Users/vanishaagrawal/Library/Application Support/ActivityTracker-nodejs/activity (node:15864) UnhandledPromiseRejectionWarning: Error: spawn /snapshot/Cross-Platform-Activity-Tracker/node_modules/.pnpm/active-win@7.6.1/node_modules/active-win/main ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:82:21) (Use `index-macos --trace-warnings ...` to show where the warning was created) (node:15864) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:15864) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:15864) UnhandledPromiseRejectionWarning: Error: spawn /snapshot/Cross-Platform-Activity-Tracker/node_modules/.pnpm/active-win@7.6.1/node_modules/active-win/main ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:82:21) (node:15864) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2) (node:15864) UnhandledPromiseRejectionWarning: Error: spawn /snapshot/Cross-Platform-Activity-Tracker/node_modules/.pnpm/active-win@7.6.1/node_modules/active-win/main ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:82:21) (node:15864) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3) (node:15864) UnhandledPromiseRejectionWarning: Error: spawn /snapshot/Cross-Platform-Activity-Tracker/node_modules/.pnpm/active-win@7.6.1/node_modules/active-win/main ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:82:21) (node:15864) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4) (node:15864) UnhandledPromiseRejectionWarning: Error: spawn /snapshot/Cross-Platform-Activity-Tracker/node_modules/.pnpm/active-win@7.6.1/node_modules/active-win/main ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19) at onErrorNT (internal/child_process.js:467:16) at processTicksAndRejections (internal/process/task_queues.js:82:21) (node:15864) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 5) ^C (base) vanishaagrawal@vanisha1 build % cd Users/vanishaagrawal/Library/Application Support/ActivityTracker-nodejs/activity cd: string not in pwd: Users/vanishaagrawal/Library/Application (base) vanishaagrawal@vanisha1 build % cd /Users/vanishaagrawal/Library/Application Support/ActivityTracker-nodejs/activity cd: string not in pwd: /Users/vanishaagrawal/Library/Application