Uncaught ReferenceError: process is not defined

I have recently upgraded to the following versions

• “quasar”: “^2.0.0-beta.13”,
• “@quasar/extras”: “^1.10.4”,

Since I have done this I have literally stopped working all the global paths, the .env files, I have not been able to do anything. I’ve been reading the documentation but couldn’t find anything useful, has anyone else had this happen?

If i remove process.env declaration the project will work but that isn’t a option for me right now.

It also happens that the global paths of the images are not working for me (I noticed this when I deleted process env).

Actually import like this: <img :src='${require(src/assets/flags/${language}.png)}'>

MY VERSIONS

“node”: “>= 12.22.1”, “npm”: “>= 6.14.2”, “yarn”: “>= 1.21.1”

[rstoenescu]

Ok, writing here for other people who might be reading this thread. The problem was that the devland code was accessing process.env.SOMETHING but SOMETHING was NOT defined in quasar.conf.js > build > env. As a result, process.env.SOMETHING did not get replaced with the actual value so the runtime actually tries to access the process object (which does not exists — it got removed in Webpack 5 anyways).

[AlexDaniel]

@rstoenescu thank you very much for taking the time to leave the comment. I was struggling with the same problem for other reasons, but found this ticket by searching for the error message, and your comment helped me figure out what was wrong (it was just an accidental naming mistake). It saved a lot of time for me, thank you!