chore: Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

Detected Package Files

• demos/app/package.json (npm)
• demos/server/package.json (npm)
• package.json (npm)
• packages/core/package.json (npm)
• packages/react/package.json (npm)
• packages/runtime/package.json (npm)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title

---

What to Expect

With your current configuration, Renovate will create 16 Pull Requests:

chore(deps): update dependency @​types/node to v22.19.19

• Schedule: ["at any time"]
• Branch name: renovate/node-22.x-lockfile
• Merge into: main
• Upgrade @types/node to 22.19.19

chore(deps): update dependency @​types/react to v19.2.15

• Schedule: ["at any time"]
• Branch name: renovate/react-monorepo
• Merge into: main
• Upgrade @types/react to 19.2.15

chore(deps): update dependency prettier to v3.8.3

• Schedule: ["at any time"]
• Branch name: renovate/prettier-3.x-lockfile
• Merge into: main
• Upgrade prettier to 3.8.3

chore(deps): update dependency vite to v6.4.2

• Schedule: ["at any time"]
• Branch name: renovate/vite-6.x-lockfile
• Merge into: main
• Upgrade vite to 6.4.2

chore(deps): update eslint monorepo to v9.39.4

• Schedule: ["at any time"]
• Branch name: renovate/eslint-monorepo
• Merge into: main
• Upgrade @eslint/js to 9.39.4
• Upgrade eslint to 9.39.4

chore(deps): update dependency tsx to v4.22.3

• Schedule: ["at any time"]
• Branch name: renovate/tsx-4.x-lockfile
• Merge into: main
• Upgrade tsx to 4.22.3

chore(deps): update typescript-eslint monorepo to v8.60.0

• Schedule: ["at any time"]
• Branch name: renovate/typescript-eslint-monorepo
• Merge into: main
• Upgrade @typescript-eslint/eslint-plugin to 8.60.0
• Upgrade @typescript-eslint/parser to 8.60.0

chore(deps): update dependency @​types/node to v24

• Schedule: ["at any time"]
• Branch name: renovate/node-24.x
• Merge into: main
• Upgrade @types/node to ^24.0.0

chore(deps): update dependency @​vitejs/plugin-react to v6

• Schedule: ["at any time"]
• Branch name: renovate/vitejs-plugin-react-6.x
• Merge into: main
• Upgrade @vitejs/plugin-react to ^6.0.0

chore(deps): update dependency globals to v17

• Schedule: ["at any time"]
• Branch name: renovate/globals-17.x
• Merge into: main
• Upgrade globals to ^17.0.0

chore(deps): update dependency jsdom to v29

• Schedule: ["at any time"]
• Branch name: renovate/jsdom-29.x
• Merge into: main
• Upgrade jsdom to ^29.0.0

chore(deps): update dependency typescript to v6

• Schedule: ["at any time"]
• Branch name: renovate/typescript-6.x
• Merge into: main
• Upgrade typescript to ^6.0.0

chore(deps): update dependency vite to v8

• Schedule: ["at any time"]
• Branch name: renovate/vite-8.x
• Merge into: main
• Upgrade vite to ^8.0.0

chore(deps): update eslint monorepo to v10

• Schedule: ["at any time"]
• Branch name: renovate/major-eslint-monorepo
• Merge into: main
• Upgrade @eslint/js to ^10.0.0
• Upgrade eslint to ^10.0.0

chore(deps): update vitest monorepo to v4

• Schedule: ["at any time"]
• Branch name: renovate/major-vitest-monorepo
• Merge into: main
• Upgrade @vitest/coverage-v8 to ^4.0.0
• Upgrade vitest to ^4.0.0

fix(deps): update dependency @​hono/node-server to v2

• Schedule: ["at any time"]
• Branch name: renovate/hono-node-server-2.x
• Merge into: main
• Upgrade @hono/node-server to ^2.0.0

🚸 PR creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prHourlyLimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR was generated by Mend Renovate. View the repository job log.