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
muslnode 18–226 runs
build_error
glibcnode 18–226 runs
build_error
Code
Verified usage
Verified import paths — ran on the pinned version, not inferred.
Quasar
✓ import { Quasar } from '@quasar/app'
✗ import { Quasar } from 'quasar-cli'
The `quasar-cli` package is a CLI tool and does not export programmatic symbols for application code. Quasar Framework core functionalities are typically imported from `@quasar/app` (for modern Quasar) or `quasar-framework` (for Quasar v0.x).
cli
✓ N/A (CLI is run via global command)
✗ import cli from 'quasar-cli'
quasar-cli is a command-line interface tool. It is not designed to be imported as a module in application code. Its functionalities are exposed through the `quasar` global command after global installation.
dev
✓ N/A (CLI command: `quasar dev`)
✗ const { dev } = require('quasar-cli')
CommonJS `require()` is also incorrect for `quasar-cli`. Commands like `dev` are executed directly from the terminal using the globally installed `quasar` executable, e.g., `quasar dev`, not imported programmatically.
Demonstrates global installation of the legacy `quasar-cli`, project initialization, dependency installation, and running development/build commands for a Quasar v0.x application.
npm install -g quasar-cli
# Initialize a new Quasar v0.x project
quasar init default my-quasar-app
# Navigate into the new project directory
cd my-quasar-app
# Install project dependencies
npm install # or yarn install
# Start the development server (SPA mode)
quasar dev
# Build for production (SPA mode)
quasar build
quasar --version
Debug
Known issues
breakingThis specific package (`quasar-cli@0.x`) is an older, abandoned CLI version. It is incompatible with Quasar Framework v1+ projects. Attempting to use it with newer Quasar versions will lead to build failures or unexpected behavior.fixFor new projects or existing projects using Quasar Framework v1+, install and use `@quasar/cli` via `npm install -g @quasar/cli`.
affects: >=0.1.0
securityVersions of `quasar-cli` 0.17.x (including 0.17.26) contain transitive dependencies with known vulnerabilities, such as `webpack-dev-server` (Missing Origin Validation), `webpack-bundle-analyzer`, and `lodash.template`. These issues have been addressed in newer, actively maintained versions of the Quasar CLI (`@quasar/cli`).fixUpgrade to the latest `@quasar/cli` and Quasar Framework v1+ to ensure you have the most up-to-date security patches and dependency updates.
affects: >=0.1.0 <=0.17.26
breakingMinor versions of `quasar-cli@0.x` frequently introduced significant dependency updates (e.g., Webpack v4, Electron v3/v4, Quasar Framework v0.17.x, Workbox). These often included breaking changes, requiring manual adjustments to project configurations or code, particularly due to the 0.x semantic versioning where any minor version could introduce breaking changes.fixRefer to the specific release notes for each `0.x` version upgrade to understand required migration steps. For long-term stability and modern features, migrating to Quasar Framework v1+ with `@quasar/cli` is highly recommended.
affects: >=0.1.0 <=0.17.26
gotchaThe `quasar.conf.js` build configuration options changed over time, for instance, `gzip: true` was known to break builds in some `0.17.x` versions, indicating potential configuration incompatibilities across minor updates.fixConsult the Quasar v0.x documentation or community forums for specific configuration issues. For modern, stable configuration, consider upgrading to Quasar Framework v1+ and its corresponding CLI.
affects: >=0.17.20
Errors
Common errors & fixes
webpack-dev-server 'Missing Origin Validation' vulnerability
Outdated `webpack-dev-server` dependency used by `quasar-cli` versions.
fixUpgrade to a newer version of Quasar CLI (`@quasar/cli`) which includes updated `webpack-dev-server` versions or other security patches. (e.g., `webpack-dev-server` v3.1.14+ was released to address this).
Error: quasar.conf > build > gzip: true breaks build
A bug in `quasar-cli@0.17.20` and possibly other `0.17.x` versions where enabling `gzip` in `quasar.conf.js` would cause the production build to fail.
fixSet `gzip: false` in `quasar.conf.js` under the `build` section, or upgrade `quasar-cli` if a patch was released, or migrate to `@quasar/cli`.
Dev on SSR gets stuck if ESLint reports any warning/error
During Server-Side Rendering (SSR) development, ESLint warnings or errors could halt the development server process in `quasar-cli@0.17.19`.
fixEnsure all ESLint warnings and errors are resolved in your project before running `quasar dev` in SSR mode, or disable ESLint strict mode during development (though not recommended). Consider upgrading to a modern Quasar CLI where such issues are typically resolved.
Installing electron bundle deps fails -- log() undefined
A specific bug in `quasar-cli@0.17.19` related to the Electron mode where dependency installation would fail due to an undefined `log()` function.
fixUpdate `quasar-cli` to a version where this specific bug is fixed, or manually address the dependency installation for Electron if possible. The best long-term solution is to migrate to `@quasar/cli` for Electron app development.
Audit
Dependencies
No dependency data recorded yet.