---
title: "Comment by Nishant Kumar on \"Avoiding Memory Leaks in Javascript\" | Hashnode"
description: "or use TypeScript."
url: "https://hashnode.com/posts/avoiding-memory-leaks-in-javascript/63db6d663d67acafcc33353f/comment/63db8e2249e190746f260d57"
---

[Discussion](https://hashnode.com/posts/avoiding-memory-leaks-in-javascript/63db6d663d67acafcc33353f)

Comment [Avoiding Memory Leaks in Javascript](https://hashnode.com/posts/avoiding-memory-leaks-in-javascript/63db6d663d67acafcc33353f)

[Nishant Kumar](https://hashnode.com/@nisnym)

[Feb 2, 2023](https://hashnode.com/posts/avoiding-memory-leaks-in-javascript/63db6d663d67acafcc33353f/comment/63db8e2249e190746f260d57)

or use TypeScript.

[Mohamed Higgy](https://hashnode.com/@higgy)

[Feb 2, 2023](https://hashnode.com/posts/avoiding-memory-leaks-in-javascript/63db6d663d67acafcc33353f/comment/63db8e2249e190746f260d57#reply-63dba02fc214a5749ea851bd)

Hi Nishant, thanks for your comment

Some developers find TypeScript to be too complex for their needs or may not have the resources to set it up in their workflow. Ultimately, the choice between using TypeScript or not depends on individual preferences, and the development team's skills and experience. However, it is important to remember that TypeScript is not a guarantee against memory leaks, and proper coding practices must still be followed to avoid them.

[Nishant Kumar](https://hashnode.com/@nisnym)

[Feb 9, 2023](https://hashnode.com/posts/avoiding-memory-leaks-in-javascript/63db6d663d67acafcc33353f/comment/63db8e2249e190746f260d57#reply-63e4fbc1f30581f89abcbe76)

agreed. worth reading your article. [Mohamed Higgy](https://hashnode.com/@higgy)
