Evaluate if embedding Node.js as a static library is easier than embedding V8

[aschaeffer]

No description provided.

[aschaeffer]

Related Issues

• Add an embedding API for Node.js nodejs/node#5265
• doc: better document --shared build nodejs/node#14158
• Discussion: How should the Node executable + Node shared library be distributed? nodejs/node#24028
• Form team/group to define "embedding requirements" nodejs/user-feedback#51
• How to embed node.js? nodejs/help#818

Related Projects

• N-API: An api for embedding Node in applications nodejs/node#23265 (comment)

Relevant Work / PRs

• test: --enable-static linked executable nodejs/node#14986
• tracing: etw/perf/lttng/etc multi-isolate support nodejs/node#18074
• Extend shared library interface nodejs/node#19005
• worker: initial implementation nodejs/node#20876

Documentation about embedding

• https://electronjs.org/blog/electron-internals-using-node-as-a-library (08/2016)
• Question: Embedding NodeJS to run many scripts nodejs/help#1031

[aschaeffer]

It seems this wouldn't solve the actual problem because we still need V8 as static library:

nodejs/help#1415 (comment)

You are doing it right and you can use the libnode.a in your C/C++ project. However, you still need other static libraries when you build your final executable, like libuv, v8, icu, openssl, http_parser and etc. And you can find these static libraries under out/deps

[aschaeffer]

denoland/deno#1666

[viferga]

Hi! If you are interested in embedding NodeJS or V8, you may be interested in trying MetaCall: https://github.com/metacall/core

We have a simple example for embedding NodeJS (as a dynamic library) into C/C++: https://github.com/metacall/embedding-nodejs-example