We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Whenever a new job uses the cached node_modules instead of installing fresh, the Quasar CLI reports:
node_modules
Error Unknown command "build" ___ / _ \ _ _ __ _ ___ __ _ _ __ | | | | | | |/ _` / __|/ _` | '__| | |_| | |_| | (_| \__ \ (_| | | \__\_\\__,_|\__,_|___/\__,_|_| Running @quasar/cli ***.2.1 Example usage $ quasar <command> <options> Help for a command $ quasar <command> --help $ quasar <command> -h Options --version, -v Print Quasar CLI version Commands create Create a project folder info Display info about your machine (and your App if in a project folder) upgrade Check (and optionally) upgrade Quasar packages from a Quasar project folder serve Create an ad-hoc server on App's distributables help, -h Displays this message -------------- => IMPORTANT ! => Trigger this inside of a Quasar project (and npm/yarn install) for more commands. --------------
The text was updated successfully, but these errors were encountered:
Zaba505
No branches or pull requests
Whenever a new job uses the cached
node_modules
instead of installing fresh, the Quasar CLI reports:The text was updated successfully, but these errors were encountered: