@arcsine/process-win

@arcsine/process-win

Forked from active-win, by Sindre Sorhus

Get metadata about the window backing a process PID, or the active window. (title, id, bounds, owner, etc)

Works on macOS, Windows and X11-based Desktops (Linux, BSD). Wayland support is missing.

Install

$ npm install @arcsine/process-win

Usage

const * as processWin = require('@arcsine/process-win');

(async () => {
	console.log(await processWin.getActive());
	/*
	{
		title: 'Unicorns - Google Search',
		id: 5762,
		bounds: {
			x: 0,
			y: 0,
			height: 900,
			width: 1440
		},
		screens: [{
			x: 0,
			y: 0, 
			height: 920,
			width: 1440,
			index: 0
		}],
		owner: {
			name: 'Google Chrome',
			processId: 310,
			bundleId: 'com.google.Chrome',
			path: '/Applications/Google Chrome.app'
		},
		memoryUsage: 11015432
	}
	*/
})();

import * as processWin from '@arcsine/process-win';

...
console.log(await processWin.getActive());
...

...
console.log(await processWin.get(1000));
...

...
console.log(processWin.getActiveSync());
...

API

get(pid: number, platform?: string)

Returns a Promise<Object> with the result for the window tied to PID.

getActive(platform?: string)

Returns a Promise<Object> with the result for the active window.

getSync(pid: number, platform?: string)

Returns an Object with the result for the window tied to PID.

getActiveSync(platform?: string)

Returns an Object with the result for the active window.

Result

• title (string) - Window title
• id (number) - Window identifier
• bounds (Object) - Window position and size
  • x (number)
  • y (number)
  • width (number)
  • height (number)
• screens (Array) - Screens that overlap with the window
  • x (number)
  • y (number)
  • width (number)
  • height (number)
  • index (number) - Display index
• owner (Object) - App that owns the window
  • name (string) - Name of the app
  • processId (number) - Process identifier
  • bundleId (string) - Bundle identifier (macOS only)
  • path (string) - Path to the app (macOS and Windows only)
• memoryUsage (number) - Memory usage by the window (macOS only)

OS support

It works on macOS, Windows 7+, and X11-based desktops (Linux, BSD).

Note: On Windows, there isn't a clear notion of a "Window ID". Instead it returns the memory address of the window "handle" in the id property. That "handle" is unique per window, so it can be used to identify them. Read more….

Maintainers

• Sindre Sorhus
• Sebastián Ramírez
• Timothy Soehnlin

License

MIT