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

    Upgrade to @quasar/app V2 BUT error->.quasar\client-entry.js: Cannot find module 'js-levenshtein'

    Help
    1
    2
    615
    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.
    • S
      shiyewuxian last edited by

      I followed the guide to upgrade to @quasar/app V2. But when I tried to start quasar dev, I have been reported an error, copy as below:

       ERROR  Failed to compile with 1 errors                                                                                                                                                                                             3:45:18 ├F10: PM┤
       error  in ./.quasar/client-entry.js
      
      Module build failed (from ./node_modules/babel-loader/lib/index.js):
        Error: [BABEL] C:\dev\wtapm\dason_2\.quasar\client-entry.js: Cannot find module 'js-levenshtein'
        Require stack:
        - C:\dev\wtapm\dason_2\node_modules\@quasar\babel-preset-app\node_modules\@babel\preset-env\lib\utils.js
        - C:\dev\wtapm\dason_2\node_modules\@quasar\babel-preset-app\node_modules\@babel\preset-env\lib\debug.js
        - C:\dev\wtapm\dason_2\node_modules\@quasar\babel-preset-app\node_modules\@babel\preset-env\lib\index.js
        - C:\dev\wtapm\dason_2\node_modules\@quasar\babel-preset-app\index.js
        - C:\dev\wtapm\dason_2\node_modules\@babel\core\lib\config\files\plugins.js
        - C:\dev\wtapm\dason_2\node_modules\@babel\core\lib\config\files\index.js
        - C:\dev\wtapm\dason_2\node_modules\@babel\core\lib\index.js
        - C:\dev\wtapm\dason_2\node_modules\babel-loader\lib\index.js
        - C:\dev\wtapm\dason_2\node_modules\loader-runner\lib\loadLoader.js
        - C:\dev\wtapm\dason_2\node_modules\loader-runner\lib\LoaderRunner.js
        - C:\dev\wtapm\dason_2\node_modules\webpack\lib\NormalModule.js
        - C:\dev\wtapm\dason_2\node_modules\webpack\lib\NormalModuleFactory.js
        - C:\dev\wtapm\dason_2\node_modules\webpack\lib\Compiler.js
        - C:\dev\wtapm\dason_2\node_modules\webpack\lib\webpack.js
        - C:\dev\wtapm\dason_2\node_modules\@quasar\app\lib\dev-server.js
        - C:\dev\wtapm\dason_2\node_modules\@quasar\app\bin\quasar-dev
        - C:\dev\wtapm\dason_2\node_modules\@quasar\app\bin\quasar
        - C:\Users\shiye\AppData\Local\Yarn\Data\global\node_modules\@quasar\cli\bin\quasar (While processing: "C:\\dev\\wtapm\\dason_2\\node_modules\\@quasar\\babel-preset-app\\index.js")
      
        - loader.js:965 Function.Module._resolveFilename
          internal/modules/cjs/loader.js:965:15
      
        - loader.js:841 Function.Module._load
          internal/modules/cjs/loader.js:841:27
      
        - loader.js:1025 Module.require
          internal/modules/cjs/loader.js:1025:19
      
        - helpers.js:72 require
          internal/modules/cjs/helpers.js:72:18
      
        - utils.js:29 Object.<anonymous>
          [dason_2]/[babel-preset-app]/[@babel]/preset-env/lib/utils.js:29:45
      
        - loader.js:1137 Module._compile
          internal/modules/cjs/loader.js:1137:30
      
        - loader.js:1157 Object.Module._extensions..js
          internal/modules/cjs/loader.js:1157:10
      
        - loader.js:985 Module.load
          internal/modules/cjs/loader.js:985:32
      
        - loader.js:878 Function.Module._load
          internal/modules/cjs/loader.js:878:14
      
        - loader.js:1025 Module.require
          internal/modules/cjs/loader.js:1025:19
      
      
      
       @ multi (webpack)-dev-server/client?http://0.0.0.0:8078 (webpack)/hot/dev-server.js ./.quasar/client-entry.js
      

      Anyone who has the idea how to solve it? Many thanks.

      1 Reply Last reply Reply Quote 0
      • S
        shiyewuxian last edited by

        Problem solved. Even though I use yarn but by using npm install can I just finally solve the problem.

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