When I install "@testing-library/react": "^11.2.5" in an existing project with tslint, I get missing kcd-scripts warning

[justin-calleja]

• @testing-library/react: 11.2.5
• Testing Framework and version: jest at 26.6.3
• DOM Environment: jsdom at 11.12.0

What you did:

install "@testing-library/react": "^11.2.5" via adding directly in package.json and lerna bootstrap.

What happened:

Cannot read file '.../node_modules/@testing-library/react/node_modules/kcd-scripts/shared-tsconfig.json'.

Problem description:

A dependency of react-testing-library is not being installed. In react-testing-library's package.json:

 "eslintConfig": {
    "extends": "./node_modules/kcd-scripts/eslint.js",

So my editor now requires the existance of that eslint.js file.

Suggested solution:

Add the missing kcd-scripts in dependencies of react-testing-library.

When I install kcd-scripts alongside @testing-library/react in my package devDependencies (and restart TS server in vs code), then the error goes away. But I would expect that the expected behaviour is to just install @testing-library/react and not get the error in the first place 🙂

[MatanBobi]

Hi @justin-calleja, thanks for taking the time to open this :)
It looks like you're looking for the shared-tsconfig.json which is being used in our tsconfig.
The eslint configs you've added here are there for a few years now and nothing was changed there. Also, the eslint+tsconfig are only used as a dev dependency..
Can you please add your tsconfig so we'll be able to look into what's going on and why you're trying to load the shared-tsconfig.json file?

[ryan-rushton]

Hi I am seeing something similar

Cannot read file '/Users/ryanrushton/dev/my-project/node_modules/@testing-library/react/node_modules/kcd-scripts/shared-tsconfig.json'.

This is what the @testing-library package in my node_modules looks like

And this is my tsconfig.json

{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",
    "baseUrl": "src",
    "noFallthroughCasesInSwitch": true
  },
  "include": [
    "src"
  ]
}

[MatanBobi]

Thanks @ryan-rushton, This Issue is fixed in version 11.2.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release