NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4446 most downloaded on npm
https://linux.die.net/man/2/nice binding for Node.js
Last release 1 years ago
14 Aug 2025
Release timing varies
gaps range from 6 weeks to 10 months
Nearly every release is documented
notes for 5 of 5 stable releases
Nothing withdrawn
no release was ever pulled
2 years old
5 releases · first in 2024
One column per month.
feat: upgrade to NAPI-RS 3.0 stable by @Brooooooklyn in https://github.com/Brooooooklyn/nice/pull/10
Full Changelog: https://github.com/Brooooooklyn/nice/compare/v1.0.4...v1.1.1
fix: export WindowsThreadPriority on Windows by @Brooooooklyn in https://github.com/Brooooooklyn/nice/pull/9
Full Changelog: https://github.com/Brooooooklyn/nice/compare/v1.0.3...v1.0.4
ci: install prebuilt cargo-zigbuild by @Brooooooklyn in https://github.com/Brooooooklyn/nice/pull/5
Full Changelog: https://github.com/Brooooooklyn/nice/compare/v1.0.1...v1.0.2
chore: allow empty argument in nice function by @Brooooooklyn in https://github.com/Brooooooklyn/nice/pull/3
Full Changelog: https://github.com/Brooooooklyn/nice/compare/v1.0.0...v1.0.1
Get and set process priority on Unix and Windows via Node.js.
@napi-rs/niceGet and set process priority on Unix and Windows via Node.js.
niceOn Unix, nice() adds inc to the nice value for the calling process. (A higher nice value means a low priority.) Only the superuser may specify a negative increment, or priority increase. The range for nice values is described in getpriority(2).
On Windows, it uses the SetThreadPriority function.
// on Unix
import { nice } from '@napi-rs/nice'
nice(2)
// on Windows
import { nice, WindowsThreadPriority } from '@napi-rs/nice'
nice(WindowsThreadPriority.THREAD_PRIORITY_ABOVE_NORMAL)
getCurrentProcessPriorityThis function gets the priority of the current process.
On Unix, it uses the getpriority(2).
On Windows, it uses the GetThreadPriority function.
| Priority Constant | Value | Description |
|---|---|---|
| THREAD_MODE_BACKGROUND_BEGIN | 0x00010000 | Begin background processing mode. The system lowers the resource scheduling priorities of the thread so that it can perform background work without significantly affecting activity in the foreground. |
| This value can be specified only if hThread is a handle to the current thread. The function fails if the thread is already in background processing mode. | ||
| Windows Server 2003: This value is not supported. | ||
| THREAD_MODE_BACKGROUND_END | 0x00020000 | End background processing mode. The system restores the resource scheduling priorities of the thread as they were before the thread entered background processing mode. |
| This value can be specified only if hThread is a handle to the current thread. The function fails if the thread is not in background processing mode. | ||
| Windows Server 2003: This value is not supported. | ||
| THREAD_PRIORITY_ABOVE_NORMAL | 1 | Priority 1 point above the priority class. |
| THREAD_PRIORITY_BELOW_NORMAL | -1 | Priority 1 point below the priority class. |
| THREAD_PRIORITY_HIGHEST | 2 | Priority 2 points above the priority class. |
| THREAD_PRIORITY_IDLE | -15 | Base priority of 1 for IDLE_PRIORITY_CLASS, BELOW_NORMAL_PRIORITY_CLASS, NORMAL_PRIORITY_CLASS, ABOVE_NORMAL_PRIORITY_CLASS, or HIGH_PRIORITY_CLASS processes, and a base priority of 16 for REALTIME_PRIORITY_CLASS processes. |
| THREAD_PRIORITY_LOWEST | -2 | Priority 2 points below the priority class. |
| THREAD_PRIORITY_NORMAL | 0 | Normal priority for the priority class. |
| THREAD_PRIORITY_TIME_CRITICAL | 15 | Base priority of 15 for IDLE_PRIORITY_CLASS, BELOW_NORMAL_PRIORITY_CLASS, NORMAL_PRIORITY_CLASS, ABOVE_NORMAL_PRIORITY_CLASS, or HIGH_PRIORITY_CLASS processes, and a base priority of 31 for REALTIME_PRIORITY_CLASS processes. |
Your coding agent can read these notes before it upgrades. Set up the MCP server →