From 6e1996df37599f67597f1c0d93243586009e60f3 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Tue, 5 Sep 2023 01:55:20 +0000 Subject: [PATCH] Version Packages --- .changeset/sweet-mangos-marry.md | 9 --------- packages/cli/CHANGELOG.md | 7 +++++++ packages/cli/package.json | 4 ++-- packages/core/CHANGELOG.md | 10 ++++++++++ packages/core/package.json | 2 +- 5 files changed, 20 insertions(+), 12 deletions(-) delete mode 100644 .changeset/sweet-mangos-marry.md diff --git a/.changeset/sweet-mangos-marry.md b/.changeset/sweet-mangos-marry.md deleted file mode 100644 index 9093e05..0000000 --- a/.changeset/sweet-mangos-marry.md +++ /dev/null @@ -1,9 +0,0 @@ ---- -"@arethetypeswrong/core": minor ---- - -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. diff --git a/packages/cli/CHANGELOG.md b/packages/cli/CHANGELOG.md index e703377..902e4a6 100644 --- a/packages/cli/CHANGELOG.md +++ b/packages/cli/CHANGELOG.md @@ -1,5 +1,12 @@ # @arethetypeswrong/cli +## 0.10.0 + +### Patch Changes + +- Updated dependencies [30bdb07] + - @arethetypeswrong/core@0.10.0 + ## 0.9.0 ### Minor Changes diff --git a/packages/cli/package.json b/packages/cli/package.json index 423c07c..25fd469 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "name": "@arethetypeswrong/cli", - "version": "0.9.0", + "version": "0.10.0", "description": "A CLI tool for arethetypeswrong.github.io", "author": "Andrew Branch & ej-shafran", "contributors": [ @@ -45,7 +45,7 @@ "typescript": "^5.0.0-dev.20230207" }, "dependencies": { - "@arethetypeswrong/core": "0.9.0", + "@arethetypeswrong/core": "0.10.0", "chalk": "^4.1.2", "cli-table3": "^0.6.3", "commander": "^10.0.1", diff --git a/packages/core/CHANGELOG.md b/packages/core/CHANGELOG.md index aabe158..313495d 100644 --- a/packages/core/CHANGELOG.md +++ b/packages/core/CHANGELOG.md @@ -1,5 +1,15 @@ # @arethetypeswrong/core +## 0.10.0 + +### 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. + ## 0.9.0 ### Minor Changes diff --git a/packages/core/package.json b/packages/core/package.json index ee3f5d0..ed6c7bd 100644 --- a/packages/core/package.json +++ b/packages/core/package.json @@ -1,6 +1,6 @@ { "name": "@arethetypeswrong/core", - "version": "0.9.0", + "version": "0.10.0", "description": "The API behind arethetypeswrong.github.io", "author": "Andrew Branch", "license": "MIT",