fix(#18600): use user’s Node version for @types/node version instead of fixed version
This PR resolves the issue #18600 and improves upon the previous PR #18642:
It uses the user's current Node.js version to dynamically determine the version of @types/node, instead of using a fixed version. This improvement ensures that the @types/node version matches the Node.js version the user is actually using, avoiding potential compatibility issues.
This approach is more flexible than using a fixed version, reducing the hassle of manually updating dependencies and improving the maintainability and stability of the project.
fix(#18600): use user’s Node version for @types/node version instead of fixed version
This PR resolves the issue #18600 and improves upon the previous PR #18642:
@types/node, instead of using a fixed version. This improvement ensures that the@types/nodeversion matches the Node.js version the user is actually using, avoiding potential compatibility issues.