Hurra! Thanks a lot.

And this for a reusable wrapper creator with support for props: https://gist.github.com/larvanitis/b4937a182e41b8563e95e531f199b7e2

Also untested…

Ok. That’s good. Good to know I was actually right to begin with. 😁

Scott

Putting here what I added on Discord

As you can see here, it was added to acorn 20 days ago in version 7.2.0
But, look here:

├─┬ @quasar/app@1.9.1 │ ├─┬ webpack@4.43.0 │ │ └── acorn@6.4.1 │ └─┬ webpack-bundle-analyzer@3.8.0 │ └── acorn@7.2.0 └─┬ eslint-plugin-vue@6.2.2 └─┬ vue-eslint-parser@7.1.0 └─┬ espree@6.2.1 └── acorn@7.2.0 deduped

Waiting on webpack to update to v7.2.0

@Christal https://github.com/quasarframework/app-extension-qenv/tree/dev/app-extension

What is the purpose for needing this? When you say “print”, do you mean output in a component or actually printing? And $t isn’t a variable, it is a method. And you can wrap methods in other methods, but the “why” for you needing to do that is unclear.

Scott

Please don’t use old threads for new problems. Start a new thread. Also, you need to explain more to get help. What did you do to the point of not getting further. Are you seeing any errors? If no errors, what do you see?

Scott

Read this carfully please. 🙂

https://quasar.dev/quasar-cli/cli-documentation/boot-files#Anatomy-of-a-boot-file

Scott

Hello,

I had the same message while migrating to capacitor from cordova.
I removed all my cordova plugins, but I still got that error.
The way I fixed the error (I have not idea why it is related to capacitor-cordova-android-plugins message), was that I was using my own certificate.
I changed from
devServer: {
https: {
key: fs.readFileSync(’/path/to/server.key’),
cert: fs.readFileSync(’/path/to/server.crt’),
ca: fs.readFileSync(’/path/to/ca.pem’),
}
to
devServer: {
https: false,

Will do.

Answering my own question. I found quasar-ide-helper, which solves this problem. However it seemed to do a bunch of other stuff to my project that I didn’t want or need. In one of the issues for that project I found this solution.

Make this change to your quasar.conf.js.

At the top add

let fs = require('fs')

Then in the extendWebpack function, add:

if (!fs.existsSync('webpack.config.js')) { fs.writeFileSync('webpack.config.js', ` /* eslint-disable */ /** * DON'T EDIT THIS FILE!! * * This file is generated to help IntelliJ resolve Webpack aliases. It is never run in the app. * If you need to extend your webpack config, put your code in quasar.conf.js into extendWebpack function */ module.exports = ${JSON.stringify(cfg, null, 2)} `) }

You’ll need to run quasar dev or quasar build to trigger this code to be run. Now you can configure the IDE to use “<project_dir>/webpack.config.js” as the webpack config, and it’ll know about your aliases. If you want to update the file because your webpack config has changed, just delete it and re-run quasar dev.

Thanks @s-molinari , @metalsadman for your insights…

Thanks Scott. I prefer typescript.

I was having trouble but used EXACTLY the code above in launch.json (except used 8080 not 8000) and it worked! I was having weird problem where breakpoint set on one line ended up assigned to a different line in the module. Now all appears to be working. Thanks!
FYI what I have in quasar.conf.js is as follows - the commented brkpt: cfg.devtool below was tried and did not seem to affect the problem; it does not seem to be needed but if anyone knows otherwise, please advise.
build: {
scopeHoisting: true,
devtool: ‘source-map’,
extendWebpack (cfg) {
// this had no effect on vs code: brkpt: cfg.devtool = ‘source-map’ // added 4/12/20, set brkpt and it gets placed elsewhere
}
},

@jrhopkins83 maybe file a bug report as well, although the specific way as you did, is the normal way to add platform per capacitor guide.

Ok, thank you

So, quasar.extensions.json should be:

checked in VCS let unformatted