Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Commit

Permalink
UNMAINTAINED: See #328
Browse files Browse the repository at this point in the history
  • Loading branch information
lloeki committed Dec 4, 2023
1 parent c5bfafa commit f7f0b56
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,21 @@
A gem for distributing the v8 runtime libraries and headers in both
source and binary form.

### Status: UNMAINTAINED

This project is [UNMAINTAINED](https://github.com/rubyjs/libv8/issues/328).

Why?

- The binding to libv8 that therubyracer implements is quite tight, making updating libv8 a huge amount of work. [mini_racer](https://github.com/rubyjs/mini_racer) has a thinner interface for that reason.
- So many issues come from depot tools and the bespoke v8 toolchain, which only support what Google Chrome needs to support. [libv8-node](https://github.com/rubyjs/libv8-node) has been created to tackle those issues, leveraging the good work of Node.js people, and mini_racer uses that.

If you use a mini_racer that depends on libv8, please move to a more recent version.

If you use therubyracer and are thus stuck with v8 3.16, please move to mini_racer. If one of your dependencies uses therubyracer, please reach out to them so that they upgrade to mini_racer.

If there are needs coming from either libv8 or therubyracer that you feel are unmet by mini_racer + libv8-node, please open issues on their respective repositories.

### Why?

The goal of libv8 is two fold: provide a binary gem containing the a
Expand Down

0 comments on commit f7f0b56

Please sign in to comment.