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

    Quasar v0.15.3 is out!

    Announcements
    7
    17
    2478
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • rstoenescu
      rstoenescu Admin last edited by

      Fixes and enhancements:

      • Reactivity improvement for i18n, iconSet, appFullscreen, appVisibility #1613
      • Hebrew language pack
      • Luxembourgish language pack
      • QItemTile not rendering tag property #1638
      • QToolbarTitle “shrink” prop #1629
      • Inclusive Date Range #868
      • QField should allow to set icon color #1577

      Enjoy!

      1 Reply Last reply Reply Quote 3
      • cheebhodh
        cheebhodh last edited by

        Thank you master 🙂

        1 Reply Last reply Reply Quote 0
        • Akaryatrh
          Akaryatrh last edited by Akaryatrh

          Hi @rstoenescu

          My question looks kinda stupid, but… how are we supposed to upgrade from 0.15.1 to 0.15.3? Is updating the CLI sufficient?
          Moreover, if I update through npm update It will upgrade only my local quasar-cli, so what is your recommendation ?

          H 1 Reply Last reply Reply Quote 0
          • H
            hughmacdonald @Akaryatrh last edited by

            @akaryatrh Did you manage to figure this out? I’d like to upgrade a project to 0.15.3. Do I just need to init a new project and copy across the files?

            1 Reply Last reply Reply Quote 0
            • benoitranque
              benoitranque last edited by

              @Akaryatrh @hughmacdonald

              This does the trick

              npm update quasar-cli
              
              1 Reply Last reply Reply Quote 0
              • Akaryatrh
                Akaryatrh last edited by

                @benoitranque And then the .quasar folder at root of my project will be updated on next build?

                1 Reply Last reply Reply Quote 0
                • J
                  jeffatpf last edited by

                  @benoitranque There seems to be a bit of confusion as to the nature of the local quasar-cli and the global quasar-cli. I ran “npm install -g quasar-cli” and “npm install --save-dev quasar-cli” (as defined within package.json) to install it locally. Could you elaborate on how to update locally vs. globally?

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    sarndt @jeffatpf last edited by

                    @jeffatef said in Quasar v0.15.3 is out!:

                    @benoitranque There seems to be a bit of confusion as to the nature of the local quasar-cli and the global quasar-cli. I ran “npm install -g quasar-cli” and “npm install --save-dev quasar-cli” (as defined within package.json) to install it locally. Could you elaborate on how to update locally vs. globally?

                    It should be sufficient to do a local “npm up”, have you tried that?

                    1 Reply Last reply Reply Quote 0
                    • benoitranque
                      benoitranque last edited by benoitranque

                      @Akaryatrh Yes

                      @jeffatef local update: from project folder

                      npm update quasar-cli
                      

                      global update: from anywhere

                      npm update -g quasar-cli
                      
                      H 1 Reply Last reply Reply Quote 0
                      • H
                        hughmacdonald @benoitranque last edited by hughmacdonald

                        @benoitranque So just to be absolutely clear, do I need to both run the npm update quasar-cli command in the project folder and run sudo npm update -g quasar-cli to upgrade the quasar version?

                        1 Reply Last reply Reply Quote 0
                        • rstoenescu
                          rstoenescu Admin last edited by

                          http://quasar-framework.org/guide/quasar-upgrade-guide.html

                          H 1 Reply Last reply Reply Quote 0
                          • H
                            hughmacdonald @rstoenescu last edited by

                            @rstoenescu Thank you very much for updating that doc (and for such an awesome framework in general). I’ve read it, but I am still a bit confused. Clearly I can run “npm install quasar-cli@latest” in my project until 1.0 gets released, and I can update the local version of quasar. But I don’t understand how this interacts with the global version, which I needed to install with sudo on Ubuntu?

                            1 Reply Last reply Reply Quote 0
                            • rstoenescu
                              rstoenescu Admin last edited by

                              Global version yields control to project-locally installed version. It’s just a simple way of being able to globally use “quasar” commands without having to specify ./node_modules/quasar-cli/bin/quasar ....

                              1 Reply Last reply Reply Quote 0
                              • H
                                hughmacdonald last edited by hughmacdonald

                                OK, so I don’t need to update globally while still using 0.15.x locally, only when 1.0 comes out? unless i want to generate a new starter kit with the latest 0.15.x version in the mean time.

                                1 Reply Last reply Reply Quote 0
                                • rstoenescu
                                  rstoenescu Admin last edited by

                                  Exactly.

                                  H 1 Reply Last reply Reply Quote 0
                                  • H
                                    hughmacdonald @rstoenescu last edited by

                                    @rstoenescu Awesome, thanks so much for replying. It might be worth making that a little bit clearer in the docs for dullards like me. 🙂

                                    1 Reply Last reply Reply Quote 0
                                    • Akaryatrh
                                      Akaryatrh last edited by Akaryatrh

                                      Thx for clarifications @rstoenescu & @benoitranque

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post