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

    Unable to find client-entry dep after upgrade

    Framework
    2
    5
    870
    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.
    • C
      coopersamuel last edited by

      I just upgraded from v1.0.0-beta.26 to latest with quasar upgrade -i. Everything seemed to work fine. But now it’s unable to find the .quasar/client-entry.js dependency. Any help appreciated

      client_1  |  Dev mode.......... spa
      client_1  |  Pkg quasar........ v1.0.5
      client_1  |  Pkg @quasar/app... v1.0.4
      client_1  |  Debugging......... enabled
      client_1  | 
      client_1  |  app:extension Running "@quasar/testing-unit-jest" Quasar App Extension... +0ms
      client_1  |  app:extension Running "@quasar/testing-e2e-cypress" Quasar App Extension... +7ms
      client_1  |  app:extension Running "@quasar/testing" Quasar App Extension... +2ms
      client_1  |  app:extension Running "@quasar/qmediaplayer" Quasar App Extension... +3ms
      client_1  |  app:quasar-conf Reading quasar.conf.js +13ms
      client_1  |  app:dev Checking listening address availability (0.0.0.0:8080)... +5ms
      client_1  |  app:quasar-conf Extension(@quasar/qmediaplayer): Extending quasar.conf... +7ms
      client_1  |  App Extension (qmediaplayer) Info: 'Adding qmediaplayer boot reference to your quasar.conf.js'
      client_1  |  App Extension (qmediaplayer) Info: 'Adding media-player.styl css reference to your quasar.conf.js'
      client_1  |  app:webpack Extending SPA Webpack config +442ms
      client_1  |  app:generator Generating Webpack entry point +7ms
      client_1  |  app:dev-server Booting up... +15ms
      client_1  | 
      client_1  |  app:progress Compiling SPA... +177ms
      client_1  |  app:progress Compiled SPA in ~693ms +694ms
      client_1  |  ERROR  Failed to compile with 1 errors7:36:49 PM
      client_1  | 
      client_1  | This dependency was not found:
      client_1  | 
      client_1  | * /usr/src/client/.quasar/client-entry.js in multi (webpack)-dev-server/client?http://0.0.0.0:8080 (webpack)/hot/dev-server.js ./.quasar/client-entry.js
      client_1  | 
      client_1  | To install it, you can run: npm install --save /usr/src/client/.quasar/client-entry.js
      
      1 Reply Last reply Reply Quote 0
      • D
        devlamine last edited by devlamine

        Have you found the solution? I have the same problem

         Dev mode.......... spa
         Pkg quasar........ v1.1.0
         Pkg @quasar/app... v1.0.6
         Debugging......... enabled
        
         app:quasar-conf Reading quasar.conf.js +0ms
         app:dev Checking listening address availability (0.0.0.0:8080)... +5ms
         app:webpack Extending SPA Webpack config +522ms
         app:generator Generating Webpack entry point +320ms
         app:dev-server Booting up... +4ms
        
        
         SPA █████████████████████████ [100%] in ~514ms
        
        
         ERROR  Failed to compile with 1 errors                                                                                                                                                 
        
        This dependency was not found:
        
        * client/.quasar/client-entry.js in multi (webpack)-dev-server/client?http://0.0.0.0:8080 (webpack)/hot/dev-server.js ./.quasar/client-entry.js
        
        To install it, you can run: npm install --save /client/.quasar/client-entry.js
        1 Reply Last reply Reply Quote 0
        • D
          devlamine last edited by

          I tried removing the .quasar, node_modules, .quasar and yarn.lock directories, and got the same error.

          1 Reply Last reply Reply Quote 0
          • D
            devlamine last edited by

            any solution for this ??

            1 Reply Last reply Reply Quote 0
            • D
              devlamine last edited by

              It is resolved : core-js@3.x has problems,return to core-js@2.x

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