GeezerVisonThe World Wide Web, restored to 800 pixels of glory. |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites |
GeezerVison is showing v8.dev — What to do if your CL broke the Node.js integration build · V8 What to do if your CL broke the Node.js integration buildNode.js uses V8 stable or beta. For additional integration, the V8 team builds Node with V8's main branch, i.e., with a V8 version from today. We provide an integration bot for Linux, while Windows and Mac are in the works. If the Source #Follow the instructions at the node-ci repository to check out source. Test changes to V8 #V8 is set up as a DEPS dependency of node-ci. You may want to apply changes to V8 for testing or to reproduce failures. To do so, add your main V8 checkout as remote: Remember to run gclient hooks before compiling. Make changes to Node.js #Node.js is also set up as a Get the Node sources #Fork V8’s Node.js repository on GitHub (click the fork button) unless you already did previously. Add your both your fork and V8’s fork as remotes to the existing checkout:
Make your changes to the Node.js checkout, and commit them. Then push the changes to GitHub: And create a pull request against the branch Once the pull request has been merged to V8’s fork of Node.js, you need to update node-ci’s |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |