{"push_id":1077452570,"size":1,"distinct_size":1,"ref":"refs/heads/symlink-require","head":"916fbd6210ec8cc3691bfcef8aba6e78b9a03a97","before":"30288b11ce150c18d2285033ef3c4d72e6cf2893","commits":[{"sha":"916fbd6210ec8cc3691bfcef8aba6e78b9a03a97","author":{"email":"9cda2ef467ac5ed4de7f7ae45dc5cd3000965f95@vt.edu","name":"Alex Lamar"},"message":"module: preserve symlinks when requiring\n\nCurrently, required modules use the real location of the\npackage/file as their __filename and __dirname, instead\nof the symlinked path if it exists. This behaviour is\nundocumented (it even goes against documentation in\ncertain scenarios), creating hard-to-debug problems\nfor developers who wish to leverage filesystem abstractions\nto lay out their application.\n\nThis patch resolves all required modules to their canonical\npath while still preserving any symlinks within the path,\ninstead of resolving to their canonical realpath. The one\nspecial case observed is when the main module is loaded\n-- in this case, the realpath does need to be used\nin order for the main module to load properly.","distinct":true,"url":"https://api.github.com/repos/digitalbazaar/node/commits/916fbd6210ec8cc3691bfcef8aba6e78b9a03a97"}]}