Global Objects? Might Need Documentation

[lancedockins]

Question... the NJS documentation doesn't seem to suggest that there is any way to make an object or variable global in scope. By global, I mean that its contents would be accessible to any script processing a given request. In specific, I'm referring to the traditional NJS engine and not QuickJS.

The most practical use case for this would be the r object. Through the testing that I've done so far, it seems like each function that NJS calls passes the r object for the request but the only way to then call a subsidiary function that has access to the r object would be to pass that object as a variable. While that's feasible, it's a bit cumbersome - particularly given the globally unique scope of r during a single request.

Is there any way to globally access r? Or if you need access to r outside of the primary function that NJS calls, do you just have to pass it around as a variable in the function signature.

By the same token, I guess I'm also asking if there is a way to create other globally accessible variables between functions (not even necessarily between functions at different stages in the request).

And to further clarify, i'm not referring to the sort of thing that you can do with NJS object preloads. This would be for variables of various types. But again, r is the most obvious use case.

[xeioex]

Hi @lancedockins,

Is there any way to globally access r?

1. you can put to the global object in your function, like globalThis.r = r;. In NJS, each request has its VM and as a result globalThis too. This is not the case for QuickJS though.

function my_handler(r) {
    globalThis.r = r;
    ...
}

function my_logger(text) {
    globalTHis.r.log(text)
}

2. you can write closures. Probably, this is a better option, because it will work in QuickJS too.

function my_handler(r) {
    function my_logger(text) {
       r.log(text)
   }

 // use my_logger or pass it as a argument
}