Navigation

    Quasar Framework

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search

    Error when running npm run dev vs quasar dev (to use qenv)

    CLI
    3
    12
    23
    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.
    • dobbel
      dobbel @GlutenBoy last edited by dobbel

      @GlutenBoy said in Error when running npm run dev vs quasar dev (to use qenv):

      cross-env,

      When did you see these warnings appear for the first time? Probably because you installed 2 packages that have incompatible dependencies. Try to remove one of them and see if the warnings go away.

      btw:

      1. those are warnings not errors .
      2. https://github.com/kentcdodds/cross-env is now in maintenance mode mode, it will break eventually. I would not invest any time in it.
      1 Reply Last reply Reply Quote 0
      • G
        GlutenBoy last edited by

        @dobbel Sorry yes these are warning not errors.

        And yes I already did the test without these packages and still get these warnings when running npm run dev vs quasar dev. So I already ruled out these packages as the cause.

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

          @GlutenBoy

          then you should keep removing…until the warning dissapears

          1 Reply Last reply Reply Quote 0
          • G
            GlutenBoy last edited by

            ok but why don’t I see these warning when running quasar dev ?

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

              @GlutenBoy

              I could guess: cross-env is injecting dependencies that are not compatible with quasar. Only way to know for sure is to create a new default quasar app with quasar cli and only add cross-env.

              1 Reply Last reply Reply Quote 0
              • G
                GlutenBoy last edited by

                it’s not cross-env since I removed qenv and cross-env, put I will create a new app an insert all our extensions until I find the culprit. Although I’m not what will I do at this point… since we probably need that extension.

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

                  @GlutenBoy At this point, I’d scrub npm and use yarn. We keep telling people this. The reason is that npm has issues hoisting dependencies that bork the node_modules. And, yarn does a better job at it, but we have also seen issues (just not in the same quantity).

                  Try to use yarn and report back to me as I would really like to know if that resolves your issue.

                  1 Reply Last reply Reply Quote 0
                  • G
                    GlutenBoy last edited by

                    Hey @Hawkeye64 ,

                    Actually I just did that, it didn’t resolve the problem, but after googling this even more, I found that on windows you get that error in the Powershell terminal but not in the good old cmd.exe terminal… so cmd.exe it is for now.

                    Thx

                    1 Reply Last reply Reply Quote 0
                    • G
                      GlutenBoy last edited by

                      @Hawkeye64 after more investigating, and cleaning everything up with yarn and using yarn in cmd.exe I now still getting the warning…

                      The weird thing is that we never see these warning when running quasar dev.

                      The only reason to use yarn run (or npm run) was to use qenv. Maybe I’ll skip that and build our own solution, and keep using ‘quasar dev’

                      Maybe there’s a better way to debug these warning, but I didn’t found any solutions yet.

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

                        @GlutenBoy Hate to be poignant about it, but set up a VirtualBox with ubuntu. Put your sources over there and see if it works. I have a feeling it will. I used to be 100% windows guy (even worked for Microsoft twice, in the day), but because of issues for web dev, I have switch to 100% linux for the past few years.

                        1 Reply Last reply Reply Quote 0
                        • G
                          GlutenBoy last edited by

                          @Hawkeye64 Yeah you’re right, I actually do have linux running on my workstation (dual boot), but I’m going to run a build on one of our pipeline in DevOps on ubuntu with the npm and see if I get the warnings.

                          Mind you even though we get warnings, all seems to be working properly. It’s just bugging me and I don’t want this to come back to haunt us.

                          Thx for your help!

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