@arethetypeswrong/[email protected]

Patch Changes

• 35544c5: Fix crash from missing optional chain

@arethetypeswrong/[email protected]

Minor Changes

• a578211: - Refactor internal checks API. This fixes duplication of some problems from the problems array, instead ensuring a single problem instance is visible from each relevant resolution.
  • Improve problem type API. Renames many fields on individual problem types.
  • Move module kind data off of EntrypointResolutionAnalysis and onto a top-level map in programInfo, a new top-level field on Analysis.
  • Remove Wildcard problem kind.

@arethetypeswrong/[email protected]

Patch Changes

• Updated dependencies [35544c5]
  • @arethetypeswrong/[email protected]

@arethetypeswrong/[email protected]

Patch Changes

• Updated dependencies [a578211]
  • @arethetypeswrong/[email protected]

@arethetypeswrong/[email protected]

Minor Changes

• 26f89d1: Infer --from-npm version from a locally-provided DefinitelyTyped package

@arethetypeswrong/[email protected]

Patch Changes

• eecbf74: Fix issue with resolving DefinitelyTyped versions

@arethetypeswrong/[email protected]

Patch Changes

• Updated dependencies [eecbf74]
  • @arethetypeswrong/[email protected]

@arethetypeswrong/[email protected]

Patch Changes

• ae2426f: Fixed bug that could cause a crash while checking for FalseExportDefault

@arethetypeswrong/[email protected]

Minor Changes

• 30bdb07: New problem kind: Missing export =

  Previously, FalseExportDefault had many cases of false positives where the JavaScript assigned an object to module.exports, and that object had a default property pointing back to itself. This pattern is not a true FalseExportDefault, but it is still problematic if the types only declare an export default. These kinds of false positives of FalseExportDefault are now instead reported as MissingExportEquals.

  Additionally, FalseExportDefault was only ever reported as being visible in node16-esm, but this was incorrect. The consequences are most likely to be visible in node16-esm, but the problem is fundamentally independent of the module resolution mode, and inaccuracies can be observed in other modes as well, especially when esModuleInterop is not enabled.

@arethetypeswrong/[email protected]

Patch Changes

• Updated dependencies [ae2426f]
  • @arethetypeswrong/[email protected]