Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc: recommend not using libuv node-api function #53521

Closed
wants to merge 5 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update n-api.md
  • Loading branch information
mhdawson authored Jun 21, 2024
commit 29e95f61f78adc362d5b22c01fe22b67104cb163
2 changes: 2 additions & 0 deletions doc/api/n-api.md
Original file line number Diff line number Diff line change
Expand Up @@ -6244,6 +6244,8 @@ NAPI_EXTERN napi_status napi_get_uv_event_loop(node_api_nogc_env env,
Note: While libuv has been relatively stable over time, it does
not provide an ABI stability guarrantee. Use of this function should be avoided.
mhdawson marked this conversation as resolved.
Show resolved Hide resolved
Its use may result in an addon that does not work across Node.js versions.
legendecas marked this conversation as resolved.
Show resolved Hide resolved
[asynchronous-thread-safe-function-calls](https://nodejs.org/docs/latest/api/n-api.html#asynchronous-thread-safe-function-calls)
are an alternative for many use cases.

## Asynchronous thread-safe function calls

Expand Down