Quasar v1.0-beta.3 released!

  • Admin


    • fix(QStepper): V1: Qstep with :disable=‘false’ will reset the stepper to step1 when next is triggered. #3307
    • fix(QSelect): [v1] q-select multiple with chips doesn’t lock disabled entries #3314
    • fix(QSelect): [v1] QSelect lazy loading with map options spews “Cannot read property ‘find’ of null” stack traces #3315
    • fix(quasar): zh-hans language pack for QDate #3298
    • fix(QSelect): Scroll not possible when max-height is larger than height of 20 items
    • fix(quasar): QDialog does not accept class attribute #3299
    • fix(quasar): [v1] Dialog docs, maximized demo breaks page if closed after minimizing #3310
    • Fix distorted UI on checkbox/radio/toggle with long label (#3302)
    • fix(QDate): [v1]QDate - What day of the week is incorrect #3297
    • fix(Panel): [v1] QCarouselSlide cannot handle name=“0”. #3295
    • fix(QBtnToggle): [v1] QBtnToggle - Icon-Text-Margin missing #3294

  • up, up and away! 🙂


  • Very nice.
    What’s the simplest way to upgrade from beta2 to beta3 asuming no breaking changes?

  • @paul - yarn upgrade. 😄


  • @s-molinari ah cool. Still a bit confused between framework update and app update. Thanks a lot.

  • or npm outdated, then npm update all inside your quasar project folder, if you’re using NPM.

  • Thank you for the fast and awesome work.

  • am I the only one who got the router broken on lazy load after upgrade to beta.3 ?

    Module parse failed: Unexpected token (4:11)
    You may need an appropriate loader to handle this file type.
    |   path: '/',
    |   component: function component() {
    >     return import('./../layouts/default-layout.vue');
    |   },
    |   children: [{
     @ ./src/router/index.js 3:0-30 19:12-18
     @ ./.quasar/app.js
     @ ./.quasar/client-entry.js
     @ multi (webpack)-dev-server/client? (webpack)/hot/dev-server.js ./.quasar/client-entry.js

  • @labs20 said in Quasar v1.0-beta.3 released!:

    or npm outdated, then npm update all inside your quasar project folder, if you’re using NPM.

    what does “npm outdated” do? what’s that for?

  • PWA is not working for me… Everything gets build, but it doesnt work offline, and it has no “add to homescreen” banner as it used to in v 0.17.
    What am I missing?

  • @luis-gilbert - Can you start a new thread please?

    And in general everyone. Let’s please not ask questions or raise possible issues in the release threads. It’s better to start new threads for that.



  • @ben-hayat This command will check the registry to see if any (or, specific) installed packages are currently outdated.

Log in to reply