No More Posting New Topics!

If you have a question or an issue, please start a thread in our Github Discussions Forum.
This forum is closed for new threads/ topics.

Navigation

    Quasar Framework

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

    Topics created by Manieck

    • M

      Dynamic/Lazy Loading component not working
      Help • • Manieck

      4
      0
      Votes
      4
      Posts
      251
      Views

      M

      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.

    • M

      Migrating Nuxt project to Quasar - Absolute path
      Help • • Manieck

      2
      0
      Votes
      2
      Posts
      65
      Views

      M

      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') } ... } ... },
    • M

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

      3
      0
      Votes
      3
      Posts
      89
      Views

      I

      turns out that just selecting “.disabled class” is not enough, you also need to match children:

      so adding this to css/app.scss works for me.

      .disabled, .disabled *{
      cursor: auto !important;
      }