It is in the docs, my mistake was copying the “working” method for q-list into the q-menu… didn’t notice the different. Thanks a lot!

It looks a bit cumbersome (to my non-professional eyes) to achieve what I need.
I appreciate a lot your effort and wanting to help but I will first finish some unfinished business I have in the queue and then I’ll get to this.
Again, thanks a lot!

Thanks, a newbie question in order for me not to damage anything, in solution 2 point b I saw

from an unprivileged shell

mkdir electron-keytar
cd electron-keytar
npm init
npm install electron
npm install keytar
npm install electron-rebuild --save-dev
.\node_modules.bin\electron-rebuild -w keytar -p -f

Because I already have a project folder with the relevant installations (electron, keytar and electron rebuild), is it enough for me just to run
.\node_modules.bin\electron-rebuild -w keytar -p -f
?

There you go: https://gofile.io/d/TziSA1
Thanks a lot!

Well, when running as web, it fails with: Keytar,getPassword is not a function.
When running as electron (executable), it fails with:
Error: node-loader: Error: C:\Users\user\AppData\Local\Temp\07e92995-d4c3-47dc-8b61-d882691c2e86.tmp.node is not a valid Win32 application. C:\Users\user\AppData\Local\Temp\07e92995-d4c3-47dc-8b61-d882691c2e86.tmp.node

I’m kinda lost The application itself is running ok, only that line specifically fails.
I don’t understand why it fails with “is not a valid Win32 application” - in github, the person told me that I must be doing something wrong and closed the ticket.
I guess I’m the only one ever to try to use Keytar or to add a “remember me” feature to his login window.
If not, I wonder how other people managed to do it.

The demo is from the very first/initial try to use Keytar before I tested deeper, not that it made me any progress

Any idea how come keyt is recognized correctly with the relevant functions (getPassword in this case) but still will fail when calling that function?
I mean generally, what can cause such error, any tip or hint might help me to go forward.
Thanks

I changed node-loader’s index.js code from global.process.dlopen to process.dlopen and it passed this line of code but now fails of something else.

Even though it recognized the function, it fails as if it’s not a function.
I posted a question on node-loader’s github.
Also made a MVP demo but before the latest changes if you want to play with it: https://gofile.io/d/HDsLoV
type quasar dev to run it

Thank you very much for the tip. I tried to do the following:

try {
    let keyt = require("keytar");
} catch (e) {
    this.errorMessage = e;
    this.showError = true;
}

When running as “web”, I got the same error as before with global.process undefined.
When running as “electron”, I got the following:

Error: node-loader: Error: C:\Users\user\AppData\Local\Temp\e6425528-a110-43aa-a474-41723fc46383.tmp.node is not a valid Win32 application. C:\Users\user\AppData\Local\Temp\e6425528-a110-43aa-a474-41723fc46383.tmp.node

Building as electron generates a portable executable that I run. My guess is that when running, it extracts the inside to the temp folder.

I know global.process is coming from node-loader but there’s one thing I still don’t understand:
I’m developing in quasar/vue and when building, I “tell” it to build it in electron mode.
How can I import something only in electron mode?

At the moment I have this, after adding the relevant code to extendWebpack (see previous message in this thread)
import { keytar } from “keytar”;
and it compiles and executed but fails to run because global.process is undefined.
My guess is because I’m not in electron mode, but this is just a guess and I want to test it.

I tried the following but obviously it does not compile
import { Platform } from “quasar”;
if ($q.platform.is.electron) import { keytar } from “keytar”;
‘import’ and ‘export’ may only appear at the top level

Any kind of help will be appreciated.
Thanks

The error is because global.process is undefined. What is global.process and who owns it?
Is it related to quasar? electron? keytar?
Thanks

I made some progress but now encountered a new issue. From the docs I realized that I should put the above code, under build -> extendWebpack.

extendWebpack(cfg) {
                cfg.module.rules.push({
                    enforce: "pre",
                    test: /.node$/,
                    loader: "node-loader",
                    //exclude: /(node_modules|quasar)/,
                });
            },

So now it is compiled and the web opens up but empty. Looking in the console I see the following

Cannot open C:\Users\user\Downloads\portable\vscode\Projects\project\node_modules\keytar\build\Release\keytar.node: TypeError: Cannot read property 'dlopen' of undefined
    at Object.eval (keytar.node?3002:1)

and the line itself is

try {global.process.dlopen(module, "C:\\Users\\user\\Downloads\\portable\\vscode\\Projects\\project\\node_modules\\keytar\\build\\Release\\keytar.node"); } catch(e) {throw new Error('Cannot open ' + "C:\\Users\\user\\Downloads\\portable\\vscode\\Projects\\project\\node_modules\\keytar\\build\\Release\\keytar.node" + ': ' + e);}

The above was taken from Chrome. Firefox says the same but from a different angle:

global.process is undefined

I wonder if it’s because keytar should only be loaded in electron mode?
If so, how can I set it? If not, what am I doing wrong?
Thanks