The README and package.json say quak needs Node 22. Both install paths in the README fail on Node 22 releases.
Steps
Getting Started, on Node 22.12.0:
git clone https://git.eeqj.de/sneak/quak.git && cd quak && yarn install
Using the library, on Node 22.22.0 (the version in the repo's own pinned Dockerfile image), in a new project beside the built clone:
yarn add file:../quak
node example.mjs, where the file holds the README's example.
What happened
yarn install stops: error @inquirer/prompts@8.5.2: The engine "node" is incompatible with this module. Expected version ">=23.5.0 || ^22.13.0 || ^20.17.0". Got "22.12.0".
yarn add stops: error @inquirer/editor@5.4.0: The engine "node" is incompatible with this module. Expected version "^22.22.2 || ^24.15.0 || >=26.0.0". Got "22.22.0".
import { Client, Library } from "quak" fails with ERR_MODULE_NOT_FOUND.
Cause:
Getting Started installs from yarn.lock, whose @inquirer/prompts 8.5.2 needs Node 22.13.
A program that adds quak by path ignores quak's yarn.lock and resolves quak's dependency ranges afresh. It gets @inquirer/editor 5.4.0, released on 10 November 2026, which needs Node 22.22.2. Later releases can raise this again.
@inquirer/prompts serves only the prompts of quak login.
With --ignore-engines, the library example runs correctly on 22.22.0.
What should happen
Every Node version that the README's "The commands below need ..." sentence and engines.node in package.json allow runs both Getting Started and "Using the library" as written. The README sentence and engines.node state the same minimum.
Model: opus-5-5
The README and `package.json` say quak needs Node 22. Both install paths in the README fail on Node 22 releases.
## Steps
Getting Started, on Node 22.12.0:
1. `git clone https://git.eeqj.de/sneak/quak.git && cd quak && yarn install`
Using the library, on Node 22.22.0 (the version in the repo's own pinned `Dockerfile` image), in a new project beside the built clone:
2. `yarn add file:../quak`
3. `node example.mjs`, where the file holds the README's example.
## What happened
1. `yarn install` stops: `error @inquirer/prompts@8.5.2: The engine "node" is incompatible with this module. Expected version ">=23.5.0 || ^22.13.0 || ^20.17.0". Got "22.12.0"`.
2. `yarn add` stops: `error @inquirer/editor@5.4.0: The engine "node" is incompatible with this module. Expected version "^22.22.2 || ^24.15.0 || >=26.0.0". Got "22.22.0"`.
3. `import { Client, Library } from "quak"` fails with `ERR_MODULE_NOT_FOUND`.
Cause:
- Getting Started installs from `yarn.lock`, whose `@inquirer/prompts` 8.5.2 needs Node 22.13.
- A program that adds quak by path ignores quak's `yarn.lock` and resolves quak's dependency ranges afresh. It gets `@inquirer/editor` 5.4.0, released on 10 November 2026, which needs Node 22.22.2. Later releases can raise this again.
- `@inquirer/prompts` serves only the prompts of `quak login`.
With `--ignore-engines`, the library example runs correctly on 22.22.0.
## What should happen
Every Node version that the README's "The commands below need ..." sentence and `engines.node` in `package.json` allow runs both Getting Started and "Using the library" as written. The README sentence and `engines.node` state the same minimum.
Model: opus-5-5
clawbot
self-assigned this 2026-11-11 21:22:24 +01:00
#250 on branch issue-239-node-minimum: engines.node and the README now say Node 22.13, or 23.5 on Node 23. "Using the library" links the clone with yarn link, so the library runs on the dependencies from quak's yarn.lock and new upstream releases no longer change the minimum.
Model: opus-5-5
https://git.eeqj.de/sneak/quak/pulls/250 on branch `issue-239-node-minimum`: `engines.node` and the README now say Node 22.13, or 23.5 on Node 23. "Using the library" links the clone with `yarn link`, so the library runs on the dependencies from quak's `yarn.lock` and new upstream releases no longer change the minimum.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The README and
package.jsonsay quak needs Node 22. Both install paths in the README fail on Node 22 releases.Steps
Getting Started, on Node 22.12.0:
git clone https://git.eeqj.de/sneak/quak.git && cd quak && yarn installUsing the library, on Node 22.22.0 (the version in the repo's own pinned
Dockerfileimage), in a new project beside the built clone:yarn add file:../quaknode example.mjs, where the file holds the README's example.What happened
yarn installstops:error @inquirer/prompts@8.5.2: The engine "node" is incompatible with this module. Expected version ">=23.5.0 || ^22.13.0 || ^20.17.0". Got "22.12.0".yarn addstops:error @inquirer/editor@5.4.0: The engine "node" is incompatible with this module. Expected version "^22.22.2 || ^24.15.0 || >=26.0.0". Got "22.22.0".import { Client, Library } from "quak"fails withERR_MODULE_NOT_FOUND.Cause:
yarn.lock, whose@inquirer/prompts8.5.2 needs Node 22.13.yarn.lockand resolves quak's dependency ranges afresh. It gets@inquirer/editor5.4.0, released on 10 November 2026, which needs Node 22.22.2. Later releases can raise this again.@inquirer/promptsserves only the prompts ofquak login.With
--ignore-engines, the library example runs correctly on 22.22.0.What should happen
Every Node version that the README's "The commands below need ..." sentence and
engines.nodeinpackage.jsonallow runs both Getting Started and "Using the library" as written. The README sentence andengines.nodestate the same minimum.Model: opus-5-5
#250 on branch
issue-239-node-minimum:engines.nodeand the README now say Node 22.13, or 23.5 on Node 23. "Using the library" links the clone withyarn link, so the library runs on the dependencies from quak'syarn.lockand new upstream releases no longer change the minimum.Model: opus-5-5