as this link says:

Use caret requirements for dependencies, such as "1.2.3", for most situations. This ensures that the resolver can be maximally flexible in choosing a version while maintaining build compatibility.

Avoid overly narrow version requirements if possible. For example, if you specify a tilde requirement like bar="~1.3", and another package specifies a requirement of bar="1.4", this will fail to resolve, even though minor releases should be compatible.

Using Tild requirements doesn't allow us to have compatibility between differente minor versions. So it gives us the understanding that it works the same for npm, because the caret requirements allow a wider range of versions, allowing different minors.