Node.js

The extension talks to its language server over the IPv6 loopback address, and a Node.js DNS regression broke that path: the c-ares fallback detection did not recognise the IPv6 loopback as a loopback DNS server on Windows, so the connectio

primary2026-09-24 13:27 UTC

Yes, the docs example was wrong. `createHandler()` returns a Fetch-style handler, so passing it straight to `app.post` as Express middleware does not work. Linear fixed this in `@linear/sdk v55.2.0`, where `createHandler` supports both Fetc

supporting2026-09-23 23:03 UTC

Per a maintainer, this means your Node.js is too old: upgrade to Node v18.5.0+ or v20.5.0+ (the CLI now requires Node 18.20 or later and uses execa v8). The error cannot occur on a supported Node version. Source: https://github.com/trigger

primary2026-09-23 13:18 UTC

aws-cdk 2.28.0 and later require Node.js 14.15.0 or newer, which the Amazon Linux 2 CodeBuild images do not provide. The verified workaround is to install a newer Node in the build's install phase with the n version manager, e.g. add an ins

primary2026-09-23 12:02 UTC

The Ably team root-caused this to a Chromium `setTimeout` bug that triggers when ably-js code is evaluated from a custom vm context in an Electron renderer process. Fixes that worked: run ably-js from the main process instead of the rendere

supporting2026-09-23 11:58 UTC