I apologize if my question sounds stupid, but I found that I need in many situations global variables such as ones that represent database and redis clients to be used in many files, however these variables themselves need to wait to get their values from promises or async functions that initialize the communication to the database or redis servers.
I want to do something like that
init.js:
export default async () => {
return await initializeWhatever()
}
db.js:
import init from './init'
let db = null
init().then(val => db = val)
export default db
api.js:
import db from './db'
const doApi = req => {
db('users').select({username:req.param.username})
}
However the db
variable imported in api.js
is always null, why doesn't it get updated to the correct value when init()
finishes? If my approach to using db is wrong, what is the correct way to export global variables that are computed asynchronously?
Async functions always return a promise. If the return value of an async function is not explicitly a promise, it will be implicitly wrapped in a promise. Note: Even though the return value of an async function behaves as if it's wrapped in a Promise.resolve , they are not equivalent.
Can we export async function? This is not possible. Since the value is retrieved asynchronously, all modules that consume the value must wait for the asynchronous action to complete first – this will require exporting a Promise that resolves to the value you want.
Use named exports to export multiple variables in JavaScript, e.g. export const A = 'a' and export const B = 'b' . The exported variables can be imported by using a named import as import {A, B} from './another-file. js' . You can have as many named exports as necessary in a file.
When you export a variable, you're exporting what's stored in the variable, not the variable itself. Assigning to the variable will only change the variable, but will not affect what was exported.
Think of it like this:
let a = null;
let b = a;
a = 'something';
console.log(b);
// null
Note how storing something new in a
doesn't change what's stored in b
.
To do something like what you want in your question, you need to export an object and update references on that object:
init.js
export default async () => {
return await initializeWhatever()
}
db-module.js
import init from './init'
const dbModule = { db: null };
init().then(val => dbModule.db = val)
export default dbModule
api.js
import dbModule from './db-module'
const doApi = req => {
dbModule.db.select({username:req.param.username})
}
Obviously you might want to change some names to make things cleaner. I don't know a lot about your project so I'm not sure how to name them.
Also, you'll have to make sure have some way of making sure that any uses of your dbModule.db
object happen after it's actually in place. In other words, you have to make sure there's no way doApi
in api.js
can be invoked before init
in db-module.js
finishes.
To do this, you'll need to make the promise chain from init
available to api.js
:
init.js
export default async () => {
return await initializeWhatever()
}
db-module.js
import init from './init'
const dbModule = { db: null };
dbModule.promise = init().then(val => dbModule.db = val)
export default dbModule
api.js
import dbModule from './db-module'
const doApi = req => {
dbModule.db.select({username:req.param.username})
}
dbModule.promise.then(() => {
// Set up routes and start listening in this promise chain.
// Ensure there is no way `doApi` can be called before this happens.
});
Why does this work? Because in JS, variables don't store entire copies of objects. They simply store references. If two variables point at the same object, changes to the object will be reflected whether your access it through one variable or another. Think of it like this:
let c = { prop: null };
let d = c;
c.prop = 'something';
console.log(d.prop);
// 'something'
You can make a getter. Something about
export default function getDB() {
return db;
}
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With