Define NodeExePath within MSBuild Target

When the NodeExePath property is left undefined (and so relying on the default installed path) there doesn't appear to be any access for custom MSBuild rules to use the "default" value.
Could this default value be set on the property (preferably somewhere before the Build target) so that it is possible for MSBuild targets to make use of it?
For our own case - in brief - we import a custom MSBuild .targets file to run the locally installed webpack, parse the output, fill out the VS Error List and "npm pack" the package if the build was successful.
Currently this is possible but it is made flimsy by implicit calls to node/npm (relying on PATH to be setup in the right order) or explicit calls (not good for source control).

The issue names no files or tests; start by locating the MSBuild target that defines or consumes NodeExePath and inspect how the default installed path is resolved. Make that default available before the Build target, then verify that custom MSBuild targets can use it without relying on PATH or implicit node/npm calls.