Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not work with quasar/app-webpack v4 (beta) #401

Open
sonicviz opened this issue Nov 6, 2024 · 0 comments
Open

Does not work with quasar/app-webpack v4 (beta) #401

sonicviz opened this issue Nov 6, 2024 · 0 comments

Comments

@sonicviz
Copy link

sonicviz commented Nov 6, 2024

Describe the bug
A clear and concise description of what the bug is.

Create a new basic Quasar quickstart project as described here: https://quasar.dev/quasar-cli-webpack/upgrade-guide.
npm init quasar
When asked to "Pick Quasar App CLI variant", answer with: "Quasar App CLI with Webpack (BETA | next major version - v4)".

Adding quasar-ui-markdown via quasar ext add @quasar/qmarkdown@next

Results in the following error:
App • Installing "@quasar/qmarkdown" Quasar App Extension

App • Installing @quasar/quasar-app-extension-qmarkdown@next...
App • [sync] Running "npm install --save-dev @quasar/quasar-app-extension-qmarkdown@next" in E:\Source Control\AI Apps\My Quasar Apps\quasar-project

added 34 packages, and audited 952 packages in 9s

195 packages are looking for funding
run npm fund for details

found 0 vulnerabilities
node:path:433
validateString(arg, 'path');
^

TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received undefined
at join (node:path:433:7)
at #getScriptFile (E:\Source Control\AI Apps\My Quasar Apps\quasar-project\node_modules@quasar\app-webpack\lib\app-extension\AppExtensionInstance.js:346:22)
at #getScript (E:\Source Control\AI Apps\My Quasar Apps\quasar-project\node_modules@quasar\app-webpack\lib\app-extension\AppExtensionInstance.js:358:39)
at #getScriptPrompts (E:\Source Control\AI Apps\My Quasar Apps\quasar-project\node_modules@quasar\app-webpack\lib\app-extension\AppExtensionInstance.js:304:51)
at AppExtensionInstance.install (E:\Source Control\AI Apps\My Quasar Apps\quasar-project\node_modules@quasar\app-webpack\lib\app-extension\AppExtensionInstance.js:218:49)
at async runExtAction (E:\Source Control\AI Apps\My Quasar Apps\quasar-project\node_modules@quasar\app-webpack\lib\cmd\ext.js:69:3) {
code: 'ERR_INVALID_ARG_TYPE'
}

Node.js v20.12.2

This will then cause errors in md files when you try to run quasar dev
eg: Module parse failed: Unexpected character ' ' (1:1)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

News

|

To Reproduce
Steps to reproduce the behavior:
Create a new basic Quasar quickstart project as described here: https://quasar.dev/quasar-cli-webpack/upgrade-guide.
npm init quasar
When asked to "Pick Quasar App CLI variant", answer with: "Quasar App CLI with Webpack (BETA | next major version - v4)".
let it create the project
CD into the new project
Run quasar ext add @quasar/qmarkdown@next and receive your new error

Expected behavior

Expect it to not error, and work correctly as it does in "@quasar/app-webpack": "^3.14.2",

Screenshots

Desktop (please complete the following information):

  • OS: Win 11 X64 Pro 23H2 latest

Additional context
Add any other context about the problem here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant