[TIMOB-19792] Android: Investigate use of NAN to abstract V8 API changes and support building against multiple V8 library versions
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Medium |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2016-02-25T15:35:55.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | Release 6.0.0 |
| Components | Android |
| Labels | look1 |
| Reporter | Christopher Williams |
| Assignee | Christopher Williams |
| Created | 2015-10-26T14:41:50.000+0000 |
| Updated | 2017-07-26T03:35:23.000+0000 |
Description
In the node community, they've developed a project called NAN to abstract the v8 apis. The intention is to allow developers to pull in these headers and code against the latest V8 API but still be able to build/target older versions through adapter interfaces.
https://github.com/nodejs/nan
This may be useful for us if we want to shield ourselves a little from V8 API changes, but really would only give us the benefit of being able to target older V8 versions over time. We'd still need to update when we pull in new V8 versions.
It _may_ be useful as an abstraction for native module developers, though?
NaN looks nice, but is geared for Node. It is useful as a reference for how the V8 Apis evolved over time though.