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!

Thanx again - see revised post, hope ok. You should be seeing a cup of coffee.

(Pls check: Link on Patreon "go back to Scott Molinari’s Page is broken, gets 404)

Thanks for your prompt response, Scott. I added the this. parameter among the many things tried to resolve the problem; sorry not to remove it prior to the post.
However, removing the “this.” does not clear the “missing value” problem. How should the name parameter be set - is it required for the carousel? What I am thinking is take the Autoplay example [or one with captions] in QCarousel doco and implement it with the v-for construct; alternatively, could this thread be removed and replaced with the code that would apply to that demo? I think something needs to be done in the forum to get rid of old material and net-out the answers. Thanks for any assistance.

(Revised Post with Answer): Using QCarousel with the v-for iteration was giving me problems - which were solved thanks to Scott Molineri with following link:
https://codepen.io/smolinari/pen/VwZOBYx?editors=1010 << Thank you, Scott - worth a cup of coffee!
A look at this simple fix, no need to read the whole thread (I had thought v-model was not needed):

<!–
Forked from:
https://quasar.dev/vue-components/carousel#Example--Image-slides
–>
<div id=“q-app”>
<div class=“q-pa-md”>
<q-carousel
animated
v-model=“slide”
arrows
navigation
infinite
>
<q-carousel-slide v-for=“slide in slides”:key=“slide.id”:name=“slide.id” :img-src=“slide.url” ></q-carousel-slide>
</q-carousel>
</div>
</div>
Script:
const slides = [
{
id: 1,
url: ‘https://cdn.quasar.dev/img/mountains.jpg’
},
{
id: 2,
url: ‘https://cdn.quasar.dev/img/parallax1.jpg’
}
]
And add to data:
data () {
return {
slide: 1,
slides
}
}

QPdfViewer is a great module, thanks. When added to the application, however, a large number of files were added to the statics folder. Can these be safely removed - which items within statics are required, and which can be deleted? Thanks

In case others run into the problem mentioned above, I changed package.json “@quasar/app”: “^1.0.0-beta.0”, to 1.1.2 and it is working. Note, however, that a large number of files have been added to statics/pdfjs - and it is not clear what these are for, nor if all are required. Request discussion of the pdfjs folder contents and their use. Thanks. (one last request: Can the zoom level be set upon load of the document?)

This looks like a very nice package. However, I am getting the following error message that I cannot track down:
app:extension(index) ️ Extension(@quasar/qpdfviewer): is not compatible with @quasar/app v1.0.0-rc.7. Required version: ^1.0.0 +3ms