[SOLVED] Spinner has disappeared in latest version (@quasar/app v1.9.1/2)

  • This morning I upgraded quasar from

    Pkg quasar........ v1.11.3
    Pkg @quasar/app... v1.8.10


    Pkg quasar........ v1.12.0
    Pkg @quasar/app... v1.9.1

    And now my spinners have disappeared. They have gone from this:
    Screen Shot 2020-05-29 at 10.09.47 AM.png

    to this:
    Screen Shot 2020-05-29 at 10.10.35 AM.png

    I can still see that tiny speck of white rotate, but that is it. Any ideas what could have changed?

  • Now I am not sure if it is directly related to these versions, because installing the earlier versions does not fix the problem. So there is some odd caching or something going on here, still investigating…

  • Ok, I am back to blaming the quasar version. When I restored a snapshot from this morning before doing anything, the spinner worked. When I did NOTHING else other than quasar upgrade -i and relaunch, the spinner was no longer working. I am assuming that a simple npm install quasar@1.11.3 and npm install @quasar/app@1.8.10 did NOT revert all the changes that came with quasar upgrade -i

  • After some more testing, I can definitely narrow the blame to @quasar/app as being the cause of the broken spinner. I have tried both v1.9.1 and v1.9.2 in isolation, and either one of them breaks the spinner for me. Does anyone have any suggestions?

  • Can you make some reproduction code? Codepen or Codesandbox?


  • So I created a minimal new quasar app and placed spinners and they work fine. So I guess this means that there is some conflict with some of the other npms that I have installed, that is only triggered in the latest quasar. I guess I will just start installing npms, one by one in this new app and see when it breaks, sigh.

  • After several painstaking hours of transferring and reinstalling, spinners are now working again. I never did figure out where the conflict was, but I followed a process of only installing things that my app complained were missing, leaving whatever extra items (accumulated in development over the last year) aside. This is probably a good (if painful) practice from time to time.

Log in to reply