Version Packages

packages/cli/CHANGELOG.md

@@ -1,5 +1,12 @@
 # @arethetypeswrong/cli
 
+## 0.10.0
+
+### Patch Changes
+
+- Updated dependencies [30bdb07]
+  - @arethetypeswrong/[email protected]
+
 ## 0.9.0
 
 ### Minor Changes

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",

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

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",