Registry / web-framework / zova-cli

zova-cli

JSON →
library1.2.36jsnpmunverified

Zova CLI is the official command-line interface tool for the Zova framework, a comprehensive full-stack solution designed to offer an intuitive development experience by integrating the strengths of Vue3, React, and Angular. The CLI, currently at version 1.2.36, is actively maintained and updated in alignment with the Zova framework's ongoing development. Zova differentiates itself by streamlining reactivity (eliminating the need for `ref.value` in Vue3 contexts), adopting a flexible TSX-based rendering approach similar to React but with a simplified 'Render Class' model to reduce complexity, and leveraging a powerful, yet simplified, Inversion of Control (IOC) container inspired by Angular to unify state management. The CLI facilitates project creation, offering various templates like Quasar, Vuetify, and an empty base for other UI libraries, enabling developers to quickly set up Zova applications with SSR, modularization, and CSS-in-JS capabilities.

npm install zova-cli
INSTALL
IMPORT
SIG · ZOVA-CLI
Z
zova-cli
web-frameworkjavascriptv1.2.36
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

zova
pnpm add -g zova-cli@latest zova :create:project my-app --template=vuetify
npm install -g zova-cli yarn global add zova-cli
The Zova documentation explicitly recommends `pnpm` for global installation and project management. Other package managers may lead to unexpected behavior or dependency conflicts.
:create:project
zova :create:project my-project-name --template=quasar
zova create project my-project-name
The command syntax uses colons for sub-commands, e.g., `:create:project`, which is a specific convention of this CLI.
zova-cli VSCode Extension
Install 'Zova - Official' extension from VSCode Marketplace
While not a code import, the Zova documentation recommends installing the official VSCode extension for enhanced development experience, providing code skeletons and other utilities.

Demonstrates the global installation of zova-cli, creation of a new Zova project with a specified template (Vuetify), installation of project dependencies, and starting the development server.

pnpm add -g zova-cli@latest # Create a new Zova project using the Vuetify template zova :create:project my-zova-app --template=vuetify # Navigate into the new project directory cd my-zova-app # Install project dependencies (using pnpm) pnpm install # Start the development server pnpm run dev console.log('Zova development server typically runs on http://localhost:3000');
zova --version
Debug
Known issues
gotchaThe Zova framework documentation explicitly recommends `pnpm` as the package manager. Using `npm` or `yarn` for global installation or project dependency management might lead to unexpected dependency resolution issues or other inconsistencies with the framework's design.
fix
Always use `pnpm` for installing `zova-cli` globally and for managing Zova project dependencies. Ensure `pnpm` is installed (`npm install -g pnpm`) and updated.
affects: >=1.0.0
gotchaZova CLI commands utilize a specific colon-delimited syntax for sub-commands (e.g., `:create:project`). Misunderstanding this syntax can lead to command not found errors.
fix
Always refer to the Zova documentation for the precise command syntax, especially for sub-commands and options. Use `zova --help` for general command overview.
affects: >=1.0.0
gotchaThe Zova framework has specific Node.js version requirements (e.g., >=24.8.0). Using an older or incompatible Node.js version can cause installation failures or runtime errors for both the CLI and generated projects.
fix
Ensure your Node.js version meets the prerequisites specified in the Zova documentation. Use a Node Version Manager (like `nvm` or `fnm`) to easily switch and manage Node.js versions.
affects: >=1.0.0
Errors
Common errors & fixes
zova: command not found
The `zova-cli` package was not installed globally or its installation directory is not in your system's PATH.
fix
Ensure `zova-cli` is installed globally using `pnpm add -g zova-cli@latest`. Verify `pnpm`'s global bin directory is in your system's PATH.
Error: Cannot find module 'vue' or 'webpack' (or similar dependency error) during project creation or `pnpm install`.
Incompatible `pnpm` or Node.js version, or corrupted `pnpm` cache, preventing correct dependency resolution for project templates.
fix
Verify Node.js version (>=24.8.0) and `pnpm` version. Try clearing `pnpm` cache (`pnpm store prune`) or reinstalling global `zova-cli` and project dependencies from scratch.
Error: unknown command ':create:project'
Typo in the command or incorrect understanding of the colon-delimited sub-command syntax unique to `zova-cli`.
fix
Double-check the command syntax. It must be `zova :create:project projectName --template=templateName`. The colons are crucial.
Upgrade
Version history
1.2.36latest on npm
Audit
Dependencies
pnpmrequiredRequired for package management as recommended by the Zova framework documentation.
Node.jsrequiredRuntime environment for the CLI and Zova projects. Version >=24.8.0 is specified as a prerequisite.
Agent activity
53 hits · last 30 days
node
46
OpenAI (training)
1
Resources
zova-cli — npm install zova-cli · libregistry