Skip to main content

​
Common issues

  • Local environment errors, check twenty local status and twenty local logs --no-follow. Docker must be installed and running with a local socket context. Add --test for the test instance. A failed start keeps its container and data for diagnosis.
  • Wrong Node version — Need 24.5+ or 26.5+ (engines.node: ^24.5.0 || ^26.5.1). Check with node -v.
  • Yarn 4 missing — Run corepack enable (on Node 26, first npm install -g corepack).
  • Dependencies broken — rm -rf node_modules && yarn install.
  • Empty yarn.lock — The build fails with “yarn.lock is empty” when the lockfile exists but has no content; run yarn install to regenerate it.
  • twenty-sdk errors after upgrading to v2.8.0 — It moved from dependencies to devDependencies in v2.8.0. See Project Structure → Dependencies.
  • twenty app build warns about twenty-client-sdk under dependencies — It is provided at runtime by Twenty, so it should be moved to devDependencies alongside twenty-sdk. See Project Structure → Dependencies.
Stuck? Ask on the Twenty Discord.