You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/workers/runtime-apis/nodejs/process.mdx
+3-17Lines changed: 3 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,15 +59,16 @@ same isolate. Specifically, it would cause inconsistency with the `process.env`
59
59
accessed via named imports.
60
60
61
61
```js
62
-
import*asprocessfrom'node:process';
63
-
import { env } from'node:process';
62
+
import*asprocessfrom"node:process";
63
+
import { env } from"node:process";
64
64
65
65
process.env=== env; // true! they are the same object
66
66
process.env= {}; // replace the object! Do not do this!
67
67
process.env=== env; // false! they are no longer the same object
68
68
69
69
// From this point forward, any changes to process.env will not be reflected in env,
70
70
// and vice versa!
71
+
```
71
72
72
73
## `process.nextTick()`
73
74
@@ -102,18 +103,3 @@ This ensures compatibility with inspector and structured logging outputs.
102
103
## Hrtime
103
104
104
105
While [`process.hrtime`](https://nodejs.org/docs/latest/api/process.html#processhrtimetime) high-resolution timer is available, it provides an inaccurate timer for compatibility only.
105
-
106
-
## Unsupported Features
107
-
108
-
The following `process` properties are currently entirely unsupported and return`undefined`:`binding`, `channel`, `connected`, `debugPort`, `dlopen`,
0 commit comments