Export resident set size function

The memRSS function gets the resident or working set size of the process's memory. This will generally be a better count of the memory solely used by the process (particularly on MacOS which otherwise counts the entire addressable space even if not allocated), but will not include 'virtual' memory.

Full Changelog: v1.4.0...v1.4.1

v1.4.0

What's Changed

• Bump http-cache-semantics from 4.1.0 to 4.1.1 by @dependabot in #2
• Add darwin-arm64 support (Apple Silicon)

Full Changelog: v1.3.1...v1.4.0

v1.3.1

What's Changed

• Bump minimist from 1.2.5 to 1.2.8 by @dependabot in https://github.com/2kai2kai2/node-ps-data/p
• Fixed bug with npm run scripts' path not being portable.

Full Changelog: v1.3.0...v1.3.1

v1.3.0

File IO Stats

Added functions for retrieving total number of bytes read and written by a process.

---

Details

Windows:
Using GetProcessIoCounters() from <WinBase.h> with PROCESS_QUERY_LIMITED_INFORMATION permissions.

Linux:
Using the /proc/[pid]/io filesystem, which may require permissions.

MacOS:
Using proc_pid_rusage() from <libproc.h>.

v1.2.0

MacOS Implementation

Details:
Using <libproc.h> function proc_pidinfo(PROC_PIDTASKINFO) we get data on MacOS process resource consumption.
The function is first available starting with MacOS 10.5 (Leopard), according to the header file.

Note that proc_pid_rusage() does not include full virtual memory usage, and was thus not used in the end.

v1.1.1

Ensuring consistency between Windows and Linux memory data.

Details:
Windows
Use "total memory" as sum of working set size and pagefile usage
Using system file psapi.h: sum of PROCESS_MEMORY_COUNTERS::WorkingSetSize and PROCESS_MEMORY_COUNTERS::PagefileUsage

Linux
Use /proc/[pid]/statm size (1)

v1.1.0

Add functions cpuUserTime(pid) and cpuKernelTime(pid) which get their respective portions of process CPU time. Their sum is equal to the value returned by cpuTime(pid).

v1.0.12

GitHub Actions Now Functional

Basically, npm publish was ignoring our prebuilds due to being in .gitignore, but now we have a separate .npmignore which takes precedence on publishing so we have separate ignores for git and the npm build.

Prebuildify with GitHub Actions

v1.0.11

Fix issues in npm-publish.yml