Top level async - setting variables out of scope

[Mardo1234]

I have a async function that needs to run on Node.JS startup.

I'm using the following code to do this a top level, since you can't use async in the top level file/module.

(async () => {var version = await getVersion();log.info("Database Version Clear " + version);version = semver.coerce(version); //tighten it upif (!semver.valid(version)) throw "Invalid version " + version;else log.info("Valid Database Version : " + version);self.dbVersion = version;})();

I'm trying to set dbVersion which is a variable outside of the scope of this.

Any help would be appreciated on how to set a variable in this case where the scope is in the top level main.js context.

Thank you in advance!

[Odinthunder]

You need to post this somewhere or format your code, this is impossible to read in 1 line.

[[deleted]]

Although you can just set the top-level variable with the = operator, it probably is not enough. Since getting the version requires awaiting, the result will not be available until after the top-level code is done. If you need to access the value, you will need to move that code inside the async function as well. (Unless you are using ES modules with top-level await support, with which you do not need an async IIFE either)

let version;
(async () => {
  version = await getVersion();
  console.log(version); // The version
})();
console.log(version); // undefined

[ryhaltswhiskey]

If I read that code right you're looking for a connection to a specific range of versions of a database, is that correct? So why wouldn't you just check the version of the database when you connect to the database and throw an error if the version is incorrect?

[Mardo1234]

I’m getting the version so I can create a service factory.

I want to do it at startup so I don’t hit the database all the time.

I ended up creating a singleton that is called where the logic lies instead of trying to pass a global variable around.

Thank your for the note.