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. marek.kaczkowski
    • Profile
    • Following 0
    • Followers 0
    • Topics 2
    • Posts 4
    • Best 1
    • Groups 0

    marek.kaczkowski

    @marek.kaczkowski

    1
    Reputation
    243
    Profile views
    4
    Posts
    0
    Followers
    0
    Following
    Joined Last Online
    Location Wrocław, Poland Age 39

    marek.kaczkowski Follow

    Best posts made by marek.kaczkowski

    • `Quasar App Extension "serve" is missing` error

      Hey Quasarians,
      I’m struggling with a strange problem related with @quasar/cli or yarn/npm on Win10.
      Assume that you have command that runs quasar serve so when you run it via cmd (on Windows 10) it works, no issue.

      BUT when you add script to your project package.json that rusn quasar serve
      you get and error Quasar App Extension "serve" is missing... because it runs local quasar app not the global cli as it should.

      Test1:

      >where quasar
      C:\Users\user\AppData\Roaming\npm\bin\quasar
      C:\Users\user\AppData\Roaming\npm\bin\quasar.cmd
      
      # add "where" script to package.json (quasar project)
      # "scripts": { "where": "where quasar" }
      
      > npm/yarn run where
      C:\repos\some-quasar-poject\node_modules\.bin\quasar
      C:\repos\some-quasar-poject\node_modules\.bin\quasar.cmd
      C:\Users\user\AppData\Roaming\npm\bin\quasar
      C:\Users\user\AppData\Roaming\npm\bin\quasar.cmd
      

      Test2

      >quasar info
      Operating System - Windows_NT(10.0.16299) - win32/x64
      NodeJs - 12.13.1
      
      Global packages
        NPM - 6.12.1
        yarn - 1.19.2
        @quasar/cli - 1.0.3 <----------------------------------
        cordova - Not installed
      
      # add "info" script to package.json (quasar project)
      # "scripts": { "info": "quasar info" }
      
      > npm/yarn run info
      Operating System - Windows_NT(10.0.16299) - win32/x64
      NodeJs - 12.13.1
      
      Global packages
        NPM - 6.12.1
        yarn - 1.19.2
        @quasar/cli - undefined <------------------------------
        cordova - Not installed
      

      So "serve:test:coverage": "quasar serve test/jest/coverage/lcov-report/ --port 8788", ain’t gonna work 😞
      Shouldn’t global quasar cli come first?

      PATH without custom stuff so there are only npm and yarn

      C:\Users\user\AppData\Roaming\npm
      C:\Users\user\AppData\Local\Yarn\bin
      C:\Users\user\AppData\Roaming\npm\bin
      

      Edit:

      Reported on gh: https://github.com/quasarframework/quasar-testing/issues/97

      IMHO there should be an exception for serve in local quasar executable that runs cli command instead of local.

      posted in CLI
      marek.kaczkowski
      marek.kaczkowski

    Latest posts made by marek.kaczkowski

    • `Quasar App Extension "serve" is missing` error

      Hey Quasarians,
      I’m struggling with a strange problem related with @quasar/cli or yarn/npm on Win10.
      Assume that you have command that runs quasar serve so when you run it via cmd (on Windows 10) it works, no issue.

      BUT when you add script to your project package.json that rusn quasar serve
      you get and error Quasar App Extension "serve" is missing... because it runs local quasar app not the global cli as it should.

      Test1:

      >where quasar
      C:\Users\user\AppData\Roaming\npm\bin\quasar
      C:\Users\user\AppData\Roaming\npm\bin\quasar.cmd
      
      # add "where" script to package.json (quasar project)
      # "scripts": { "where": "where quasar" }
      
      > npm/yarn run where
      C:\repos\some-quasar-poject\node_modules\.bin\quasar
      C:\repos\some-quasar-poject\node_modules\.bin\quasar.cmd
      C:\Users\user\AppData\Roaming\npm\bin\quasar
      C:\Users\user\AppData\Roaming\npm\bin\quasar.cmd
      

      Test2

      >quasar info
      Operating System - Windows_NT(10.0.16299) - win32/x64
      NodeJs - 12.13.1
      
      Global packages
        NPM - 6.12.1
        yarn - 1.19.2
        @quasar/cli - 1.0.3 <----------------------------------
        cordova - Not installed
      
      # add "info" script to package.json (quasar project)
      # "scripts": { "info": "quasar info" }
      
      > npm/yarn run info
      Operating System - Windows_NT(10.0.16299) - win32/x64
      NodeJs - 12.13.1
      
      Global packages
        NPM - 6.12.1
        yarn - 1.19.2
        @quasar/cli - undefined <------------------------------
        cordova - Not installed
      

      So "serve:test:coverage": "quasar serve test/jest/coverage/lcov-report/ --port 8788", ain’t gonna work 😞
      Shouldn’t global quasar cli come first?

      PATH without custom stuff so there are only npm and yarn

      C:\Users\user\AppData\Roaming\npm
      C:\Users\user\AppData\Local\Yarn\bin
      C:\Users\user\AppData\Roaming\npm\bin
      

      Edit:

      Reported on gh: https://github.com/quasarframework/quasar-testing/issues/97

      IMHO there should be an exception for serve in local quasar executable that runs cli command instead of local.

      posted in CLI
      marek.kaczkowski
      marek.kaczkowski
    • RE: Testing

      Hey,

      Good news (Qusar v0.15.1x)
      I spent last month on configuring Qusar v0.15.1x with Jest 22 and Babel 6. It was real pain in the ass (today I’m thinking about better runner than jest). Important - it works as expected (tests, coverage, reporting to sonar). Will try to find time to publish example project on GH.

      Bad news (Qusar v0.16.xx)
      Yesterday I started migration to Quasar v0.16.xx, Jest 23 and Babel 7.
      Right now striggling with module-resolver and vue files,

      Test suite failed to run
          TypeError: Cannot read property 'includes' of undefined
                at node_modules/babel-plugin-module-resolver/lib/normalizeOptions.js:148:22
                at node_modules/reselect/lib/index.js:86:37
                at node_modules/reselect/lib/index.js:36:25
                at PluginPass.pre (node_modules/babel-plugin-module-resolver/lib/index.js:53:60)
                at transformFile (node_modules/@babel/core/lib/transformation/index.js:98:25)
                at runSync (node_modules/@babel/core/lib/transformation/index.js:35:3)
                at transformSync (node_modules/@babel/core/lib/transform-sync.js:15:38)
                at Object.transform (node_modules/@babel/core/lib/transform.js:20:65)
                at compileBabel (node_modules/vue-jest/lib/compilers/babel-compiler.js:21:21)
                at processScript (node_modules/vue-jest/lib/process.js:29:10)
      
      posted in Help
      marek.kaczkowski
      marek.kaczkowski
    • QTypeahead like Twitter's Typeahead

      Hey,
      I’m trying to reproduce Twitter’s Typeahead with

      • QTree component (nested data),
      • QTree filter input,
      • and dropdown.

      At the moment I found few places for improvements:

      • would be nice to bold filtered string in QTree nodes
      • collapse lost-match nodes on backspace

      I want to reproduce it with pure Quasar components (no external packages) and will PR it to Quasar Play repo when I’m done 🙂

      posted in Help
      marek.kaczkowski
      marek.kaczkowski
    • RE: [0.15.1] Components registering within Jest tests

      @vinstah thank you! You saved my life 😉

      Is there a guide how to inject layout when my template root element is a q-page?
      At the moment test yelds QPage needs to be child of QPageContainer, when I remove root q-page (so q-table is root template element) test works.

      posted in Help
      marek.kaczkowski
      marek.kaczkowski