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

    Start v0.15 project -> upgrades

    Framework
    5
    21
    3526
    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.
    • bestog
      bestog @snezhkois last edited by

      @snezhkois Yes, your app is on 0.14

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

        to get started with v0.15 :

        npm install -g quasar-cli@next
        quasar init
        
        S 2 Replies Last reply Reply Quote 0
        • S
          snezhkois @benoitranque last edited by

          @benoitranque said in Start v0.15 project -> upgrades:

          npm install -g quasar-cli@next

          i see that i must replace all my code in new version 😞

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

            How can I start with quasar-cli electron or android with 0.15?

            1 Reply Last reply Reply Quote 0
            • S
              snezhkois @benoitranque last edited by

              @benoitranque

              Can I just update quasar without init new project?

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

                @snezhkois Not if you are updating from v0.14, as there are major breaking changes.

                @bestog quasar build --help is all the info you need 🙂

                S bestog 2 Replies Last reply Reply Quote 0
                • S
                  snezhkois @benoitranque last edited by

                  @benoitranque

                  Thanks. Hope other updates will not so “hard” 🙂

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

                    @benoitranque Thank you. I was blind. 😃

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

                      @snezhkois They won’t be, you’ll just have to npm update quasar-framework

                      1 Reply Last reply Reply Quote 0
                      • E
                        ekoster last edited by ekoster

                        Unfortunatly I have an error, the same after two tryouts. If you wonder what happens in a normal cmd window (instead of powershell) it’s the same. This is windows 10 64bit machine. Also I just pressed ENTER with the cordova question (I don’t want it actually). Any tips?

                        [EDIT] I see by default there is not a ‘scripts’ entry for ‘dev’ in ‘package.json’ I’ll see if I need to make that. I though since there is src it would show something with ‘quasar dev’ just like ‘quasar test’ works

                        PS D:\Workspace…\chk\chk> quasar dev
                        D:\Workspace…\chk\chk\node_modules\quasar-cli\bin\quasar-dev:60
                        async function goLive () {
                        ^^^^^^^^
                        SyntaxError: Unexpected token function

                        • module.js:20 require
                          internal/module.js:20:19

                        • quasar:80 Object.<anonymous>
                          [chk]/[quasar-cli]/bin/quasar:80:3

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

                          Make sure you install the latest version of quasar-cli by selecting the next branch.

                          npm install -g quasar-cli@next
                          

                          edit:

                          Also note you must have node version 8+

                          1 Reply Last reply Reply Quote 0
                          • E
                            ekoster last edited by

                            ah then the node must be the issue. I’ll try tonight

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