fix: bug with precommit check using nvs

[okineadev]

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known):

In this patch, I added to the .husky/pre-commit file an automatic detection of the use of nvs, if the user has nvs - then the pre-commit script will use the standard version of NodeJS

If the standard version is not installed, this can be done using a simple command:

nvs link <version>

This commit closes the issue with this error - #12565

[Teri-anric]

Okey.

[okineadev]

@fazlearefin Done!

[gutjuri]

How would this affect users of nvm that would like to run a nonstandard version of npm?

[okineadev]

How would this affect users of nvm that would like to run a nonstandard version of npm?

This PR contains fixes only for nvs, I don't know anything about nvm bugs, because I don't use it.

[gutjuri]

How would this affect users of nvm that would like to run a nonstandard version of npm?

This PR contains fixes only for nvs, I don't know anything about nvm bugs, because I don't use it.

Typo :) Of course I meant to ask "How would this affect users of nvs that would like to run a nonstandard version of npm?" :)

[okineadev]

How would this affect users of nvm that would like to run a nonstandard version of npm?

This PR contains fixes only for nvs, I don't know anything about nvm bugs, because I don't use it.

Typo :) Of course I meant to ask "How would this affect users of nvs that would like to run a nonstandard version of npm?" :)

I don't even know if anyone has bugs with this - I'll look into them.