v2.23 causes no-extraneous-dependencies errors for related @types/ packages that aren't imported

[neefrehman]

Since upgrading to v2.23 I'm seeing lot's of errors in my TypeScript codebase related to @types dependencies, even though they are not directly being imported. for example:

import React from "react";
import * as THREE from "three";
import { OrbitControls } from "three/examples/jsm/controls/OrbitControls";

Is throwing:

  3:1  error  '@types/react' should be listed in the project's dependencies, not devDependencies  import/no-extraneous-dependencies
  4:1  error  '@types/three' should be listed in the project's dependencies, not devDependencies  import/no-extraneous-dependencies
  5:1  error  '@types/three' should be listed in the project's dependencies, not devDependencies  import/no-extraneous-dependencies

[marjorg]

Can confirm this. Reverting to 2.22.1 for now

[buu700]

Possibly related issue: I'm now getting error 'rxjs/operators' should be listed in the project's dependencies. Run 'npm i -S rxjs/operators' to add it import/no-extraneous-dependencies, with rxjs/operators being a path within the rxjs package.

[ljharb]

I believe this may be a duplicate of #2065, and possibly related to #2058.

[JuanpaG94]

Can confirm this. Not only for @types/ dependencies but everything that has other packages inside the dependency.
For example styled-components/native or similar.

Possible workarounds are:

1. Reverting to 2.22.1 for now
2. Adding 'import/no-extraneous-dependencies': 'off' to your eslint rules

[sachinraja]

Thanks for reporting this! I thought I was going crazy 😆. For me, @types dependencies are erroring, specifically @types/react ( '@types/react' should be listed in the project's dependencies, not devDependencies). and @types/yup ('@types/yup' should be listed in the project's dependencies. Run 'npm i -S @types/yup' to add it). Downgrading to 2.22.1 fixed both of these.

[mtnowl]

Is this addressed by #2097?

[VirajKanse]

is this fixed yet or not?
Am still facing same issue for @chakra-ui/layout & other components

[ljharb]

Yes, it’s fixed in v2.23.4. If you’re still seeing it, please file a new issue.