No More Posting New Topics!

I have seen this error, and the weirdest thing was that I had suddenly in my code an import node: which I am 100% certain I did not put in, almost like a plugin in Visual Studio Code was adding this without my knowledge. I removed this line and the latest plugins and now all is OK again. But watch out for ‘stinky’ plugins !!

@ebdonato

I would just create a new project with Quasar CLI and copy the eslint deps from package.json and some other files in your other project.

@dylanglockler said in Hot reload or watch does not work:

While reading the Quasar doc I came across this:

https://quasar.dev/quasar-cli/quasar-conf-js#Docker-and-WSL-Issues-with-HRM

@miquelcapo

Ah so you create plugins designed to be used in the backend of WP?

Do you have a link to any of your created quasar/WP plugins?

On development I use the localhost devserver and on production I build the app and load js, css and assets with wp

So if I understand correctly: you use Quasar CLI for development. For a production build you run quasar build and then load the created js/css/assets from the quasar’s build folder with WP admin_enqueue_scripts hook. Or do you use Quasar’s UMD mode generated files in to load in WP( if not, why not use UMD?).

On your question, here’s a github issue you might find interesting:
https://github.com/quasarframework/quasar/issues/5063

@crmi

Once I switch to Quasar CLI, is there a known way to use the quasar.conf file to build for multiple targets in this way?

Not possible in Quasar as far as I know it.

here’s a thread about it:
https://forum.quasar-framework.org/topic/4139/multiple-entry-points

Btw for this particular question I would ask around in Quasar’s discord channel.

@metalsadman yayyy!!! It worked.

bfd4e5e9-5faa-400a-8298-d0c3f3e0fdd4-image.png

I targeted the inner Input tag element and passed it in the request to Google. Voila its working!!! Now I can make it work alongside with q-select tag too. Thankyou very much. Damn QUASAR is simply WOW!!!

Nevermind, just seen In the docs It’s not supported yet https://quasar.dev/quasar-cli/developing-capacitor-apps/capacitor-version-support

You have two options, reinstall the project or add into package.json => dependencies “http-proxy-middleware@0.19.x” version. In default version used by “@quasar/cli” is “http-proxy-middleware@1.x.x”, I added v 0.19 and it works for me without errors in the console.

@dobbel Ahh, thank you! That worked. The key was I needed to remove publicPath entirely from quasar.conf.js, not just set it to a relative path.

So, to recap for anyone else looking for an answer to this problem. If you want to build a quasar app such that the build can be mounted under arbitrary base paths, you need to:

Set vueRouterMode to ‘hash’ Set publicPath to null, or don’t set it all.

I may play around in my spare time with seeing if I can patch things up to get history mode to work with a relative public public path and post back here if I get something working.

@pachino-max said in SOS! Help! Quasar + Cordova how build to Android 4 and 5!:

I mean how to set styles for 4.4 separately?

You mean a different style if your app runs on android 4.4 instead of android 8/9/10?

Never seen anyone do that. But I guess you could do that with this:
https://quasar.dev/options/platform-detection#Introduction

@pachino-max

use node v12.x for Quasar V1 apps.

App · Bundling app with electron-packager…

Packaging app for platform win32 x64 using electron v9.4.4

App · [SUCCESS] electron-packager built the app

Build succeeded

Build mode… electron
Pkg quasar… v1.15.4
Pkg @quasar/app… v2.1.15
Debugging… no
Publishing… no
Transpiled JS… yes (Babel)

Output folder… F:\XDD\lifeon-electron\dist\electron

PS F:\XDD\lifeon-electron>

Hello I’ve a problem with productName:
Html Webpack Plugin:

<pre> Error: ReferenceError: productName is not defined - index.twig.template.html:97 /src/index.twig.template.html:97:11 - index.twig.template.html:106 98bd.module.exports /src/index.twig.template.html:106:3 - index.js:400 [client2]/[html-webpack-plugin]/index.js:400:16 - task_queues.js:82 processTicksAndRejections internal/process/task_queues.js:82:5 - async Promise.all </pre>

Hi I have same problem , remove .babelrc dont work , also the other things that you here recommended. Please help.

@mila76

Maybe you should ask the webpack community for support on this.

@aitcheyejay , can you share the hack?