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 app 2 upgrade

    Framework
    3
    7
    734
    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.
    • A
      amoss last edited by

      Hi

      I want to join to the greetings and thank yous regarding the hard work, this is not taken for granted. The upgrade process itself went smooth, except for 2 issues:

      1. quasar upgrade didn’t upgrade quasar/app, only quasar itself. I needed to manually update quasar/app.

      2. Everything worked after the process but then I deleted node_modules folder and ran npm install. After that, quasar dev ran ok, the console tab is empty but in the network tab I see several 101 and 304 status codes (instead of 200) and neither the main layout (app.vue) nor the first page (login) were shown.

      Has anyone encounter this? If you’re going to delete node_modules, don’t forget to backup your folder.
      1.png

      1 Reply Last reply Reply Quote 0
      • A
        amoss last edited by

        Hi

        I saw a new minor release for quasar/app, is it related to this issue?
        Has anyone else tried to delete and npm install the project after updating to quasar/app 2?
        Thanks

        1 Reply Last reply Reply Quote 0
        • s.molinari
          s.molinari last edited by s.molinari

          Hi.

          Not sure if the fixed issues have to do with yours. But, did you follow the upgrade guide?

          https://quasar.dev/quasar-cli/app-upgrade-guide

          Scott

          1 Reply Last reply Reply Quote 0
          • A
            amoss last edited by

            Ofcourse I did and it works great… Only when I delete node_modules and npm install, the problem occurs.
            Maybe I did something wrong but I have no idea what because I don’t get a clear error except for those codes in the network tab.

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

              try using yarn for local deps, since npm doesn’t work well with it. npm for global, yarn for local.

              1 Reply Last reply Reply Quote 0
              • A
                amoss last edited by

                You mean to delete node_modules folder and then run yarn install?

                1 Reply Last reply Reply Quote 0
                • s.molinari
                  s.molinari last edited by

                  Yeah. We highly recommend using Yarn for local dependencies.

                  Scott

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