nodejs/node

Option to have a shared V8 library?

Open

#53,509 创建于 2024年6月19日

在 GitHub 查看
 (14 评论) (0 反应) (0 负责人)JavaScript (35,535 fork)batch import
feature requesthelp wantedv8 engine

仓库指标

Star
 (117,218 star)
PR 合并指标
 (平均合并 18天 17小时) (30 天内合并 219 个 PR)

描述

What is the problem this feature will solve?

In distros like NixOS and GuixSD, building NodeJS from scratch is a heavy computation. Building vendored V8 NodeJS is not only computationally heavy, but it also makes caching the good parts of the library impossible for a simple failed test. It is painful having to wait for a day to have a package build, only for the tests to fail for the package maintainer to disable or patch them one by one per build.

What is the feature you are proposing to solve the problem?

With V8 as a shared library, it would be possible to not only cache the dependency in a functional package manager, but also use it with other packages that require them.

What alternatives have you considered?

None, as I've read somewhere than v8 dependencies are patched, which would make it impossible to use vanilla v8 alongside.

贡献者指南