From a235c5fea2b006e63b5289312c1895355bb6c1b4 Mon Sep 17 00:00:00 2001
From: Haoqun Jiang <haoqunjiang@gmail.com>
Date: Mon, 18 Aug 2025 14:21:53 +0800
Subject: [PATCH 1/2] fix: disable `exactOptionalPropertyTypes` for now

Even popular libraries can't easily migrate to this option at the moment.

I think we need

1. more consensus on whether this should be the default in the Vue.js
ecosystem, and
2. a softer way to push this forward before making it a type error.
---
 tsconfig.json | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tsconfig.json b/tsconfig.json
index 8b21832..04b1cc0 100644
--- a/tsconfig.json
+++ b/tsconfig.json
@@ -34,7 +34,9 @@
     // See <https://www.semver-ts.org/formal-spec/5-compiler-considerations.html#strictness>
     // These 2 options are also part of the recommended tsconfig as of TS 5.9
     "noUncheckedIndexedAccess": true,
-    "exactOptionalPropertyTypes": true,
+    // Commented out for now. It's hard to land in the current ecosystem.
+    // Needs more consensus before moving forward.
+    // "exactOptionalPropertyTypes": true,
 
     // <https://devblogs.microsoft.com/typescript/announcing-typescript-5-0/#verbatimmodulesyntax>
     // Any imports or exports without a type modifier are left around. This is important for `<script setup>`.

From 4a223b286dde66b8e70608b09ee2ca3ed41d76d7 Mon Sep 17 00:00:00 2001
From: Haoqun Jiang <haoqunjiang@gmail.com>
Date: Mon, 18 Aug 2025 14:25:04 +0800
Subject: [PATCH 2/2] 0.8.1

---
 package.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/package.json b/package.json
index 2ef1553..b70a367 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@vue/tsconfig",
-  "version": "0.8.0",
+  "version": "0.8.1",
   "description": "A base TSConfig for working with Vue.js",
   "main": "tsconfig.json",
   "scripts": {