feat: add ubugeeei/vize

[hituzi-no-sippo]

ubugeeei/vize: Unofficial High-Performance Vue.js Toolchain in Rust

aqua g -i ubugeeei/vize

Check List

• Read CONTRIBUTING.md
  • Read OSS Contribution Guide
• All commits are signed
  • This repository enables Require signed commits, so all commits must be signed
• Avoid force push
• Do only one thing in one Pull Request
• Execute cmdx s to scaffold code
• Install and execute the package and confirm if the package works well

How to confirm if this package works well

Reviewers aren't necessarily familiar with this package, so please describe how to confirm if this package works well.
Please confirm if this package works well yourself as much as possible.

Command and output

$ vize lint foo.vue

  × [vize:vue/require-v-for-key] Elements in iteration expect to have 'v-bind:key' directives. Element: <li>
   ╭─[foo.vue:4:11]
 3 │     <ul>
 4 │       <li v-for="item in items">{{ item.name }}</li>
   ·           ────────────────────
 5 │     </ul>
   ╰────
  help: Why: The :key attribute helps Vue's virtual DOM efficiently track and update list items.
        Fix: Add a unique identifier as the key:
          <li v-for="item in items" :key="item.id">
          {{ item.name }}
          </li>
        Best practices:
        - Use unique, stable identifiers (like database IDs)
        - Avoid using array index as key when list order may change
        - Keys must be primitive values (string or number)


1 error in 1 file
Linted 1 files in 4.8491ms
$

If files such as configuration file are needed, please share them.

foo.vue

<template>
  <div class="container">
    <ul>
      <li v-for="item in items">{{ item.name }}</li>
    </ul>
  </div>
</template>

Reference

• GitHub Release

Summary by CodeRabbit

• New Features
  • New package ubugeeei/vize v0.24.0 is now available in the registry with full cross-platform support for Linux, macOS, and Windows, supporting both x86_64 and ARM64 architectures with automatically optimized package formats for each operating system.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b8b2494b-a351-4c13-84d5-20f1a99a9946

📥 Commits

Reviewing files that changed from the base of the PR and between bb05b78 and 9d9332f.

📒 Files selected for processing (3)

• pkgs/ubugeeei/vize/pkg.yaml
• pkgs/ubugeeei/vize/registry.yaml
• registry.yaml

---

📝 Walkthrough

Walkthrough

The PR introduces a new package registration for ubugeeei/vize v0.24.0 across the package management system, including manifest entry, local registry configuration, and global registry entry with version constraints and platform-specific asset mappings.

Changes

Cohort / File(s)	Summary
Package Manifest pkgs/ubugeeei/vize/pkg.yaml	Added versioned package entry for ubugeeei/vize@v0.24.0 to define explicit dependency configuration.
Package Registry Configuration pkgs/ubugeeei/vize/registry.yaml, registry.yaml	Created new registry entries with GitHub release metadata, version constraints, platform-specific asset mappings (architecture/OS translations), and archive format configurations (tar.gz default, zip for Windows).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Suggested labels

enhancement

Poem

🐰 A hop, skip, and jump through configs so neat,
New vize package joins the registry fleet!
Platform-mapped paths from Windows to Linux divine,
Version constraints set, dependencies align! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'feat: add ubugeeei/vize' clearly and concisely summarizes the main change—adding a new package entry for ubugeeei/vize to the registry.
Description check	✅ Passed	The description includes package details, installation instructions, a comprehensive checklist with all items checked, verification steps with sample output, and relevant file examples demonstrating the package functionality.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[suzuki-shunsuke]

Thank you!