You guys could have saved me a lot of time earlier today! Really glad to have found this thread, and the most helpful example by s.molinari with CodePen implementation (which includes the settings for Quasar). Thanks a bunch - I feel like you’ve more than made up my wasted time today.

@s-molinari Scott - thanks for your reply. I’ll mull over and get back in the coming days. Best wishes with m8a.

I returned to this task and got it running: npm module MSSQL allows Node.js access to SQL Server and in my case Azure SQL. However, Quasar Electron did not run, although non-Quasar Electron did. MSSQL uses one of two drivers: tedious (default) or msnodesqlv8. Not getting tedious to work I tried msnodesqlv8, noting in the doco for mssql one must specify this with var sql = require(‘mssql/msnodesqlv8’). However, this generated a different error that something was built with wrong npm version (whatever) but in researching msnodesqlv8 doco it said for use with Electron one should run npm module electron-rebuild (see its doco for how to run, not straightforward). But ultimately it is working. So: 1) use mssql, 2) specify use of msnodesqlv8, 3) run electron-rebuild and hopefully your Quasar Electron App can talk to Azure SQL.

Sorry not to see this until now. Yes, I do have MSSQL working as of 4/18 with Azure SQL in a Quasar Electron application. It has been a while so it would take me some digging to see what I did to get things working. I do not recall doing anything other than downloading everything I used once again; I cannot recall if I had to do anything with tedious but I don’t think so. Used: npm modules mssql and ALSO msnodesqlV8. Sam
(PS for anyone interested: I’m working on a series of basic Quasar programs SPA and Electron that I’m calling Quick Quasar.)

This is VERY cool - not only informative but also a well laid out and attractive design! Congratulations from Michigan (a COVID hotspot). Definitely worth a cup.

I returned to this task and got it running: npm module MSSQL allows Node.js access to SQL Server and in my case Azure SQL. However, Quasar Electron did not run, although non-Quasar Electron did. MSSQL uses one of two drivers: tedious (default) or msnodesqlv8. Not getting tedious to work I tried msnodesqlv8, noting in the doco for mssql one must specify this with var sql = require(‘mssql/msnodesqlv8’). However, this generated a different error that something was built with wrong npm version (whatever) but in researching msnodesqlv8 doco it said for use with Electron one should run npm module electron-rebuild (see its doco for how to run, not straightforward). But ultimately it is working. So: 1) use mssql, 2) specify use of msnodesqlv8, 3) run electron-rebuild and hopefully your Quasar Electron App can talk to Azure SQL.

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
}
},

I would like to second this question, and see if the popular logger Winston would be recommended with Quasar (SPA mainly), or something else. In my case, I am beginning to use Google’s Firestore, and I would be interested in the pro’s and con’s of using that resource for log retention. If this logger were to be used, how would it be structured within the Quasare folder / module structure; would / could it be integrated with or employ Vuex? Any suggestions or examples would be appreciated. Thanks, SMS

The following link has a suggested solution. However, would anyone care to comment as to the efficacy of this suggestion, and if it makes sense, what would be needed in the Quasar configuration files to designate externals and/or his “electron-renderer” idea? Thanks to all.
http://www.matthiassommer.it/software-architecture/webpack-node-modules/
How can we expose the Node modules globally in our project? We have to define them as externals in our webpack.config.js:

module.exports = {
“externals”: {
“electron”: “require(‘electron’)”,
“child_process”: “require(‘child_process’)”,
“fs”: “require(‘fs’)”,
“path”: “require(‘path’)”
[remainder omitted]
}
},
Solution for Electron users
If you are using Electron and it still does not work, try the following things in addition.

Add target:’electron-renderer’ to module.exports in the Webpack configuration. Others also recommend to use this NPM package: webpack-target-electron-renderer

@metalsadman Thank you. However, nodeIntegration: true is already set in quasar.config.js. I am attempting to get either tedious or mssql to work, but from what I have read mssql / msnodeV8 are only compatible with electron < V6 (I re-loaded electron to version 5.0.13 with no success; same problem). I am dead in the water trying to integrate tedious, mssql or other method to get Quasar Electron to access Azure SQL. I think the issue is simply getting the modules loaded correctly. The error I have now is: [vue-router] Failed to resolve async component default: TypeError: webpack_require is not a function.

I am hoping someone has implemented SQL Access from Quasar with either Tedious or MSSQL, as I have been unsuccessful trying it - although it works with Electron sans Quasar. The error is TypeError: webpack_require(…) is not a function_
In the Electron non-Quasar solution, the use of require works ok. Is there any specific solution for this condition with tedious/mssql, or is there a general way to convert from require to import that will circumvent this error? (#9379 addresses this problem but I do not see a solution there)

d3.js is an incredibly powerful set of functions, not only graphics but other stuff as well. I used d3-sparql to do SPARQL queries against Wikidata and it works great. However, I am finding it difficult to locate examples of d3 graphics in Quasar. The description in https://github.com/CorpGlory/d3vue/blob/master/src/d3-components/circle-mount.vue for Vue.js is helpful and the simple circle works. In template have a div with <svg> element in the example, const d3 = require(‘d3’) appears to work rather than using import (although I used import { sparql} from ‘d3-sparql’ to get the sparql-only function. It would be helpful to have some Quasar-d3 example applications, although it appears that Vue.js use of d3 may carry over to Quasar with few, if any, special considerations. Are others enthusiastic about d3 for graphics and other functions, or is this not a good way to go? I am adventurous, but only if it is worthwhile!