Quasar Inventory Install

1 view

Skip to first unread message

Rebbeca Schulke

unread,

Aug 3, 2024, 10:43:38 AM8/3/24

to uncogtocheng

So i bought the quasar inventory script & did what i had to do & now it keeps telling me

ive ran into many problems trying to install this script . when i fly into my test server and flex my tab my char does the interaction but the inventory does not pop up .
Please help,Thank you

qs inventory are a very good inventory system if you cannot config or adapt to your server open a ticket simple like that i work on it been like 1-2years with no probleme . it look like a pretty smal problem.

Hello, I search for this warning above and is nothing to worry. Tell me if you want what problem d you have with this inventory and i help you if i can. But remember the QS inventory need to run after es_extended and before all scripts.

Clicking on the poster below will open a Youtube playlist on the process of upgrading your Quasar CLI project from Quasar v1 to Quasar v2. It may get out of sync as we progress with Quasar v2, but it may help you get started.

This guide refers to Quasar CLI & UMD projects, but information from here can be used for Vue CLI too. For developers already using Vue CLI on your projects you can check out how to install the vue-cli-plugin-quasar package that works with Quasar v2. You will also need to make a few changes to your main.js (and also upgrade your Vue CLI project to support Vue 3) too (best way currently is to generate a new Vue CLI project for Vue 3 and then following the install steps for the vue-cli-plugin-quasar and check out the changes incurred to that /src folder, then apply the same principle to your current Vue CLI project).

Quasar UI v2 is based on Vue 3, as opposed to the previous version which was based on Vue 2. This means that your app code (Vue components, directives, etc) should be Vue 3 compliant too, not just the Quasar UI source-code. If you are using additional libraries in your app, please make sure that you are using their Vue 3 versions.

This guide assumes that you are currently using a @quasar/app v2 project. You will upgrade it to Quasar CLI with Webpack for Quasar v2 (the package is now named @quasar/app-webpack to better differentiate it from Quasar CLI with Vite).

Second option is to create a fresh project and port to it bit by bit. We see this option as a worst case scenario (where you encounter problems with Vue 3 and Vue Router v4 rather than with Quasar itself) and we only mention it for the completeness of this guide.

As part of the upgrade to Webpack 5, Quasar CLI now supplies webpack-dev-server v4 and webpack-dev-middleware v4 which come with their own breaking changes. This influences quasar.config file > devServer options. Below are some of the most used props:

We suggest that you first convert your project to Quasar v2 while maintaining Options API (because your components are already in Options API form and you probably want to ensure everything is working first). After this transition, you can convert all your Vue components to Composition API, but in no way is this a requirement.

Suggestion: you may want to do a search and replace for :value and @input. Please be careful on replacing the :value as some components (QLinearProgress, QCircularProgress) are not tied to v-model and still use value as a property.

We have changed the language pack filenames to reflect the standard naming used by browsers. This will allow you to use $q.lang.getLocale() when you want to dynamically import the Quasar language pack file.

Nothing changed in regards to how App Extensions work. Please note that not all of our App Extensions are yet compatible with Quasar UI v2. We are working towards releasing new compatible versions of them.