/var/lang/lib/node_modules/npm/node_modules/node-gyp/gyp/docs
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
# Hacking ## Getting the sources Git is required to hack on anything, you can set up a git clone of GYPas follows: ```mkdir foocd foogit clone git@github.com:nodejs/gyp-next.gitcd gyp``` (this will clone gyp underneath it into `foo/gyp`.`foo` can be any directory name you want. Once you've done that,you can use the repo like anything other Git repo. ## Testing your change GYP has a suite of tests which you can run with the provided test driverto make sure your changes aren't breaking anything important. You run the test driver with e.g. ``` sh$ python -m pip install --upgrade pip$ pip install --editable ".[dev]"$ python -m pytest``` See [Testing](Testing.md) for more details on the test framework. Note that it can be handy to look at the project files output by the teststo diagnose problems. The easiest way to do that is by kindly asking thetest driver to leave the temporary directories it creates in-place.This is done by setting the environment variable "PRESERVE", e.g. ```set PRESERVE=all # On Windowsexport PRESERVE=all # On saner platforms.``` ## Reviewing your change All changes to GYP must be code reviewed before submission.