Where are closures genuinely useful in JavaScript?
Closures are useful whenever you want a function to remember something while keeping that something invisible to the rest of the program. Six patterns come up again and again in real code.
Private state. A factory function keeps a variable in its own scope and hands back only the functions that you are willing to expose. Nothing outside can read the state or change it, and there is no way to skip the checks that you put in front of it.
Memoisation. A function that caches its results inside a closure does the expensive work only once. The cache is private, so nothing outside can spoil it, and it disappears as soon as nothing holds the function any more.
Event handlers and callbacks. A handler needs to know which row, which item, or which request it belongs to, and a closure is how you give it that context without inventing a global variable.
Module factories. A function that takes a configuration and returns a configured object is a closure, and that is how you build modules that are easy to test and easy to reuse.
Middleware and decorators. A wrapper function takes a function and returns a function that adds behaviour around it, and the added behaviour usually needs some state of its own.
Currying and partial application. A function that takes some of the arguments and then returns a function that waits for the rest is a closure over the arguments that it already has.
The honest caveat is that closures are everywhere in JavaScript whether you notice them or not, so it is better to think of them as a tool rather than as a feature to use on purpose. The question that matters is always whether the state that you are keeping alive is worth keeping alive.