Navigation

    Quasar Framework

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. Manieck
    M
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 6
    • Best 0
    • Groups 0

    Manieck

    @Manieck

    0
    Reputation
    11
    Profile views
    6
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    Manieck Follow

    Latest posts made by Manieck

    • RE: Form input autofill background color in Chrome

      HI! I also got the same problem, Does anyone know how to solve it?

      posted in Framework
      M
      Manieck
    • RE: Dynamic/Lazy Loading component not working

      Hi

      The reason is @babel/parser@7.8.4 which is installed as we generate a new quasar project.

      There are two solutions.

      First.
      Change inline declarations

      : import(`./AppComponents/${this.componentName}.vue`);
      

      for

      : import('./AppComponents/' + this.componentName + '.vue');
      

      It works with @babel/parser@7.8.4

      Second.
      Delete folder ./node_modules/babel/parser
      Install @babel/parser@7.7.5:
      Add in package.json “@babel/parser”: “7.7.5”

      "devDependencies": {
          "@babel/core": "^7.6.2",
          "@quasar/app": "^1.0.0",
          "@babel/parser": "7.7.5",
          "@vue/eslint-config-standard": "^4.0.0",
          "babel-eslint": "^10.0.1",
          "eslint": "^5.10.0",
          "eslint-loader": "^2.1.1",
          "eslint-plugin-vue": "^5.2.2",
          "sass": "^1.25.0",
          "sass-loader": "^8.0.2"
        },
      
      npm install
      

      or directly

      npm install @babel/parser@7.7.5
      

      Works with inline declarations.

      Thank you for helping me find the reason.

      posted in Help
      M
      Manieck
    • Dynamic/Lazy Loading component not working

      Re: dynamic/lazy component import with runtime generated path not working with v1

      Hi,
      I’m in the process of migrating from Nuxt project to Quasar. Many things already work, but I have a problem with it.

      My code

      computed: {
          componentFile() {
            return () => this.componentName === ''
              ? import('./AppComponents/emptyComponent.vue')
              : import(`./AppComponents/${this.componentName}.vue`);
          }
        }
      

      Error

      Module build failed (from ./node_modules/eslint-loader/index.js):
        TypeError: Cannot read property 'range' of null
        Occurred while linting D:\Workspace\p1\qfrontend\src\components\PreviewComponent.vue:23
      

      In Nuxt this is working properly.

      posted in Help
      M
      Manieck
    • RE: Migrating Nuxt project to Quasar - Absolute path

      I think I found a solution. I don’t know if it’s the correct, but it works.
      In the quasar.conf.js file I added:

      // Full list of options: https://quasar.dev/quasar-cli/quasar-conf-js#Property%3A-build
          build: {
            ...
            extendWebpack (cfg) {
              cfg.resolve.alias = {
                ...cfg.resolve.alias,
                '~/util': path.resolve(__dirname, './src/util')
              }
              ...
            }
            ...
          },
      
      posted in Help
      M
      Manieck
    • Migrating Nuxt project to Quasar - Absolute path

      Hi,

      I just started to migrate project from Nuxt to Quasar. I have a problem with importing modules.
      I would like to import using absolute path like Nuxt:

      import { objectActions } from '~/util/defs';
      

      but it is not working

      This dependency was not found:
      
      * ~/util/defs in ./node_modules/babel-loader/lib??ref--1-0!./node_modules/@quasar/app/lib/webpack/loader.auto-import.js?kebab!./node_modules/vue-loader/lib??vue-loader-options!./src/pages/Index.vue?vue&type=script&lang=js&
      
      To install it, you can run: npm install --save ~/util/defs
      

      It doesn’t work either

      import { objectActions } from '@util/defs';
      

      After change to relative path is OK.

      import { objectActions } from '../util/defs';
      

      I tried to move my module to folder components, pages and it’s work!

      import { objectActions } from 'components/defs';
      

      I guess it’s a Webpack problem but I don’t know much about it yet.

      How to get to the root of the project in Quasar?
      How can I define an additional folder so that I can reference it like ‘components/…’, ‘pages/…’, etc.?

      Regards

      posted in Help
      M
      Manieck
    • How to remove {cursor: not-allowed !important} from class .disabled?

      Hi

      I am a beginner in Quasar.
      I would like to disable the not-allowed mouse pointer that appears above disabled components.
      I tried to add my own styles, but it doesn’t work.
      I do not know how to do this.
      Have any ideas?

      posted in Help
      M
      Manieck