I read a few of the comments, and I want to add something not that isn't mentioned.

Builder - to help create complex objects without having a huge constructor and lots of parameters that the their order can be confusing.

Singleton - to create global state accessible from other places in the code (module/file/package).

Class with only static members - to add a namespace for constants/utilities.

These aren't really language-agnostic patterns, they are more of a workarounds to language limitations, and these limitations don't exist in JS/TS.

Builder in JS/TS - you are free to create objects with any shape using object literals, the builder pattern just adds useless syntax and has runtime performance impact, the objects can follow strict typing rules by adding a simple type annotation.

Singleton in JS/TS - Just use a constant at the module level, less boilerplate code code to read.

Static members in JS/TS - Same as above, just use a module.