No More Posting New Topics!

Hi,
I have the same problem now.
Is there a solution?

Thanks in advance,

where you able to fix this am fixing same issue

@steve

devServer: { https: false, port: 8080, open: 'chrome' // opens browser window automatically },

For automatically opening Google Chrome

I never found an answer documented but I think my hunch worked.

import { mountFactory } from '@quasar/quasar-app-extension-testing-unit-jest' import { QMenu, QList, QItemLabel, QItem, QItemSection, QIcon, QBtn, ClosePopup, } from 'quasar' import HelpMenu from '../../../../src/components/menus/HelpMenu.vue' const $t = jest.fn() // $t.mockReturnValue('') const factory = mountFactory(HelpMenu, { mount: { mocks: { $t }, }, quasar: { components: { QMenu, QList, QItemLabel, QItem, QItemSection, QIcon, QBtn, }, directives: { ClosePopup, }, }, }) describe('HelpMenu', () => { test('mount w/o error', () => { console.log(factory()) expect(factory).toBeTruthy() }) })

I no longer see the error message.

@sebag well, late to the party, but you could do something like…

actions: [ { icon: 'close', color: 'white', handler: () => {}, }, ],

and your css could be…

.q-notification__actions .q-btn__wrapper.col.row.q-anchor--skip { padding: 0px !important; font-size: 8px !important; } .q-notification__actions .q-btn__wrapper.col.row.q-anchor--skip i { position: absolute; top: -10px; font-weight: bold; }

Rejoining this thread, because I’ve figured out a complete solution for a user controlled app refresh (similar to the pop-up in the Quasar documentation) that might be useful for others who have the same issue. It’s a combination of ideas taken from the Workbox Advanced Recipes (https://developers.google.com/web/tools/workbox/guides/advanced-recipes#offer_a_page_reload_for_users) and an article by Doug Allrich. It uses the Workbox-Window plug-in from Google.

<template> <q-dialog v-model="displayUpdatePrompt"> <q-banner> A new version is available. <template v-slot:action> <q-btn label="Update" @click="refreshApp" /> </template> </q-banner> <q-dialog> </template> <script> import { Wokbox } from 'workbox-window' export default { data() { return { displayUpdatePrompt: false, workbox: null, } }, methods: { refreshApp() { this.workbox.addEventListener('controlling', () => { window.location.reload() }) this.workbox.messageSkipWaiting() } }, created() { if ('service-worker' in navigator) { this.workbox = new Workbox('/service-worker.js') this.workbox.addEventListener('waiting', (event) => { this.displayUpdatePrompt = true }) this.workbox.register() } } } </script>

@cata-orellana
https://github.com/quasarframework/quasar/discussions/9065

useServiceWorker is deprecated

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 Global packages 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 typescript - 4.2.2 -- TypeScript is a language for application scale JavaScript development @capacitor/core - Not installed @capacitor/cli - Not installed @capacitor/android - Not installed @capacitor/ios - Not installed Quasar App Extensions *None installed* $ 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 Example usage $ quasar <command> <options> Help for a command $ quasar <command> --help $ quasar <command> -h Options --version, -v Print Quasar App CLI version Commands 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.

conseguiu resolver seu problema?

Sorry, in my previous post you should only comment in quasar.conf.js, the line with “roboto-font” and decomment “material-icons”

Thanks for sharing the “Quasar v1 to v2 Upgrade Video Tutorials” with us. It is really useful for us.
office.com/setup

@turigeza cannot agree more!

What is really happening is that you’re referencing your store’s todos to components’s todos to.
You should clone the array instead:

I found myself in the same situation but with members, and this solved the issue:

const clonedMembers: [...this.formData.members] // then you call the mutation with the clone

Yes… is a pain in the ass.

I think this is solved in Vue3.

Just a note: Be sure the style is not scoped to your component.
In Electron this works:

<style> input[type="number"]::-webkit-outer-spin-button, input[type="number"]::-webkit-inner-spin-button { -webkit-appearance: none; margin: 0; } </style>

But, <style scoped>…</style> doesn’t.

Scoping the style appears to work in browsers, but failed for me in Electron.

@dsl101

I agree, you could create feature request in github:
https://github.com/quasarframework/quasar/issues

or open a new discussion about it on the new forum( this forum is dead):
https://github.com/quasarframework/quasar/discussions

@damiendeville

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.

Vue Formulate has a newer generate-from-schema option (https://vueformulate.com/guide/forms/generating-forms/), but currently lacks much of the repeater/validators that the “statically-defined in template” method offers.

BlitzarForm (https://blitzar.cycraft.co/docs/blitz-form) is a new effort that also allows any component, so all Quasar components could be used.

For something more than a pet project, I’m nervous to “place a bet” on what would be used by my company for years to come!