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. tmladek
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 12
    • Best 1
    • Groups 0

    tmladek

    @tmladek

    1
    Reputation
    278
    Profile views
    12
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    tmladek Follow

    Best posts made by tmladek

    • Platform detection no longer works in 0.15 (import { Platform } from 'quasar')

      Hi,
      I just upgraded to Quasar 0.15, and I found that my page does not render and throws the following error in the console:

        TypeError: __WEBPACK_IMPORTED_MODULE_2_quasar__.b.is is undefined
      

      I tracked it to the if (Platform.is.cordova) line, which worked fine before the upgrade. But now when I import { Platform } from 'quasar', the Platform object looks as follows (as found out with console.log):

      __installed: false
      install: install()
      length: 1
      name: "install"
      __proto__: function ()
      __proto__: Object { … }
      

      i.e. it doesn’t really look like much.

      Am I doing something wrong? This part of the docs (http://quasar-framework.org/components/platform-detection.html) has stayed the same even for the 0.15 version.

      Thanks!

      posted in Help
      tmladek
      tmladek

    Latest posts made by tmladek

    • How to use "Speed Measure Plugin" - or other build profiling?

      Building my app, from start to finish, takes about 4-5 minutes, which is quite long.

      I would like to use the Speed Measure Plugin to see what are the points that take up the most time so I can start optimizing, but according to it’s readme, the intended usage is to wrap and replace the entire config:

      const SpeedMeasurePlugin = require('speed-measure-webpack-plugin');
      
      const webpackConfig = smp.wrap({
        plugins: [
          new MyPlugin(),
          new MyOtherPlugin()
        ]
      });
      

      However, according to the Quasar docs, the extendWebpack() function allows just that - extending the config, but it doesn’t seem to allow replacing it entirely.

      I still tried returning the wrapped config like vue.config.js's configureWebpack() would allow:

      const SpeedMeasurePlugin = require('speed-measure-webpack-plugin');
      
      // ...
            extendWebpack (cfg) {
                  return smp.wrap(cfg);
            }
      // ...
      

      But I Immediately get this error when trying to build it:

      (node:42345) UnhandledPromiseRejectionWarning:   TypeError: Cannot read property 'tapAsync' of undefined
      

      Which makes me think I’m doing something wrong.

      Did anybody get this plugin to work with Quasar? Or does anyone have any recommendations about other plugins that could be used to profile the build? Thanks!

      posted in Help
      tmladek
      tmladek
    • RE: QCard assumes any color I set is dark?

      Submitted an issue: https://github.com/quasarframework/quasar/issues/2546

      posted in Help
      tmladek
      tmladek
    • RE: QCard assumes any color I set is dark?

      It doesn’t seem like you’re setting the color of the QCard though?

      posted in Help
      tmladek
      tmladek
    • QCard assumes any color I set is dark?

      Hello, I’ve noticed that no matter what color I pass as the color prop to QCard, it colors the text white and adds a q-card-dark class to the outermost <div> of the QCard, which also causes the separator to be white.

      This happens even when setting the color to white, which means the QCard appears completely blank.

      Is this a bug? Or can this be overriden? I know I can pass the textColor prop to override the text color, but this doesn’t change the color of the separator.

      posted in Help
      tmladek
      tmladek
    • TypeScript migration woes (webpack can't resolve plugins, store, etc in entry.js)

      Hello,
      I decided to migrate my project to TypeScript, so I followed all the steps for migrating a Vue project to TS, but now I ran into a webpack issue:

      $ quasar build
       app:build Mode [ SPA ] with [ MAT ] theme +0ms
      
       app:quasar-conf Reading quasar.conf.js +362ms
       app:quasar-conf Generating Webpack config +194ms
       app:quasar-conf Extending Webpack config +458ms
       app:artifacts Cleaned build artifact: "/home/t/cis/cis-dashboard-app/dist/spa-mat" +5ms
       app:generator Generating Webpack entry point +0ms
       app:build Building main... +2ms
      
      Starting type checking service...
      Using 1 worker with 2048MB memory limit
      Build completed in 9.11s
      
      /* snip */
      
      ERROR in ./.quasar/entry.js
      Module not found: Error: Can't resolve '../src/router' in '/my/app/.quasar'
       @ ./.quasar/entry.js 25:37-61
       @ multi ./.quasar/entry.js
      
      ERROR in ./.quasar/entry.js
      Module not found: Error: Can't resolve 'src/plugins/auth' in '/my/app/.quasar'
       @ ./.quasar/entry.js 27:35-62
       @ multi ./.quasar/entry.js
      
      ERROR in ./.quasar/entry.js
      Module not found: Error: Can't resolve 'src/plugins/axios' in '/my/app/.quasar'
       @ ./.quasar/entry.js 29:36-64
       @ multi ./.quasar/entry.js
      
      ERROR in ./.quasar/entry.js
      Module not found: Error: Can't resolve 'src/plugins/cordova-etc' in '/my/app/.quasar'
       @ ./.quasar/entry.js 35:41-75
       @ multi ./.quasar/entry.js
      
      ERROR in ./.quasar/entry.js
      Module not found: Error: Can't resolve 'src/plugins/i18n' in '/my/app/.quasar'
       @ ./.quasar/entry.js 31:35-62
       @ multi ./.quasar/entry.js
      
      ERROR in ./.quasar/entry.js
      Module not found: Error: Can't resolve 'src/plugins/notifications' in '/my/app/.quasar'
       @ ./.quasar/entry.js 33:44-80
       @ multi ./.quasar/entry.js
      
       app:build [FAIL] Build failed with errors +0ms
      

      The entry.js file (which is apparently generated somewhere in the build process by quasar?) is still a .js file, and thus the plugin imports:

      import pluginAuth from 'src/plugins/auth'
      plugins.push(pluginAuth)
      

      and other imports fail.

      The relevant portion of my quasar.conf.js is:

      extendWebpack (cfg) {
          cfg.module.rules.push({
            enforce: 'pre', // tried both with and without, no luck
            test: /\.ts$/,
            loader: 'ts-loader',
            options: {
              appendTsSuffixTo: [/\.vue$/],
              transpileOnly: true
            }
          })
          cfg.plugins.push(new ForkTsCheckerWebpackPlugin())
          // disabled temporarily eslint before I get this mess of a build process working
          // cfg.module.rules.push({
          //   enforce: 'pre',
          //   test: /\.(js|vue)$/,
          //   loader: 'eslint-loader',
          //   exclude: /(node_modules|quasar|src-cordova)/
          // })
      }
      

      Any ideas how to get the build to work? Thanks!

      posted in Help
      tmladek
      tmladek
    • RE: 'undefined' error due to missing Platform plugin when using Popover

      Hello again! I’m afraid that this issue might have solved itself.

      I realized I accidentally lied about the <q-popover> being a direct child of <q-btn>, because it was in a different component (of which the QPopover was the root element). Changing this and putting the <q-popover> directly in the parent component solved the issue, so I thought this was the problem; but when I reverted back to it being separate, it actually still works and I can’t reproduce the error.

      posted in Help
      tmladek
      tmladek
    • 'undefined' error due to missing Platform plugin when using Popover

      Hello!
      I’m trying to use a QPopover as in the docs (i.e. the <q-popover> is a direct descendant of <q-btn>), but when I click the button, I get this error:
      TypeError: __WEBPACK_IMPORTED_MODULE_0__plugins_platform__.a.is is undefined

      edit: above error in Firefox, Chrome provides the much more descriptive Uncaught TypeError: Cannot read property 'desktop' of undefined.

      I’ve tracked it down to the file escape-key.js, which checks the Platform object; which my debugger confirms is indeed undefined:

      0_1528900204767_scrnsht.png

      The QPopover is correctly included in components in quasar.conf.js, as well as Platform in plugins, and I am not sure what else could be the cause of this error.

      Thanks in advance!

      posted in Help
      tmladek
      tmladek
    • RE: How to easily emulate responsiveness of QDatetime input (i.e. open in modal on mobile but as a popover on desktop)

      Any help please?

      posted in Help
      tmladek
      tmladek
    • How to easily emulate responsiveness of QDatetime input (i.e. open in modal on mobile but as a popover on desktop)

      Hello,
      I have a menu with a couple options that I would like to open just like QDatetime opens - in a modal on small screens, and as a popover on desktop.
      Of course, I can always make two components and just dynamically select between which one to render, but I was wondering whether there was an easy, or rather a ‘preferred’ way to do this (that wouldn’t involve duplicating code for the menu options, etc).
      Thanks in advance!

      posted in Help
      tmladek
      tmladek
    • Platform detection no longer works in 0.15 (import { Platform } from 'quasar')

      Hi,
      I just upgraded to Quasar 0.15, and I found that my page does not render and throws the following error in the console:

        TypeError: __WEBPACK_IMPORTED_MODULE_2_quasar__.b.is is undefined
      

      I tracked it to the if (Platform.is.cordova) line, which worked fine before the upgrade. But now when I import { Platform } from 'quasar', the Platform object looks as follows (as found out with console.log):

      __installed: false
      install: install()
      length: 1
      name: "install"
      __proto__: function ()
      __proto__: Object { … }
      

      i.e. it doesn’t really look like much.

      Am I doing something wrong? This part of the docs (http://quasar-framework.org/components/platform-detection.html) has stayed the same even for the 0.15 version.

      Thanks!

      posted in Help
      tmladek
      tmladek