node
node copied to clipboard
Node.js JavaScript runtime ✨🐢🚀✨
Main change that affects us: https://github.com/v8/v8/commit/12203e0c46b507dc138047c0fe22ce254bfced91 ~I still need help to solve at least https://github.com/nodejs/node-v8/issues/272~ fixed.
### Test `test/parallel/test-zlib-brotli-16GB.js` ### Platform AIX ### Console output ```console 17:07:37 not ok 3588 parallel/test-zlib-brotli-16GB 17:07:37 --- 17:07:37 duration_ms: 412.84800 17:07:37 severity: fail 17:07:37 exitcode: 1 17:07:37 stack: |- 17:07:37...
This commit is the result of reverting the v5.28.3 security update and then cleanly cherry-picking all 6.x updates from `main` until 6.6.2, which also includes the security fix. Reverts: 9d2ac2b3fcf41c33ba81a83aae2879df0685edcb...
How should I upgrade? [root@VM-0-17-centos bin]# node -v node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by node) node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by node) node: /lib64/libc.so.6: version `GLIBC_2.28'...
Currently the dot reporter prints white dots and white X. I think it should print green dots and red X.
- **Version**: v.6.3.1 - **Platform**: Linux (Ubuntu 14.04) - **Subsystem**: `repl` (I think) ``` let s = Set(); ``` gives `TypeError: Constructor Set requires 'new'`. However, after this: ``` s...
Fixes #51001 undici will already work once this change lands.
Fixes: https://github.com/nodejs/node/issues/51714
Because the previous security release modified the bundled version of libuv, we cannot automatically update libuv without potentially undoing those changes. cc: @nodejs/security-wg
I have recently read the article about Olipan: https://v8.dev/blog/oilpan-library. It might be worthwhile investigating if it's something we could use inside Node.js C++ internals to simplify some of our memory...