Apologies for resuming this old thread, but I have the same problem with a new project I’m setting up. This time I tried using yarn (instead of npm) but it doesn’t work neither in the default terminal nor in iTerm2.
Can somebody help me?
$ quasar info
Operating System - Darwin(20.3.0) - darwin/x64
NodeJs - 14.16.1
NPM - 6.14.12
yarn - 1.22.10
@quasar/cli - undefined
@quasar/icongenie - 2.3.3
cordova - Not installed
Important local packages
quasar - 2.0.0-beta.13 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
@quasar/app - 3.0.0-beta.17 -- Quasar Framework local CLI
@quasar/extras - 1.10.4 -- Quasar Framework fonts, icons and animations
eslint-plugin-quasar - Not installed
vue - 3.0.11 -- vue
vue-router - 4.0.5
vuex - 4.0.0 -- state management for Vue.js
electron - Not installed
electron-packager - Not installed
electron-builder - Not installed
@babel/core - 7.13.16 -- Babel compiler core.
webpack - 5.35.0 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff.
webpack-dev-server - 4.0.0-beta.2 -- Serves a webpack app. Updates the browser on changes.
workbox-webpack-plugin - Not installed
register-service-worker - 1.7.2 -- Script for registering service worker, with hooks
@capacitor/core - Not installed
@capacitor/cli - Not installed
@capacitor/android - Not installed
@capacitor/ios - Not installed
Quasar App Extensions
$ quasar upgrade
App • Looking for Quasar App Extension "upgrade" command
App • ⚠️ Quasar App Extension "upgrade" is missing...
/ _ \ _ _ __ _ ___ __ _ _ __
| | | | | | |/ _` / __|/ _` | '__|
| |_| | |_| | (_| \__ \ (_| | |
Running @quasar/app v3.0.0-beta.17
$ quasar <command> <options>
Help for a command
$ quasar <command> --help
$ quasar <command> -h
--version, -v Print Quasar App CLI version
dev, d Start a dev server for your App
build, b Build your app for production
clean, c Clean all build artifacts
new, n Quickly scaffold page/layout/component/... vue file
mode, m Add/remove Quasar Modes for your App
inspect Inspect generated Webpack config
ext, e Manage Quasar App Extensions
run, r Run specific command provided by an installed
Quasar App Extension
describe Describe a Quasar API (component)
test, t Run @quasar/testing App Extension command
- requires @quasar/testing App Extension to be installed
- this is an alias command for convenience purposes
info, i Display info about your machine and your App
help, h Displays this message
If the specified command is not found, then "quasar run"
will be executed with the provided arguments.
a) The commands to create the project do not mention neither meteor nor quasar
Every thing under api is managed by meteor. So for example to start the meteor backend you use Meteor CLI to start it. Also to update meteor you use meteor cli. And of course Quasar Cli is used to manage and start client.
The code in quasar-meteor/api/client/main.js/ contains Blaze code; why should it be needed it if the client is made of Quasar/Vue components?
I have not seen that, because I run meteor headless. But you could create a gui in the api backend part of meteor, for admin things. Its’ optional/just a bonus.
I have seen this error, and the weirdest thing was that I had suddenly in my code an import node: which I am 100% certain I did not put in, almost like a plugin in Visual Studio Code was adding this without my knowledge. I removed this line and the latest plugins and now all is OK again. But watch out for ‘stinky’ plugins !!
I’ve been evaluating schema-based form generators too, as I want to move from server-generated DOM to a JSON serializaton of forms and their rules, so we can offer a better mobile experience, offline, etc. We have hundreds of fields in a form, dozens per “page”, with potentially a lot of business rules.
Vue-Form-Generator is not really maintained and doesn’t look like it quite made it to the next version. It also bakes in Bootstrap UI.
Vue Form JSON Schema looks promising, but I wish it was a little more “automatic” and less verbose. Last updated 5 months ago or so?
JSONForms (https://jsonforms.io/) I just came across. I think they recently added Vue support (was originally Angular and React). It uses Material as the UI styling. But it has some neat features like defaulting a UI Schema for you based on the data Schema. I like some of their dependent fields (if Yes, show/require this other field) stuff, and I like how using this would abstract us from Vue, in case we have to use React in some context in the future.