v8/tools/node
Peter Marshall a522da3935 [tools] Remove node backport script and leave a readme
There is a better maintained script in node-code-utils which properly
bumps the version numbers for each of the LTS branches, which is more
useful. Node collaborators also use this script, so it will make
backports more uniform.

Change-Id: If5449b8a801c4bd14f39d59b7af52cc959989be7
Reviewed-on: https://chromium-review.googlesource.com/c/1328927
Reviewed-by: Yang Guo <yangguo@chromium.org>
Commit-Queue: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#57393}
2018-11-09 14:08:43 +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] check out wasm-js as a dependency 2018-10-12 19:07:00 +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 [build] Remove catapult dependency for node.js 2018-10-04 08:06:06 +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.