yarn develop -> Cannot destructure property 'client' of 'db.config.connection' as it is undefined

[vitakili]

Full error log even after --debug is ->
│ TypeError: Cannot destructure property 'client' of 'db.config.connection' as it is undefined. │
│ at getDialect (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\database\dist\index.js:1014:11) │
│ at new Database (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\database\dist\index.js:6114:20) │
│ at Database.init (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\database\dist\index.js:6100:16) │
│ at Strapi.bootstrap (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\strapi\dist\Strapi.js:365:39) │
│ at Strapi.load (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\strapi\dist\Strapi.js:419:16) │
│ at async Object.develop (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\admin\dist_chunks\index-cce8ecb6.js:1160:28) │
│ at async develop (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\admin\dist_chunks\develop-69e28e61.js:52:5) │
│ at async Command.parseAsync (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules\commander\lib\command.js:923:5) │
│ at async Module.runStrapiCommand (D:\nextjs_strapi\vita-multilang\portfolio-backend\node_modules@strapi\strapi\dist\commands\index.js:124:3)
-->

Bug report

• Node.js version: v18.18.2
• Yarn version: 1.22.19
• Strapi version:4.13.6/4.15.4 (doesn't matter -> both same error)
• Database: postgres
• Operating system: win32-x64
• Is your project Javascript or Typescript: ts

Steps to reproduce the behavior

1. type yarn build && yarn develop
2. look at error
3. 8 times delete node_modules and change versions of Strapi
4. See error again

Expected behavior

Development server -> localhost:1337

[github-actions]

This is a templated message

Hello @vitakili,

I see you are wanting to ask a question that is not really a bug report,

• questions should be directed to our forum or our Discord
• feature requests should be directed to our feedback and feature request database

Please see the following contributing guidelines for asking a question here.

Thank you.

[djakaitis]

@vitakili Were you able to find a solution to this? We are experiencing this in our local development environment.

[zguig52]

@djakaitis seems the doc is KO.

[exotexot]

The same issue also exists in the JS version ...

[sebammon]

We're experiencing this issue when running tests for strapi using jest.

[parsagholipour]

Same experience

[jhsu98]

also running into this trying to use jest locally

[shfx]

I found that when you use TS, Strapi is looking for a dist dir (the one from tsconfig.json) while looking for the config. I was trying to tinker with tsconfig.json and enabled "noEmit". This resulted in a similar situation. Hope that helps. You might have typescript pipeline broken for some reason.

[richardgotthard]

Facing same problem, anyone have an update on this with typescript.

[sebammon]

FWIW, I was able to solve this issue for the case of running strapi programmatically when testing with jest. As @shfx mentioned, when you use TS, Strapi is looking for a dist dir. So following the docs:

const Strapi = require("@strapi/strapi");

async function setupStrapi() {
  ...
-  await Strapi().load();
+  await Strapi.compile().then((appContext) => Strapi(appContext).load());
  ...
}

[gilliardmacedo]

It happened to me when I was launching an existing project into another repo and another environment. My gitignore template removed tsconfig.json so it didn't exist in CI environment. Removing that line from gitignore solved it

[sfarkas1988]

I can confirm that this issue exists only when using strapi with TS.
I can reproduce it by:

yarn build && node server.js

It does not work when strapi is initiated with TS.
It does work when strapi is initiated without TS.