Commit de46e68
node-api: update libuv ABI stability note
PR-URL: #62789
Reviewed-By: Richard Lau <richard.lau@ibm.com>
Reviewed-By: Santiago Gimeno <santiago.gimeno@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>1 parent 1cd3694 commit de46e68
1 file changed
Lines changed: 7 additions & 5 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -6569,11 +6569,13 @@ NAPI_EXTERN napi_status napi_get_uv_event_loop(node_api_basic_env env, | |||
| 6569 | 6569 | * `[in] env`: The environment that the API is invoked under. | |
| 6570 | 6570 | * `[out] loop`: The current libuv loop instance. | |
| 6571 | 6571 | ||
| 6572 | - Note: While libuv has been relatively stable over time, it does | ||
| 6573 | - not provide an ABI stability guarantee. Use of this function should be avoided. | ||
| 6574 | - Its use may result in an addon that does not work across Node.js versions. | ||
| 6575 | - [asynchronous-thread-safe-function-calls](https://nodejs.org/docs/latest/api/n-api.html#asynchronous-thread-safe-function-calls) | ||
| 6576 | - are an alternative for many use cases. | ||
| 6572 | + Note: While libuv only [guarantees ABI stability](https://github.com/libuv/libuv?tab=readme-ov-file#versioning) | ||
| 6573 | + in a major version, its use may result in an addon that does not work across | ||
| 6574 | + Node.js major versions. | ||
| 6575 | + | ||
| 6576 | + [ThreadSafeFunction](#asynchronous-thread-safe-function-calls) | ||
| 6577 | + is an ABI-stable alternative for many use cases to calling into the | ||
| 6578 | + JavaScript thread from another thread. | ||
| 6577 | 6579 | ||
| 6578 | 6580 | ## Asynchronous thread-safe function calls | |
| 6579 | 6581 | ||
0 commit comments