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

    this.$q is undefined

    Framework
    4
    12
    4206
    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.
    • rubs
      rubs last edited by

      Actually I already did this, several times. I even cleared up all my global npm modules and reinstalled everything, to no effect. Thanks anyway!

      dobbel 1 Reply Last reply Reply Quote 0
      • dobbel
        dobbel @rubs last edited by

        @rubs

        What’s the output of quasar info ?

        What if you try it in a VM or other computer?

        rubs 1 Reply Last reply Reply Quote 0
        • rubs
          rubs @dobbel last edited by

          @dobbel, quasar info shows this:

          8a3d97cc-ceaf-4780-ac74-5c7f545cee81-image.png

          What if you try it in a VM or other computer?

          The project works in my colleague’s machine, so something must be different here. However I have many other Vue / Quasar projects and this is the only one with this kind of problem. (It’s the only one that uses quasar-cli. My other ones use vue-cli and Quasar as a plugin).

          I can make the project available for testing if it helps.

          dobbel 1 Reply Last reply Reply Quote 0
          • dobbel
            dobbel @rubs last edited by

            @rubs

            One thing I notice: don’t use node 14.x with Quasar cli( that’s what I have been told). Use the latest 12.x.

            Sure you can post a repo and I will take a look at it.

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

              Ah yes @rubs as @dobbel said, don’t use Node 14, go back to Node 12+. Node 14+ breaks webpack. We’re still waiting on upstream packages to catch up.

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

                Okay, I’ll try going back to 12.x and I’ll let you guys know. Thanks for the time being.

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

                  This post is deleted!
                  1 Reply Last reply Reply Quote 0
                  • rubs
                    rubs last edited by

                    I thought the problem was gone, but no. Going back to 12.x allowed the app to be built, but unfortunately it seems the problem is still there.

                    1 Reply Last reply Reply Quote 0
                    • W
                      whoacowboy last edited by

                      @rubs @Hawkeye64 @dobbel Any luck with this. I am having the same issue.

                      dobbel 1 Reply Last reply Reply Quote 0
                      • dobbel
                        dobbel @whoacowboy last edited by

                        @whoacowboy

                        what’s the output of quasar info

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