bun-types 1.1.2 → 1.1.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bun.d.ts +11 -4
- package/package.json +1 -1
package/bun.d.ts
CHANGED
|
@@ -3105,12 +3105,19 @@ declare module "bun" {
|
|
|
3105
3105
|
}
|
|
3106
3106
|
|
|
3107
3107
|
/**
|
|
3108
|
-
*
|
|
3108
|
+
* Returns the number of nanoseconds since the process was started.
|
|
3109
3109
|
*
|
|
3110
|
-
* This uses a high-resolution monotonic system timer.
|
|
3110
|
+
* This function uses a high-resolution monotonic system timer to provide precise time measurements.
|
|
3111
|
+
* In JavaScript, numbers are represented as double-precision floating-point values (IEEE 754),
|
|
3112
|
+
* which can safely represent integers up to 2^53 - 1 (Number.MAX_SAFE_INTEGER).
|
|
3111
3113
|
*
|
|
3112
|
-
*
|
|
3113
|
-
*
|
|
3114
|
+
* Due to this limitation, while the internal counter may continue beyond this point,
|
|
3115
|
+
* the precision of the returned value will degrade after 14.8 weeks of uptime (when the nanosecond
|
|
3116
|
+
* count exceeds Number.MAX_SAFE_INTEGER). Beyond this point, the function will continue to count but
|
|
3117
|
+
* with reduced precision, which might affect time calculations and comparisons in long-running applications.
|
|
3118
|
+
*
|
|
3119
|
+
* @returns {number} The number of nanoseconds since the process was started, with precise values up to
|
|
3120
|
+
* Number.MAX_SAFE_INTEGER.
|
|
3114
3121
|
*/
|
|
3115
3122
|
function nanoseconds(): number;
|
|
3116
3123
|
|
package/package.json
CHANGED