Update dependencies

[nortonandreev]

PR Type

Enhancement

---

Description

• Update multiple dependencies to latest versions

• Move @rollup/plugin-alias from dependencies to devDependencies

• Update VuePress ecosystem packages to rc.121 and rc.102

• Upgrade sass, mermaid, and other core packages

---

Diagram Walkthrough

flowchart LR
  A["package.json"] -->|"Move to devDeps"| B["@rollup/plugin-alias v6.0.0"]
  A -->|"Update VuePress"| C["@vuepress packages rc.121+"]
  A -->|"Upgrade core"| D["sass, mermaid, eslint"]
  A -->|"Update tooling"| E["vite-plugin-vue-devtools v8.0.5"]

Loading

File Walkthrough

	Relevant files
Dependencies	package.json Update all dependencies and reorganize package structure  package.json Move @rollup/plugin-alias from dependencies to devDependencies with version bump to ^6.0.0 Update @vuepress/plugin-llms from ^2.0.0-rc.112 to 2.0.0-rc.121 Upgrade sass from ^1.86.0 to ^1.97.3 Update mermaid from ^11.4.0 to ^11.12.2 Bump vite-plugin-vue-devtools from ^7.3.6 to ^8.0.5 Update @vuepress/bundler-vite and vuepress to 2.0.0-rc.26 Upgrade vuepress-theme-hope to 2.0.0-rc.102 Minor version updates for eslint, sass-loader, and @vuepress/plugin-watermark +11/-11  pnpm-lock.yaml Regenerate lock file for updated dependencies                        pnpm-lock.yaml Lock file updated to reflect all package.json dependency changes Regenerated with new versions of all updated packages +1358/-1635
Miscellaneous	SidebarLayout.vue Layout file updated with dependency changes                            docs/.vuepress/layouts/SidebarLayout.vue File modified as part of dependency update process +0/-2

---

[github-actions]

Docs build

• Status: ✅ Build succeeded
• Preview: https://update-dependencies.documentation-21k.pages.dev
  Changed pages:

[github-actions]

Docs build

• Status: ✅ Build succeeded
• Preview: https://update-dependencies.documentation-21k.pages.dev
  Changed pages:

[cloudflare-workers-and-pages]

Deploying documentation with    Cloudflare Pages

Latest commit:	a73a337
Status:	✅  Deploy successful!
Preview URL:	https://841fd0f9.documentation-21k.pages.dev
Branch Preview URL:	https://update-dependencies.documentation-21k.pages.dev

View logs

[github-actions]

Docs Preview

• Status: ⏳ Creating preview…

[qodo-code-review]

ⓘ Your approaching your monthly quota for Qodo. Upgrade your plan

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Missing diff context: The PR includes changes in files not shown in the provided diff, so it cannot be verified whether any critical actions were introduced/modified without corresponding audit logging context. Referred Code <script setup lang="ts"> import { computed } from 'vue' Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Missing diff context: The PR indicates modifications to code files whose diffs are not provided, so new/changed identifiers cannot be reviewed for meaningful, self-documenting naming. Referred Code <script setup lang="ts"> import { computed } from 'vue' Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Missing diff context: Because the diff for modified application/source files is not included, potential new failure points and corresponding error/edge-case handling cannot be validated. Referred Code <script setup lang="ts"> import { computed } from 'vue' Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Missing diff context: The PR modifies code in files not shown here, so it cannot be verified whether any user-facing errors now expose internal details or stack traces. Referred Code <script setup lang="ts"> import { computed } from 'vue' Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Missing diff context: Since code diffs for all modified files are not available, it cannot be confirmed whether any new/changed logging was introduced and whether it avoids sensitive data. Referred Code <script setup lang="ts"> import { computed } from 'vue' Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Missing diff context: The PR includes modifications outside the shown package.json diff, so any new/changed input handling cannot be assessed for validation/sanitization and secure data handling. Referred Code <script setup lang="ts"> import { computed } from 'vue' Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

ⓘ Your approaching your monthly quota for Qodo. Upgrade your plan

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
High-level	Address new Node.js version requirement Updated dependencies like @mdit-vue/* and @rollup/plugin-alias now require Node.js v20+. This breaking change must be documented in the PR, and all environments (dev, CI/CD, prod) must be upgraded to prevent build failures. Examples: pnpm-lock.yaml [1003-1005] '@mdit-vue/plugin-component@3.0.2': resolution: {integrity: sha512-Fu53MajrZMOAjOIPGMTdTXgHLgGU9KwTqKtYc6WNYtFZNKw04euSfJ/zFg8eBY/2MlciVngkF7Gyc2IL7e8Bsw==} engines: {node: '>=20.0.0'} pnpm-lock.yaml [1385-1387] '@rollup/plugin-alias@6.0.0': resolution: {integrity: sha512-tPCzJOtS7uuVZd+xPhoy5W4vThe6KWXNmsFCNktaAh5RTqcLiSfT4huPQIXkgJ6YCOjJHvecOAzQxLFhPxKr+g==} engines: {node: '>=20.19.0'} Solution Walkthrough: Before: # pnpm-lock.yaml (old) '@rollup/plugin-alias@3.1.9': engines: {node: '>=8.0.0'} ... '@mdit-vue/plugin-component@2.1.4': # No engine specified '@mdit-vue/plugin-frontmatter@2.1.4': # No engine specified # ... other mdit-vue plugins without specific node engine requirements After: # pnpm-lock.yaml (new) '@rollup/plugin-alias@6.0.0': engines: {node: '>=20.19.0'} ... '@mdit-vue/plugin-component@3.0.2': engines: {node: '>=20.0.0'} '@mdit-vue/plugin-frontmatter@3.0.2': engines: {node: '>=20.0.0'} # ... other mdit-vue plugins now requiring node >=20.0.0 # PR description should be updated to mention this breaking change. Suggestion importance[1-10]: 10 __ Why: The suggestion correctly identifies a critical breaking change in the required Node.js version introduced by updated dependencies, which could break build and deployment pipelines.	High
General	Pin release candidate dependency version Pin the version of the vuepress-plugin-md-enhance dependency to avoid potentially unstable updates from the release candidate. package.json [58] -"vuepress-plugin-md-enhance": "^2.0.0-rc.93" +"vuepress-plugin-md-enhance": "2.0.0-rc.93" [To ensure code accuracy, apply this suggestion manually] Suggestion importance[1-10]: 6 __ Why: The suggestion correctly points out an inconsistent version specifier for an RC package and recommends pinning it, which is a best practice for stability and aligns with other changes in the PR.	Low
More

[github-actions]

Docs build

• Status: ✅ Build succeeded
• Preview: https://update-dependencies.documentation-21k.pages.dev
  Changed pages:

[nortonandreev]

This has been removed, as the project uses pnpm, not npm.