---
title: "Comment by Abheeshta P on \"Easily Update npm Packages Without the Fear of Breaking the Application\" | Hashnode"
description: "This is a great article!! Thanks Yogesh Chavan . I have two questions Is it necessary to run audit can't we skip vulnerabilities? what will be the worst case sc"
url: "https://hashnode.com/posts/easily-update-npm-packages-without-the-fear-of-breaking-the-application/60d2fc654e084d6e649c563b/comment/686627d361daa1db91395fe7"
---

[Discussion](https://hashnode.com/posts/easily-update-npm-packages-without-the-fear-of-breaking-the-application/60d2fc654e084d6e649c563b)

Comment [Easily Update npm Packages Without the Fear of Breaking the Application](https://hashnode.com/posts/easily-update-npm-packages-without-the-fear-of-breaking-the-application/60d2fc654e084d6e649c563b)

[Abheeshta P](https://hashnode.com/@abheeshta)

[Jul 3, 2025](https://hashnode.com/posts/easily-update-npm-packages-without-the-fear-of-breaking-the-application/60d2fc654e084d6e649c563b/comment/686627d361daa1db91395fe7)

This is a great article!! Thanks [Yogesh Chavan](https://hashnode.com/@myogeshchavan97). I have two questions

1.  Is it necessary to run audit can't we skip vulnerabilities? what will be the worst case scenario if we skip it.
2.  Will updating the node itself cause any issues in existing projects? given that it is a major update. Context : I have v20.13.1 and I want to update but not sure if doing so will break my existing projects. Could you please guide me on this?

[Yogesh Chavan](https://hashnode.com/@myogeshchavan97)

[Jul 3, 2025](https://hashnode.com/posts/easily-update-npm-packages-without-the-fear-of-breaking-the-application/60d2fc654e084d6e649c563b/comment/686627d361daa1db91395fe7#reply-686632fda09875e39b216da6)

1.  You should always try to fix all the vulnerabilities when you want to keep your application secure.

Vulnerable dependencies can lead to real-world exploits such as:

-   Remote code execution
-   Data leaks
-   Denial of service (DoS)

By running audits, you're proactively reducing the risk of these issues in your application.

You should at-least fix the high severity vulnerabilities.

2.  You should always check your current project node version, and each of the above nodejs version changelog if there is any breaking change before updating to the latest.

So If your current Node.js version is 17, you should read all the changelog of version 18, 10 and 20 If you want to update to 20 to see if there is any breaking change, and gradually update your project version to 18 first, then 19 and then 20 to see if anything breaks.

You can use [https://github.com/nvm-sh/nvm](https://github.com/nvm-sh/nvm) to update node.js version without manual uninstall and install.

[Abheeshta P](https://hashnode.com/@abheeshta)

[Jul 3, 2025](https://hashnode.com/posts/easily-update-npm-packages-without-the-fear-of-breaking-the-application/60d2fc654e084d6e649c563b/comment/686627d361daa1db91395fe7#reply-68666ca0ae77ed58b87eef90)

Thank you!! I will try using nvm for managing different versions of node. [Yogesh Chavan](https://hashnode.com/@myogeshchavan97)
