A
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.
