Create a fingerprint value that is exposed to your user environment
$ npm install --save process-fingerprint
var fingerprint = ;;// => "_pf1440759573263"
I ran into an issue recently while building a Metalsmith + Gulp Boilerplate where existing fingerprint modules weren't sharing the fingerprint values nicely across the gulp and metalsmith build processes. This lead me to the conclusion that the fingerprint value should be hoisted up to some globally-available namespace, where the metalsmith and gulp build process could share the same fingerprint value.
I am sure there is a better way to create a fingerprint variable, perhaps I shouldn't be using the
object for my own silly experiments, but for now, this approach will solve the problem of making a global
fingerprint across multiple build processes. I will use this module with caution until my experiments lead me
to believe that this is a worthwhile fingerprinting method.
Please open an issue to start a discussion, share your thoughts or offer suggestions
MIT @ Michael Wuergler