@pepe-pipo My two cents - we’re solidly on the Vue/Quasar train. The components are world-class, the build tools are great, and the support (we’re a Patreon contributor) is truly excellent. But, don’t let a single guy on a chat board somewhere convince you around decisions concerning your tech stack. Take a day and write the same application in Ionic and Vue/Quasar. A very simple way to feel/decide what is best for you with minimal investment and maximum return.
Posts made by jeffatpf
RE: Why should I choose Quasar instead of Ionic?
RE: Internet Explorer 11 - missing chunk
@rstoenescu - I added transpileDependencies to my quasar.conf > build with two dependencies that I discovered need transpiling (vuex-persist and vue-echarts-v3) and it solved my problem.
You will be receiving a request for an invoice for us - it’s beyond time for us to begin supporting Quaser and rewarding your remarkable efforts! Thank you sir, it’s very much appreciated.
Internet Explorer 11 - missing chunk
Our Quasar app works perfectly on all browsers (Chrome, Safari, Firefox, Edge), except for IE11. I get an error indicating that a chunk cannot be loaded, it’s missing. Any help/tips would be greatly appreciated.
Operating System Darwin(17.7.0) - darwin/x64
yarn Not installed
cordova Not installed
Important local packages
quasar-cli 0.17.22 (Quasar Framework CLI)
quasar-framework 0.17.18 (Build responsive SPA, SSR, PWA, Hybrid Mobile Apps and Electron apps, all simultaneously using the same codebase)
quasar-extras 2.0.9 (Quasar Framework fonts, icons and animations)
vue 2.5.17 (Reactive, component-oriented view layer for modern web interfaces.)
vue-router 3.0.1 (Official router for Vue.js 2)
vuex 3.0.1 (state management for Vue.js)
electron Not installed
electron-packager Not installed
electron-builder Not installed
@babel/core 7.0.0-beta.54 (Babel compiler core.)
webpack 4.25.1 (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 3.1.10 (Serves a webpack app. Updates the browser on changes.)
workbox-webpack-plugin 3.6.3 (A plugin for your Webpack build process, helping you generate a manifest of local files that workbox-sw should precache.)
register-service-worker 1.5.2 (Script for registering service worker, with hooks)
supportIE = true in quasar.conf.js
devDependencies in package.json:
RE: [solved] Auto-logout, or multi-threading/web worker
Check out idle-vue. It works perfectly for same purposes within our application.
RE: Plugins and Entry.js
@rstoenescu - I’ve been using Quasar since it’s early days on this project. In this project there is a file ./quasar/entry.js that is not rewritten on each quasar dev/build.
I just created a new quasar project and there is no ./quasar/entry.js - there is a ./quasar/client-entry.js that is rewritten on each quasar dev/build.
I removed the .quasar/entry.js in my project and rebuilt - a ./quasar/client-entry.js appeared that is rewritten on each quasar dev/build.
RE: Plugins and Entry.js
@s-molinari - Intereresting. (1) I moved the last two (logger/vueapexcharts) to the top of the plugins array, and shuffled the order of the rest. (2) ran ‘quasar dev’ - there were no changes made to the entry.js file. (3) ran ‘quasar build’ - there were no changes made to the entry.js file.
I expected the entry.js file to be changed/updated.
quasar-cli version 0.17.20
quasar-framework version 0.17.17