The only “official” node repository is https://github.com/joyent/node. For code, docs, tests, or anything else, joyent/node is the repository that reflects the official state of the Node.js project. That’s where all patches have to end up if they are going to be in the release, website, or API docs. To submit a patch fork the repository and send a pull request via GitHub to joyent/node.
make jslintto validate.
Node uses an automated test suite run via “make test”. To create a new test file, select an appropriate subdirectory of “test/” and create a file named “test-<something>.js” – where the “<something>” indicates what is being tested. See the other tests in those directories for examples of how to write tests. Generally this involves calling
assert.equal() to check things match your expected outcome. Every new feature MUST have tests or it will not be accepted into the node core.
To generate patch files:
git format-patchcommand to generate patch files.
For more detailed information on managing a Git repo, please visit the Contributing for Dummies page.
These are some things to consider before thinking about patching node core:
Last edited by Kevin Ji,