Cannot find package root when ts-jest is symlinked instead of being installed

[KSXGitHub]

This line of code is supposed to find package root, it works when I install ts-jest using yarn or npm but doesn't when I use pnpm.

Unlike npm and yarn, pnpm wants to save disk space by symlinking packages from node_modules/.registry.npmjs.org to node_modules. This makes package root not ../../ relative to ts-jest but ../../../../ relative to ts-jest causing it to print warnings.

Suggestion

Instead of just assuming package root to be in ../../, search for package root in every ancestor directory starting with ../.

...

BTW, I have a package that lists all ancestor directories.

[huafu]

That is a bug I was waiting for someone to report... I meant, I have it in mind, but never got the time to report neither fix.

Instead of just assuming package root to be in ../../, search for package root in every ancestor directory starting with ../.

Actually, not only. I meant, it's a bit more complex. For example in monorepo using yarn workspaces, the package.json of the related project (not the root one) is in ../../somewhere-usually-named-packages/the-package-name/package.json

[KSXGitHub]

Actually, not only. I meant, it's a bit more complex. For example in monorepo using yarn workspaces, the package.json of the related project (not the root one) is in ../../somewhere-usually-named-packages/the-package-name/package.json

I think there're a few solutions to this:

• Making package root configurable from jest.config.js.
• Package root is whatever contains jest.config.js.

[huafu]

Package root is whatever contains jest.config.js.

• I have, and because I followed a tutoral so I am not the only one, all my config files in another dir:

config/
  jest.config.js
packages/
  a/
    package.json {scripts: {test: 'jest --config ../../config/jest.config.js'}}

• You CANNOT know in all cases where is that jest.config.js from what Jest gives you as a transformer

Making package root configurable from jest.config.js.

Best solution so far. When we cannot find the package.json, show a warning which explains about this config.

There is also a node package which allow to find that package.json, I can't remember its name, but I do remember it is written in the readme that it does not find it in 100% of the cases, even tho it's not just a lookup in parents

[dhl]

Very interesting discussion here highlighting the nuances of the config lookup.

I wonder if the problem can be simplified by introducing some assumptions here. For example, according to TypeScript's documentation, tsconfig.json marks the root of a TypeScript project:

The presence of a tsconfig.json file in a directory indicates that the directory is the root of a TypeScript project
Source

With the root of the project found, the jest.config.js file can be resolved by having the path looked up in the project root, or in a ts-jest config file or setting in package.json.

[KevinTCoughlin]

I'm also running into this warning similar to the above and @octogonz in #852. Has there been any resolution? Is this something that a contributor could fix?

[lonix1]

I see the fix is merged, but the docs are not showing the changes yet...