javascript – Is this extensive usage of closure a known (anti-)pattern? And does it have a name?

I often use function closures for storing data (e.g. database URL), which doesn’t change between function calls. Is this an (anti-)pattern? Does it have a name?

While developing apps, which recieve data, process and send data (using a variety of protocolls), I stumpled upon this recurring problem:

A functions needs 4 or more paramters to performe it’s task, while only one (or two) of these parameters change between calls.
E.g.:(1) A function sending data, which needs the ip-address and the port of the destination, something for authorization and the data to send.
E.g.:(2) A function processing raw data into the format of a database, which needs information about the raw data, the database and the raw data itself.

My original approach was to store this information where the function is called and just pass it everytime I call the function. But I find this quite hard to read, so I searched for a solution to store the constant parameters elsewhere. One thing I considered, was packing these into objects, but JS does not support private and constant attributes + this functions are often used as callback functions.

Of course I could use method_name.bind(the_object); , but using closures seemed to solve the problem as well, wouldn’t require usage of ““this“` and seemed more ‘functional’ than the other approach and therefore more fit for JS.

So my implementation of such a function usually looks like this:

function create_processData(schema, connectionInfosForAnotherDB, (...)){

    const someImportantInfo = getTheInfoFromAnotherDB(connectionInfosForAnotherDB);
    const interpretationOfThatInfo = interpretThatInfo(someImportantInfo);
    let processedMessageCounter = 0;

    function processData(data){
        //do the processing using the schema and the interpretationOfThatInfo
        //also use the processedMessageCounter
        return processedData;
    return processData;

module.exports = create_processData;

I have a function (create_processData) which setUps everything the actual function(processData) needs to work and save it’s in it’s closure, so that the actual function can access it. Then I return a reference to the actual function.

Code which uses this function would look like this:

const create_processData = require("./the_path/processData");
const processData = create_processData(...);

//use the processData function in a callback or something similar 

Unfortunatly, this doesn’t provide the clearity of code I wanted to achieve (while enabling a whole lot of encapsulation and keeping data only where it is needed – which I do like). In addition to that, a the code feels hard to understand, but this may just be a result of me beeing used to OOP and beeing unfamilier to functional programming (I don’t have a exhaustive experience or knowledge of both of them).

I tried to do some research about this, but I didn’t find anything usefull. Probably, this is due to a lack of vocabulary for this type of problem, pattern etc.

So: is this a known (anti-)pattern or problem? Does it have a name?
(Or is there just an obvious flaw in my thinking, which just isn’t obvious to me?)