No they are not needed. See these and many similar statements/posts. https://michelenasti.com/2019/01/23/is-typescript-namespace-feature-deprecated.html https

No they are not needed. See these and many similar statements/posts. https://michelenasti.com/2019/01/23/is-typescript-namespace-feature-deprecated.html https://michelenasti.com/2019/01/23/is-typescript-namespace-... https://stackoverflow.com/questions/64495793/typescript-namespaces-to-be-discontinued https://stackoverflow.com/questions/64495793/typescript-name... https://github.com/microsoft/TypeScript/issues/30994#issuecomment-492017219 https://github.com/microsoft/TypeScript/issues/30994#issueco... (link to a specific comment) > Namespaces are probably never going away and, simultaneously, you probably shouldn't use them, since better, more standard and modern patterns exist through the use of modules. If you have code that you feel needs to use a namespace, more power to you and go for it, but most of the time you don't need one, as we now have a different conceptual organizational model recommended for large-scale JS (modules). That's why @DanielRosenwasser (Program Manager of TypeScript) said namespaces are not a huge loss - most new TS code should probably never need to use them, and should think hard about if they really need to. Sure, you can use them, enums as well still provide a few more options than object literals, and since those features are in TS anyway and will remain like everything in JS always remains for backwards compatibility... - but they are not needed. There even is a sentence in the TS documentation (under Namespaces and Modules) that starts with "If you’re converting a program from namespaces to modules,..." (see https://www.typescriptlang.org/docs/handbook/namespaces-and-modules.html#needless-namespacing https://www.typescriptlang.org/docs/handbook/namespaces-and-...) This is distorting my post's point, which was Typescript is ECMAscript, and I did mention the two big exceptions, and I said they are not needed - which is just truth. They were necessary before ES 2015, which is the reason they exist to begin with. Other than that, Microsoft's explicitly stated goal is to keep Typescript perfectly aligned with ECMAScript, and to only add types. Now that the language has all the minimum features they don't make any more changes that require actual transpiling because the code itself - not the types - is "Typescript only" and not part of ECMAScript. They will, however, leave in anything that is already there, just like ECMAScript does, because backwards compatibility trumps all. Also note that you can have types-only namespaces that only contain type definitions, which are entirely different: They fall exactly under what I said, types are just removed in the .js file generation step. Those kinds of "namespaces" don't lead to any executable code. Not to mention that you could easily just write the tiny bit of JS yourself instead of using the namespace keyword, because namespaces are simply named JavaScript objects in the global namespace. -- This is all it does: https://www.typescriptlang.org/play?noUnusedLocals=true&noUnusedParameters=true&preserveConstEnums=true&target=99&jsx=0&pretty=true&q=283#code/HYQwtgpgzgDiDGEAEARCYD2A5Aykg3gLABQSS8GwUGANhAHQ0YDmAFACwBMAlANwkBfEkA https://www.typescriptlang.org/play?noUnusedLocals=true&noUn... So if you want the same thing as TS namespaces with just JS code, all you need is a global object and then assign stuff to it, from one or from several modules.