quasar: `client-entry.js` not found after upgrade to latest version

I just upgraded from v1.0.0-beta.26 to latest using quasar upgrade -i, everything seemed to work fine. Now building my app fails with

This dependency was not found:
 * /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`

Full copy/paste of the error:

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:quasar-conf Reading quasar.conf.js +8ms
client_1  |  app:dev Checking listening address availability (0.0.0.0:8080)... +5ms
client_1  |  app:webpack Extending SPA Webpack config +448ms
client_1  |  app:generator Generating Webpack entry point +6ms
client_1  |  app:dev-server Booting up... +10ms
client_1  | 
client_1  |  app:progress Compiling SPA... +177ms
client_1  |  app:progress Compiled SPA in ~691ms +691ms
client_1  |  ERROR  Failed to compile with 1 errors2:28:05 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

This error happens without any changes to the code itself, the only change was the quasar upgrade. I’ve confirmed that /usr/src/client/.quasar/client-entry.js is the correct path and it is there. I’ve already tried removing node_modules and yarn.lock and reinstalling.

Any help is greatly appreciated

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 2
Comments: 21 (7 by maintainers)

Most upvoted comments

in quasar.conf.js I’ve changed boot files names from ‘axios’ to ‘axios.ts’ and it started to work…

drsaint23 on Apr 14, 2020

TL;DR: I ran into this. Found that it was my own mistake. However, the error could definitely be more accurate to save time.

For fellow developers who might land here from a google search on the error:

I just spent 2 hours debugging this, reading quasar-cli code, comparing the content of the files under .quasar with a different project that I had and is working, and cleaning all the above folders many times. It turned out that I had accidentally uninstalled eslint-loader which is needed in my quasar.conf.js!

So my two cents are:

The error can mean: “there was an error in creating a proper .quasar/client-entry.js (while it is [re-]created, even if you rm and then ls!); so go check anything in quasar.conf that might have changed/touched.”
It’s probably not your day-to-day Vue/js/ts code that has caused this. So, for debugging, try to checkout your last working commit, on a clean clone (before npm i), and try npm i && npm run dev. It might take some attempts to binary-search, if it’s not very last commit. Once you found out the commit that’s causing the problem, go examine that closely to figure out what you have touched at very high level (e.g. package.json or quasar.conf.js) that might be problematic.

eyedean on Nov 2, 2019

Have you also tried deleting the .quasar folder?

panstromek on Aug 7, 2019

try deleting node_modules, .quasar and package-lock.json as well if you have it, then try npm i and build again

wilbertverayin on Sep 26, 2019

I just spent 2 hours debugging this, reading quasar-cli code, comparing the content of the files under .quasar with a different project that I had and is working, and cleaning all the above folders many times. It turned out that I had accidentally uninstalled eslint-loader which is needed in my quasar.conf.js!

Your comment spared me one hour (already spent an hour searching for the solution, though): eslint-loader was the key for my weird error messages like Module not found .quasar/client-entry.js as well, thanks!

arutz12 on Dec 20, 2020

Can reproduce this error.

yarn install - with this error (not every install) npm install - without this error (every install without error)

yarn version - 1.22.4 npm version - 6.14.4

vitaliytv on Jul 1, 2020

We actually understood what was wrong (at least for our team, and in our case).

Apparently, TS support changed with @quasar/app v1.6+ - here is the doc

So, what worked for us was :

In our quasar.conf.js file, add supportTS: true
In our tsconfig.json file, add "extends": "@quasar/app/tsconfig-preset"

If you upgrade quasar (using quasar upgrade -i), nothing complains about it, even though it could break your build, for no “apparent” reason.

@rstoenescu display something to the user while upgrading might be a good idea, wouldn’t it be ?

NB : In our tsconfig.json file, we also added "types": ["quasar", "jest"] in our "compilerOptions" object, specifically because we use jest as test engine.

GhyslainBruno on Jun 10, 2020

This needs to be in a FAQ

hawkeye64 on Aug 8, 2019

Yeah, that changed during the beta. You do not need to import those anymore. Sry for the confusion.

https://quasar.dev/style/stylus-variables#Caveat

nothingismagick on Aug 8, 2019