Jake Bailey

Ah, I see. Curiously, `@types/webpack-env` is not mentioned at all in webpack's docs. Given webpack's types in =5, maybe this package is a relic of those pre-upstream-types times and should...

The errors go away if you get rid of `export` on everything, and #40094 made the check always occur: https://github.com/microsoft/TypeScript/pull/40094/files#diff-d9ab6589e714c71e657f601cf30ff51dfc607fc98419bf72e04f6b0fa92cc4b8R32219 Which is probably the problem, though I am confused as...

Thankfully testable using fourslash (but not a compiler test): ``` Semantic Diagnostics for file '/tests/cases/fourslash/overloadNotCompatibleErrorDuplication.ts': /tests/cases/fourslash/overloadNotCompatibleErrorDuplication.ts(8,17): error TS2394: This overload signature is not compatible with its implementation signature. /tests/cases/fourslash/overloadNotCompatibleErrorDuplication.ts(8,17): error...

@typescript-bot bisect good v3.3.3 bad v3.5.1

Those node_module folders look nested. Perhaps you have multiple versions of this types package in your dependency tree?

Or, do you need to install `@types/mapbox-gl` into your package, since you seem to be explicitly referencing it in your project? I'd definitely check those versions to see where the...

Is there any chance you could post your yarn.lock file, specifically all of the entries that start with `@types/mapbox`?

All good!

I'll mirror my comment from https://github.com/yarnpkg/yarn/issues/5428#issuecomment-712481010 here: My need for this behavior (versioning per workspace, but still have lockfiles in each package) is that I have a nested monorepo, where...

I haven't had time to try it out in my project (the above reminded me it exists, oops), but one thing about that plugin is that it appears to always...