v8/tools/node
Yang Guo 169fe8c2ad [node] remove everything before updating v8.
This ensures that we have a clean slate when updating to newer V8.

TBR=machenbach@chromium.org

Bug: v8:8584
Change-Id: I37f6e4a42738e5e9ea5bfdca5465d6a3e984fe65
Reviewed-on: https://chromium-review.googlesource.com/c/1378169
Reviewed-by: Yang Guo <yangguo@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#58242}
2018-12-14 14:14:26 +00:00
..
testdata Roll googletest to 1.8.0+. 2018-03-23 07:54:27 +00:00
build_gn.py build_gn.py: Forward BUNDLED_WIN_TOOLCHAIN_ROOT 2018-04-25 16:13:13 +00:00
fetch_deps.py [node] also remove deleted files that are gitignored. 2018-12-13 09:10:54 +00:00
node_common.py [tools] Fix missing import in node script 2018-07-25 13:18:25 +00:00
README.md [tools] Remove node backport script and leave a readme 2018-11-09 14:08:43 +00:00
test_update_node.py Roll googletest to 1.8.0+. 2018-03-23 07:54:27 +00:00
update_node.py [node] remove everything before updating v8. 2018-12-14 14:14:26 +00:00

Node.js Backports

We no longer maintain our own backport script.

For backporting V8 changes to Node.js, there is a useful script in node-core-utils. You can use the git node v8 backport command, which will bump the necessary V8 version numbers depending on the specific branch.

See the Node.js documentation on V8 backports for a guide.