fix: tsc

Upgrade dooboo-ui to resolve issue as hyochan/dooboo-ui@9d61d3e
crossplatformkorea · Sep 19, 2024 · f810a7b · f810a7b
1 parent b54de79
commit f810a7b
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 10 deletions.
diff --git a/bun.lockb b/bun.lockb
diff --git a/package.json b/package.json
@@ -54,7 +54,7 @@
     "@supabase/supabase-js": "^2.45.1",
     "base64-arraybuffer": "^1.0.2",
     "date-fns": "^4.0.0",
-    "dooboo-ui": "^0.2.37",
+    "dooboo-ui": "^0.2.38",
     "expo": "~51.0.31",
     "expo-constants": "~16.0.2",
     "expo-device": "~6.0.2",

diff --git a/yarn.lock b/yarn.lock
@@ -1,6 +1,6 @@
 # THIS IS AN AUTOGENERATED FILE. DO NOT EDIT THIS FILE DIRECTLY.
 # yarn lockfile v1
-# bun ./bun.lockb --hash: DB593551A00E9104-37e19a57fe9dcdd6-3AE88466605F0B8E-491a7c0c0d5d39b5
+# bun ./bun.lockb --hash: 88D55B2F60888258-b0db5d93e7685601-63C3DDC4B71F1AF0-4063e4b372e9f11b
 
 
 "@aashutoshrathi/word-wrap@^1.2.3":
@@ -10291,10 +10291,10 @@ domutils@^3.0.1:
     domelementtype "^2.3.0"
     domhandler "^5.0.3"
 
-dooboo-ui@^0.2.37:
-  version "0.2.37"
-  resolved "https://registry.npmjs.org/dooboo-ui/-/dooboo-ui-0.2.37.tgz"
-  integrity sha512-Hj6aaXQiWXRHmgH9wxPe6jxOBCZeUBKtoUnuYfI6pjoPFOhwGtkS3eVMvtBKmjZYQYiNYUQ9Jgv9cf5yjQqkZA==
+dooboo-ui@^0.2.38:
+  version "0.2.38"
+  resolved "https://registry.npmjs.org/dooboo-ui/-/dooboo-ui-0.2.38.tgz"
+  integrity sha512-Xjkt5hYE9ddHniCQN/dk20hrHZMw8nWHr6lmr6tqWVTEE8KhdxCHX6oF7Wl0Yx2XEcD31OwJ/fQGGb1ppKuH7w==
   dependencies:
     "@dooboo-ui/theme" "^0.12.14"
     dooboolab-welcome "^1.3.2"
@@ -16621,7 +16621,7 @@ react-native@*, "react-native@>= 0.30.0", react-native@>=0.60:
     "@react-native-community/cli-platform-ios" "13.6.9"
     "@react-native-community/cli-platform-android" "13.6.9"
 
-react-native@*, react-native@>=0.58, react-native@>=0.59, react-native@>=0.62.x, react-native@>=0.73:
+react-native@*, react-native@>=0.59, react-native@>=0.62.x, react-native@>=0.73:
   version "0.74.5"
   resolved "https://registry.npmjs.org/react-native/-/react-native-0.74.5.tgz"
   integrity sha512-Bgg2WvxaGODukJMTZFTZBNMKVaROHLwSb8VAGEdrlvKwfb1hHg/3aXTUICYk7dwgAnb+INbGMwnF8yeAgIUmqw==
@@ -16664,7 +16664,7 @@ react-native@*, react-native@>=0.58, react-native@>=0.59, react-native@>=0.62.x,
     "@react-native-community/cli-platform-ios" "13.6.9"
     "@react-native-community/cli-platform-android" "13.6.9"
 
-react-native@*, react-native@~0.75.0:
+react-native@*, react-native@>=0.58, react-native@~0.75.0:
   version "0.75.3"
   resolved "https://registry.npmjs.org/react-native/-/react-native-0.75.3.tgz"
   integrity sha512-+Ne6u5H+tPo36sme19SCd1u2UID2uo0J/XzAJarxmrDj4Nsdi44eyUDKtQHmhgxjRGsuVJqAYrMK0abLSq8AHw==
@@ -16726,7 +16726,7 @@ react-native-error-boundary@^1.2.4:
   resolved "https://registry.npmjs.org/react-native-error-boundary/-/react-native-error-boundary-1.2.4.tgz"
   integrity sha512-PF5xn+3mGKk8uzf9GpOQa1kvxsG3Bs3XMwJZNqqUG//jC1FDp+WRGxg4r2sPG70MveSOQmQNuHnAycCPYQNg6g==
 
-react-native-gesture-handler@*, react-native-gesture-handler@>=2.0.0:
+react-native-gesture-handler@>=2.0.0:
   version "2.16.2"
   resolved "https://registry.npmjs.org/react-native-gesture-handler/-/react-native-gesture-handler-2.16.2.tgz"
   integrity sha512-vGFlrDKlmyI+BT+FemqVxmvO7nqxU33cgXVsn6IKAFishvlG3oV2Ds67D5nPkHMea8T+s1IcuMm0bF8ntZtAyg==
@@ -16737,7 +16737,7 @@ react-native-gesture-handler@*, react-native-gesture-handler@>=2.0.0:
     lodash "^4.17.21"
     prop-types "^15.7.2"
 
-react-native-gesture-handler@~2.18.1:
+react-native-gesture-handler@*, react-native-gesture-handler@~2.18.1:
   version "2.18.1"
   resolved "https://registry.npmjs.org/react-native-gesture-handler/-/react-native-gesture-handler-2.18.1.tgz"
   integrity sha512-WF2fxQ5kTaxHghlkBM4YxO86SyGWVwrSNgJ1E8z/ZtL2xD5B3bg5agvuVFfOzvceC114yq71s6E9vKPz94ZxRw==