@whalent/agent 0.3.298 → 0.3.302
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/README.md +6 -0
- package/dist/core.cjs +7 -7
- package/dist/index.cjs +1 -1
- package/package.json +2 -4
- package/scripts/preinstall-check.cjs +0 -19
package/README.md
CHANGED
|
@@ -22,6 +22,12 @@ Node.js 20 is still the safest choice on older Linux hosts. Newer Node.js
|
|
|
22
22
|
releases can force native `node-pty` fallback builds that need newer C++
|
|
23
23
|
compilers when prebuilt binaries are unavailable.
|
|
24
24
|
|
|
25
|
+
Self-updates stay in the npm prefix that owns the running `whalent` command,
|
|
26
|
+
verify that prefix before restarting, and explicitly allow only the reviewed
|
|
27
|
+
`node-pty` and `ssh2` lifecycle scripts required by the runtime. The Whalent
|
|
28
|
+
packages themselves rely on the `engines` declaration and do not run install
|
|
29
|
+
hooks.
|
|
30
|
+
|
|
25
31
|
The HTTP, HTTPS, and SOCKS proxy paths are regression-tested on Node.js 20 and
|
|
26
32
|
Node.js 26. Whalent keeps its `fetch` implementation and custom dispatchers on
|
|
27
33
|
the same bundled Undici version so Node runtime upgrades do not break proxies.
|