Google Git
Sign in
chromium / v8 / node-ci / c580d5585bc1db1fcf0d907a920136e556cf5bb2
commitc580d5585bc1db1fcf0d907a920136e556cf5bb2[log] [tgz]
authorpthier <pthier@chromium.org>Thu Aug 28 13:08:09 2025
committerNode-ci LUCI CQ <node-ci-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Aug 28 13:53:35 2025
treef5d6e33d5cd855d12a76cdd2692012794d2c99f4
parentbfb2bfc2fab6c5c6721f660b788dab3b9a0f93a5 [diff]
Update node

- Update node to node-ci-2025-08-20
- Update all other deps to latest version (except depot_tools, which
  caused issues. On other bots we use the system depot_tools instead
  of the project specific third_party/ one, so we don't have issues
  there. We will change node-ci to also use the system depot_tools).

Change-Id: I91333744d9f208e0393f95b5f79ec4e71abbd124
Reviewed-on: https://chromium-review.googlesource.com/c/v8/node-ci/+/6871413
Auto-Submit: Patrick Thier <pthier@chromium.org>
Reviewed-by: Victor Gomes <victorgomes@chromium.org>
Commit-Queue: Victor Gomes <victorgomes@chromium.org>
1 file changed
tree: f5d6e33d5cd855d12a76cdd2692012794d2c99f4
  1. build_overrides/
  2. gn/
  3. node_tests/
  4. testing/
  5. third_party/
  6. tools/
  7. .gitignore
  8. .gn
  9. BUILD.gn
  10. codereview.settings
  11. DEPS
  12. LICENSE
  13. Makefile
  14. README.md
README.md

Node.js built with GN

This project is a set of dependency and build configurations to build Node.js with GN.

Background

V8 was originally built with SCons. Following Chromium, it made the switch to GYP, completing around 2012. That was when Node.js started its success story. However, again following Chromium, V8 made the switch to GN, completing in 2016. So far, Node.js has hesitated in adopting GN. One of the reasons is its now established native modules ecosystem that relies on GYP for build configuration.

Electron, having both Chromium and Node.js as its dependencies, adopted GN. Many files in this repository have been derived from the Electron project, with appropriate changes to avoid the need for forking files, to implement a standalone build, or to fix test failures.

Some reading material:

Instructions

Checking out source

Get depot_tools first.

mkdir node-ci
cd node-ci
fetch node-ci

Alternatively, you can

mkdir node-ci
cd node-ci
git clone https://chromium.googlesource.com/v8/node-ci
gclient config https://chromium.googlesource.com/v8/node-ci --unmanaged

Build

cd node-ci
make deps
make node

Test

JOBS=4 make test

Advanced build configurations

For more advanced build options, check out tools/gn-gen.py --help.

Update dependencies

To update a dependency, e.g. V8 or Node.js, use gclient to update DEPS.

gclient setdep --var=v8_revision=<updated-git-hash>

To apply changes, e.g. for local testing, use git:

cd v8
git remote add local-v8 <path-to-v8-checkout>/.git
git fetch local-v8
git checkout local-v8/<your-branch>

Project priorities

  • Stay as slim as possible. By avoiding to fork files from dependencies, future maintenance becomes less a hassle.
  • Pull necessary sources as dependencies rather than checking in the sources.
  • Stay as up-to-date as possible. The point of this is to be able to build with newest versions of dependencies, including Node.js, V8, and ICU.
  • Simplicity. It should be easy to get up and running.

Not yet implemented

  • Support building on Windows. The current configurations have been tested for Linux and Mac.
  • Platform-specific OpenSSL build configurations. The current build only supports the slowest platform-independent configuration.

Explicit non-goals

  • To translate every configuration from the GYP build.
  • To support platforms not supported by Chromium.
  • To replace Node.js' test runner with the one used by V8.
  • To use GN to build native modules.

Advantages over upstream Node.js

  • Proper dependency management. Upgrading dependencies is just a small change in DEPS.
  • No need to port V8 changes to GYP.
  • Availability of sanitizers.
  • Ability to use GN features such as jumbo builds.
  • Toolchain to build is bundled as dependency.