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. ajmas
    A
    • Profile
    • Following 0
    • Followers 0
    • Topics 3
    • Posts 5
    • Best 0
    • Groups 0

    ajmas

    @ajmas

    0
    Reputation
    3
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    ajmas Follow

    Latest posts made by ajmas

    • Upgrading to Quasar 2 breaks PreloadWebpackPlugin?

      Prior to Quasar 2 we have been using @vue/preload-webpack-plugin to have our resources preloaded, but it would seem that the htmlWebpackPlugin is no longer part of Quasar.

      This plugin had resolved the issue of partially loaded chunks and dependencies when uses an SPA in a situation with poor internet connectivity. We did not find that preloadChunks was sufficient to deal with this in the past.

      Can anyone suggest an alternative approach to having the preload attribute added against loaded resources, or at the very least ensure all resources are loaded up front?

      Environment:

      • NodeJS: 14.15.1
      • @vue/preload-webpack-plugin: 1.1.2
      • @quasar/app: 2.1.14
      posted in Framework
      A
      ajmas
    • RE: Method's first letter gets dropped, produces "Property _________ does not exist on type 'CombinedVueInstance'"

      I recently ran into this issue, or at least one that resembles it. After some exploration I discovered another dev had introduced a .vscode/settings.json file that contained the following entry:

      "vetur.experimental.templateInterpolationService": true
      

      Removing this line resolved things for me.

      BTW My approach was to compare a project that worked and one that didn’t. Since my project was not Typescript based and I was using the same Vue version in both project, this left any possible settings that we VS Code and project specific.

      I am currently using Vetur 0.28.0, with Visual Studio Code 1.50.0, on macOS 10.15.6.

      posted in Framework
      A
      ajmas
    • RE: Upgrading to 1.x - Unknown import: QLayoutHeader

      Thanks.

      Also jumping into the components section of the docs and generating a new reference project, I see certain elements have changed structure. One such example being the list items.

      https://quasar.dev/vue-components/list-and-list-items

      posted in Framework
      A
      ajmas
    • Where is the guide?

      Most of the Quasar related Google searches take me towards pages in the guide: https://quasar-framework.org/guide/ , but most are ending up with 404. Can anyone suggest what happened?

      Examples:

      • https://quasar.dev/guide/ssr-introduction.html
      • https://quasar.dev/guide/quasar-upgrade-guide.html
      posted in Help
      A
      ajmas
    • Upgrading to 1.x - Unknown import: QLayoutHeader

      I am in the process of upgrading from Quasar 0.17.x to 1.0.0-rc.2 and the build is now failing with:

      ERROR in ./.quasar/import-quasar.js
      Module build failed (from ./node_modules/babel-loader/lib/index.js):
        Error: Unknown import from Quasar: QLayoutHeader
        
        - imports.js:167 module.exports
          [client]/[quasar]/dist/babel-transforms/imports.js:167:11
        
        - index.js:64 transform
          [client]/[babel-plugin-transform-imports]/index.js:64:16
        
        - index.js:138 
          [client]/[babel-plugin-transform-imports]/index.js:138:39
      
      ...
      

      Can anyone indicate what I need to change to get this definition?

      posted in Framework
      A
      ajmas