You can control most of this through the package.json file of your projects. You can fix the versions of the libraries and I believe you can also specify a node version as well.
Pinning library versions at least to minor release is pretty standard. As for locking a node version that is a little less common, but possible.
You can also control this by writing a script that ensures a production version of your software uses all the correct versions, so there is less hope that a person that is too busy does it all correctly by hand.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
You can control most of this through the package.json file of your projects. You can fix the versions of the libraries and I believe you can also specify a node version as well.
Pinning library versions at least to minor release is pretty standard. As for locking a node version that is a little less common, but possible.
You can also control this by writing a script that ensures a production version of your software uses all the correct versions, so there is less hope that a person that is too busy does it all correctly by hand.