From eeb6f31f06c6c9a9f32bf359339fe547d5b92c47 Mon Sep 17 00:00:00 2001
From: zo_zni <thekey1027@naver.com>
Date: Sun, 31 May 2026 05:49:27 +0900
Subject: [PATCH] chore: regenerate package-lock.json after npm install (#137)

Running `npm install` against the existing lockfile added a `"dev": true`
flag to the fsevents entry. Committed so the lockfile matches a clean
install on Node 20.

Co-authored-by: zozni-douzone <hjcho1027@douzone.com>
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
---
 package-lock.json | 1 +
 1 file changed, 1 insertion(+)

diff --git a/package-lock.json b/package-lock.json
index eb3d21b..d14ed3d 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -5882,6 +5882,7 @@
       "version": "2.3.2",
       "resolved": "https://registry.npmjs.org/fsevents/-/fsevents-2.3.2.tgz",
       "integrity": "sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==",
+      "dev": true,
       "hasInstallScript": true,
       "license": "MIT",
       "optional": true,