Autodesk Forge web application – from visual studio code to close .exe file

I have a working forge application ( bim360 hub sidebar with forge viewer and some charts).

It is currently running from Visual Studio Code IDE only. I want to build the app into an .exe file in order to be able to send it to a user, upload it to a server with IIS, etc..

General details:

• I used Petr Broz tutorial to set up the backend of the viewer and hub
  (Forge online training – view your models https://www.youtube.com/watch?v=-O1e3gXCOEQ&t=8986s )

• The app is running on Node.js

I tried to use ‘nexe’ module and build executable file. With this method, I need to specify index.js file ("an entry point") and define a ‘nexe.config.js’ file. I used the entry point start.js.
Eventually, I managed to create an exe file – and when I run it from the command line, I get an error

Missing FORGE_CLIENT_ID or FORGE_CLIENT_SECRET env. variables.

although I have them in the config.js

Main questions:

• Is there another way to build a close exe file from visual studio code – for a forge web application?
• Am i doing something wrong with the processes I mention above?
• Is it even possible to deploy a web application to IIS using an exe file?? all of the documentation points toward Azur, AWS and heroku..

Relevant files:

1) start.js:

const path = require('path');//bringing in built in node js modeules ( to resulve file system path )
const express = require('express');//module to create the express server 
const cookieSession = require('cookie-session'); 
//any piece of code would have an opportunity to handle the request 
const PORT = process.env.PORT || 3000;
const config = require('./config.js');
if (config.credentials.client_id == null || config.credentials.client_secret == null) {
    console.error('Missing FORGE_CLIENT_ID or FORGE_CLIENT_SECRET env. variables.');
    return;
}

let app = express();
//static middlewere to check for the front end files (html,js,css)
app.use(express.static(path.join(__dirname, 'public')));//method inside express module: a middlewere for serving static files  this line will check in 'public' folder if the request 
//that is sent (specific file) is in there. if so - it will ignore the rest of the stack(the rest of the code)
app.use(cookieSession({
    // create 2 cookies that stores the name and encripted key 
    name: 'forge_session',
    keys: ['forge_secure_key'],//takes cater of decipher the encription for the forge key for us 
    maxAge: 14 * 24 * 60 * 60 * 1000 // 14 days, same as refresh token
}));
app.use(express.json({ limit: '50mb' }));//middlewere that looks at the title of the request - and if its .json it will look at the body of the request and parese it to javascript object
app.use('/api/forge', require('./routes/oauth.js'));//adding our custom express routers that will handle the different endpoints.
app.use('/api/forge', require('./routes/datamanagement.js'));
app.use('/api/forge', require('./routes/user.js'));
app.use((err, req, res, next) => {
    console.error(err);
    res.status(err.statusCode).json(err);
});
app.listen(PORT, () => { console.log(`Server listening on port ${PORT}`); });

2) config.js:

// Autodesk Forge configuration
module.exports = {
    // Set environment variables or hard-code here
    credentials: {
        client_id: process.env.FORGE_CLIENT_ID,
        client_secret: process.env.FORGE_CLIENT_SECRET,
        callback_url: process.env.FORGE_CALLBACK_URL
    },
    scopes: {
        // Required scopes for the server-side application-->privliges for our internal opperation in the server side ("back end")
        internal: ['bucket:create', 'bucket:read', 'data:read', 'data:create', 'data:write'],
        // Required scope for the client-side viewer-->priveliges for the client ("front end") 
        public: ['viewables:read']
    }
};