@vue/reactivity for inversion of control in Node.js

[hypeJunction]

As of late, I have been thinking about IoC containers and how they pollute the global state, which becomes problematic in serverless/lambda environments, where you want to keep your functions to a minimal. With IoC containers the bundler has a difficulty determining whether something registered as a service would ever be invoked in the context of a specific lambda, so there isn't much treeshaking going on.

I was wondering what your thoughts are on using @vue/reactivity in the backend. If you think about it, ref could be used to wrap around static dependencies (e.g. env values), and computed could represent singletons:

const env = z.object({
  DB_URL: z.string().noempty()
}).parse(process.env)

const databaseUrl = ref(env.DB_URL)
const db = computed(() => {
  return new Database(databaseUrl.value)
})

This approach would allow you to import services as needed with a clear dependency tree. It is also quite easy to stub the services for testing.

I guess my questions are:

• are computed properties guaranteed to have the same identity? any chance it could be garbage collected and reevalutated thus creating a new singleton?
• anything else I am missing in terms of how this would play out in the backend?