Topics created by rstoenescu

This will make it easier to remember.

Whenever possible, please help us grow by taking a look at our Patreon page: https://www.patreon.com/quasarframework

@rstoenescu Thanks a lot. I only could successfully upgrade quasar locally after updating yarn in windows to the latest version. Otherwise, quasar upgrade, wouldn’t work.

@recke I haven’t tried. but it is supposed … yes possible

Oops, I think I see the issue. I was on a tab of a production version of the docs. But needed to be in https://v1.quasar-framework.org/vue-components/list-and-list-items

Basically upgrading the Quasar dependencies of the project (the devland app) will also upgrade the CLI at the same time. That way, changes that occur to the core software, which also need the Node code improvements in the CLI, will get them automatically. Without this setup, devland would constantly need to update the global CLI too. This change in v1.0 reduces once more developer effort. @quasar/app holds things like extension addition and removal commands, describe for the API, inspect, mode, etc. You’ll notice with the CLI, that if you are in a project directory, you get a lot more commands. If you are outside a project, you only get help, info and create. Did that make any sense? Scott

@ben-hayat This command will check the registry to see if any (or, specific) installed packages are currently outdated. npm-outdated

Personally I see the vue-cli-plugin as a “gateway” to Quasar. Its important that we have it, but you are very right Razvan, users will not have tight coupling with the rest of the Quasar ecosystem if they use this.

The beta fixes and enhancements are insanely fast…can’t describe how awesome u are @rstoenescu

@rusia Thanks!