chore(deps-dev): bump @typescript-eslint/parser from 8.36.0 to 8.37.0 in /Frontend

[dependabot]

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

好的，这是翻译成中文的 pull request 总结：

Sourcery 总结

将开发依赖项 @typescript-eslint/parser 升级到 8.37.0 版本，并相应地更新 pnpm lockfile

任务：

• 在前端将 @typescript-eslint/parser 及相关的 ESLint 包升级到 8.37.0
• 重新生成 pnpm lockfile

Original summary in English

Summary by Sourcery

Bump the dev dependency @typescript-eslint/parser to version 8.37.0 and update the pnpm lockfile accordingly

Chores:

• Bump @typescript-eslint/parser and related ESLint packages to 8.37.0 in the Frontend
• Regenerate pnpm lockfile

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
quicknote-frontend-demo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 15, 2025 7:57am

[sourcery-ai]

## 审查者指南

在 Frontend 项目中将 @typescript-eslint/parser 升级到 v8.37.0，调整 package.json 并重新生成 pnpm lockfile，以包含新的 parser 版本及其相关的 @typescript-eslint 包更新。

### 文件级别变更

| 变更 | 详情 | 文件 |
| ------ | ------- | ----- |
| 将 @typescript-eslint/parser 开发依赖项升级到 8.37.0 | <ul><li>更新 package.json 中的 parser 规范从 ^8.36.0 到 ^8.37.0</li></ul> | `Frontend/package.json` |
| 重新生成 pnpm-lock.yaml 以升级 parser 和相关的 ESLint 包 | <ul><li>更新 lockfile 中的 @typescript-eslint/parser 版本和规范</li><li>为 parser 和所有 @typescript-eslint/* 子包添加 8.37.0 版本的解析条目，包含新的完整性哈希和 peerDependencies</li><li>刷新快照部分以反映更新后的 parser 和插件依赖版本</li></ul> | `Frontend/pnpm-lock.yaml` |

---

<details>
<summary>提示和命令</summary>

#### 与 Sourcery 互动

- **触发新的审查：** 在 pull request 上评论 `@sourcery-ai review`。
- **继续讨论：** 直接回复 Sourcery 的审查评论。
- **从审查评论生成 GitHub issue：** 通过回复审查评论，让 Sourcery 从审查评论创建一个 issue。您也可以回复审查评论并使用 `@sourcery-ai issue` 从中创建一个 issue。
- **生成 pull request 标题：** 在 pull request 标题中的任何位置写入 `@sourcery-ai` 以随时生成标题。您也可以在 pull request 上评论 `@sourcery-ai title` 以随时（重新）生成标题。
- **生成 pull request 摘要：** 在 pull request 正文中的任何位置写入 `@sourcery-ai summary` 以随时在您想要的位置生成 PR 摘要。您也可以在 pull request 上评论 `@sourcery-ai summary` 以随时（重新）生成摘要。
- **生成审查者指南：** 在 pull request 上评论 `@sourcery-ai guide` 以随时（重新）生成审查者指南。
- **解决所有 Sourcery 评论：** 在 pull request 上评论 `@sourcery-ai resolve` 以解决所有 Sourcery 评论。如果您已经解决了所有评论并且不想再看到它们，这将非常有用。
- **驳回所有 Sourcery 审查：** 在 pull request 上评论 `@sourcery-ai dismiss` 以驳回所有现有的 Sourcery 审查。如果您想重新开始新的审查，这将特别有用 - 不要忘记评论 `@sourcery-ai review` 以触发新的审查！

#### 自定义您的体验

访问您的 [仪表板](https://app.sourcery.ai) 以：
- 启用或禁用审查功能，例如 Sourcery 生成的 pull request 摘要、审查者指南等。
- 更改审查语言。
- 添加、删除或编辑自定义审查说明。
- 调整其他审查设置。

#### 获取帮助

- [联系我们的支持团队](mailto:support@sourcery.ai) 提出问题或反馈。
- 访问我们的 [文档](https://docs.sourcery.ai) 获取详细的指南和信息。
- 通过在 [X/Twitter](https://x.com/SourceryAI)、[LinkedIn](https://www.linkedin.com/company/sourcery-ai/) 或 [GitHub](https://github.com/sourcery-ai) 上关注我们，与 Sourcery 团队保持联系。

</details>

Original review guide in English

Reviewer's Guide

Upgrade @typescript-eslint/parser to v8.37.0 in the Frontend project, adjusting package.json and regenerating the pnpm lockfile to include the new parser version and its related @typescript-eslint package updates.

File-Level Changes

Change	Details	Files
Bump @typescript-eslint/parser dev dependency to 8.37.0	Update parser specifier in package.json from ^8.36.0 to ^8.37.0	Frontend/package.json
Regenerate pnpm-lock.yaml to upgrade parser and related ESLint packages	Update @typescript-eslint/parser version and specifier in lockfile Add resolution entries for parser and all @typescript-eslint/* subpackages at 8.37.0 with new integrity hashes and peerDependencies Refresh snapshot sections to reflect updated parser and plugin dependency versions	Frontend/pnpm-lock.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[dependabot]

Superseded by #71.