On test pipeline using default bitbucket-pipelines.yml i'm getting the following error: Error: Can't find a root directory while resolving a config file path. Provided path to resolve: test/config.json What could I do?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can't find a root directory while resolving a config file path on Jest tests.

lukaswilkeer

On test pipeline using default bitbucket-pipelines.yml i'm getting the following error:

<span><br>Provided path to resolve: test/config.json</span><span>Error: Can't find a root directory while resolving a config file path.</span>

What could I do?

Accepted answers

lukaswilkeer

Solved. It was a mistake.

All comments

lukaswilkeer

Solved. It was a mistake.

Marcella Del Tito

What was the mistake? I'm likely making the same one

Declan Shanaghy

Ya, post the solution. I'm hitting this error. I added a file to the list of setupFilesAfterEnv and now running into this

The file exists. I can't see any obvious link between adding a file to this config entry and suddenly not being able to determine the root dir

lukaswilkeer

This project is from years ago. Seeing the only project that runs jest I needed to set --config flag on the npm test task. In that case, this points to test/config.json.

Running it I don't see any problem.

@Declan Shanaghymaybe seting the --config option solved the issue. If you have any problems after this, try open an issue.

Mark Potter_24zz34

The silly mistake I was making was feeding in `--config jest.config.json` when my config file was actually js. Worth checking if google brought you here

Garrett Brustkern

Thank you 😅

Mitch Snyder _IOT_

This did the trick! My `package.json` file was looking for a js but I am using Typescript so it was TS.