KristijanS99
commented
3 weeks ago Same here! I started a fresh project in order to port our extension to Manifest V3 and I cannot run the dev/build process for it... tried with the v1 stable and v2 beta. Both of them have the same issue. In my case it doesn't matter if I remove node_modules or not, it does not work anyhow (probably because I am running from scratch so it always pulls the latest changes).
`kristijanstefanoski@Kristijans-MBP bex-project % npx quasar dev -m bex
.d88888b.
d88P" "Y88b
888 888
888 888 888 888 8888b. .d8888b 8888b. 888d888
888 888 888 888 "88b 88K "88b 888P"
888 Y8b 888 888 888 .d888888 "Y8888b. .d888888 888
Y88b.Y8b88P Y88b 888 888 888 X88 888 888 888
"Y888888" "Y88888 "Y888888 88888P' "Y888888 888
Y8b
App • WAIT • Compiling of Background Script with Esbuild in progress...
✘ [ERROR] Could not resolve "quasar/src/utils/uid"
.quasar/bex/bridge.js:8:16:
8 │ import uid from 'quasar/src/utils/uid'
╵ ~~~~~~~~~~~~~~~~~~~~~~
You can mark the path "quasar/src/utils/uid" as external to exclude it from the bundle, which will
remove this error.
/Users/kristijanstefanoski/Desktop/workspace/bex-project/node_modules/esbuild/lib/main.js:1621
let error = new Error(`${text}${summary}`);
^
Error: Build failed with 1 error:
.quasar/bex/bridge.js:8:16: ERROR: Could not resolve "quasar/src/utils/uid"
at failureErrorWithLog (/Users/kristijanstefanoski/Desktop/workspace/bex-projec/node_modules/esbuild/lib/main.js:1621:15)
at /Users/kristijanstefanoski/Desktop/workspace/bex-projec/node_modules/esbuild/lib/main.js:1263:28
at runOnEndCallbacks (/Users/kristijanstefanoski/Desktop/workspace/bex-projec2/node_modules/esbuild/lib/main.js:1176:65)
at buildResponseToResult (/Users/kristijanstefanoski/Desktop/workspace/bex-projec/node_modules/esbuild/lib/main.js:1261:7)
at /Users/kristijanstefanoski/Desktop/workspace/bex-projec/node_modules/esbuild/lib/main.js:1374:14
at /Users/kristijanstefanoski/Desktop/workspace/bex-projec/node_modules/esbuild/lib/main.js:675:9
at handleIncomingPacket (/Users/kristijanstefanoski/Desktop/workspace/bex-projec/node_modules/esbuild/lib/main.js:772:9)
at Socket.readFromStdout (/Users/kristijanstefanoski/Desktop/workspace/bex-projec/node_modules/esbuild/lib/main.js:641:7)
at Socket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:559:12) {
errors: [
{
detail: undefined,
id: '',
location: {
column: 16,
file: '.quasar/bex/bridge.js',
length: 22,
line: 8,
lineText: "import uid from 'quasar/src/utils/uid'",
namespace: '',
suggestion: ''
},
notes: [
{
location: null,
text: 'You can mark the path "quasar/src/utils/uid" as external to exclude it from the bundle, which will remove this error.'
}
],
pluginName: '',
text: 'Could not resolve "quasar/src/utils/uid"'
}
],
warnings: []
}
Node.js v20.11.1`
IGZmanuelMartinVivaldi
evandor
rstoenescu
roberttolton
What happened?
create a new quasar project with default settings (yarn create quasar, all recommended choices, typescript, no plugins) add bex mode optionally "rm -rf node_modules dist yarn.lock" yarn install running "quasar dev -m bex" results in error (see below)
What did you expect to happen?
successful build, running application, like it was working "yesterday" (don't know exactly when this error was introduced)
Reproduction URL
https://github.com/evandor/quasar-project
How to reproduce?
create a new quasar project with default settings (yarn create quasar, all recommended choices, typescript, no plugins) add bex mode optionally "rm -rf node_modules dist yarn.lock" yarn install running "quasar dev -m bex"
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
BEX Mode
Platforms/Browsers
Firefox, Chrome, Safari, Microsoft Edge, iOS, Android, Electron, Other
Quasar info output
Relevant log output
Additional context
all over a sudden, all my projects stopped building. This only occurs if you remove the node_modules folder and rerun "yarn install". Running the dev command after that results in the described error.
Btw: Thanks so much for this project!!