chore(deps): update dependency nuxt-site-config to v2 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
nuxt-site-config	^1.6.1 -> ^2.2.11

---

Release Notes

harlan-zw/nuxt-site-config (nuxt-site-config)

v2.2.11

Compare Source

No significant changes

    View changes on GitHub

v2.2.10

Compare Source

   🐞 Bug Fixes

• Support https nitro origin for development  -  by @​harlan-zw (cc2bf)
• Prefer explicit props for SiteLink  -  by @​harlan-zw (ec3d3)

    View changes on GitHub

v2.2.9

Compare Source

   🐞 Bug Fixes

• client: Recursion bug crashing IE  -  by @​harlan-zw (9963d)
• devtools: Broken link  -  by @​Endermanch (36b73)

    View changes on GitHub

v2.2.8

Compare Source

   🐞 Bug Fixes

• site-link: Use nuxt's link properties  -  by @​dargmuesli in https://github.com/harlan-zw/nuxt-site-config/issues/18 (e803c)

    View changes on GitHub

v2.2.7

Compare Source

No significant changes

    View changes on GitHub

v2.2.6

Compare Source

   🐞 Bug Fixes

• SiteLink: Properly extend NuxtLinks props  -  by @​harlan-zw (4e974)

    View changes on GitHub

v2.2.5

Compare Source

   🐞 Bug Fixes

• Ensure static site runtimeConfig is applied  -  by @​harlan-zw (91635)

    View changes on GitHub

v2.2.4

Compare Source

   🐞 Bug Fixes

• Nuxt vitest env issue  -  by @​harlan-zw (b003a)

    View changes on GitHub

v2.2.3

Compare Source

   🐞 Bug Fixes

• Safer version resolution  -  by @​harlan-zw (95a4a)
• Avoid undefined overrides  -  by @​harlan-zw (e798b)

    View changes on GitHub

v2.2.2

Compare Source

   🐞 Bug Fixes

• Warning with i18n on updateSiteConfig  -  by @​harlan-zw (265f7)

    View changes on GitHub

v2.2.1

Compare Source

   🐞 Bug Fixes

• Make sure version exists within debug endpoint  -  by @​harlan-zw (02c0f)
• devtools: More consisent UI  -  by @​harlan-zw (1e04a)

    View changes on GitHub

v2.2.0

Compare Source

   🐞 Bug Fixes

• Rename core plugin to nuxt-site-config:init  -  by @​harlan-zw (a8230)
• Require nuxt 3.9  -  by @​harlan-zw (b44df)
• i18n: Ensure plugin runs in the correct order  -  by @​harlan-zw (8bb89)

    View changes on GitHub

v2.1.3

Compare Source

No significant changes

    View changes on GitHub

v2.1.2

Compare Source

   🐞 Bug Fixes

• kit: Add urls subpath export  -  by @​harlan-zw (9aa6a)

    View changes on GitHub

v2.1.1

Compare Source

   🐞 Bug Fixes

• nuxt: Warning being thrown unnecessarily  -  by @​harlan-zw (58110)

    View changes on GitHub

v2.1.0

Compare Source

   🚀 Features

• nitro: site-config:init hook  -  by @​harlan-zw (cba43)

   🐞 Bug Fixes

• nuxt:
  • Incorrect client-side warning for updateSiteConfig  -  by @​harlan-zw (7e7fe)
  • Give i18n a priority of -1  -  by @​harlan-zw (c7785)

    View changes on GitHub

v2.0.1

Compare Source

No significant changes

    View changes on GitHub

v2.0.0

Compare Source

   🚀 Features

• componentOptions config for configuring <SiteLink>  -  by @​harlan-zw (a5e69)
• Nitro getSiteIndexable util  -  by @​harlan-zw (20f71)
• Validate url config on start  -  by @​harlan-zw (66ad1)
• Support any keys from env starting with NUXT_SITE_  -  by @​harlan-zw (c4dfd)

   🏎 Performance

• Client-side read only  -  by @​harlan-zw (df9d9)
• Export url utils on /urls subpath  -  by @​harlan-zw (6e210)
• Smaller state payloads  -  by @​harlan-zw (9be9d)

    ⚠️ Breaking Changes

Client-side site config updates disabled

The updateSiteConfig composable will no longer work client-side. This allows the module to have a significantly smaller performance footprint and avoids hydration errors.

When navigating between pages that change the site config you should do a full page load so that the SSR response will be accurate (i.e switching language or changing domain). If you need to change site config at runtime make sure it happens server-side and early.

    View changes on GitHub

v1.6.7

Compare Source

Bug Fixes

• explicit return types for composables (daa3c72), closes #​10
• maybe resolve nitro import warnings (4d99ddf)

v1.6.6

Compare Source

Bug Fixes

• devtools: avoid errors in rendering (8f5b98b)

v1.6.5

Compare Source

Bug Fixes

• enable debug endpoint by default in dev (a4e9920)

v1.6.4

Compare Source

Bug Fixes

• devtools: make sure client gets generated* (3d0f39b)

v1.6.3

Compare Source

Bug Fixes

• devtools: make sure client gets exported (d0b88fd)

v1.6.2

Compare Source

Bug Fixes

• devtools: use unique name (83f2875)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[coderabbitai]

Important

Auto Review Skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	19.6 kB	pi0
npm/[email protected]	environment, filesystem Transitive: eval, shell, unsafe	+55	9.75 MB	eslintbot

🚮 Removed packages: npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]
Install scripts	npm/[email protected]	Install script: postinstall Source: node install.js	orphan: npm/[email protected]

View full report↗︎

Next steps

What is an install script?

Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts.

Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]
• @SocketSecurity ignore npm/[email protected]