René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Handle the case where one cannot execute JavaScript","articleBody":"Re #30327 #37236\r\n\r\nOne (somewhat elaborate?) API for semver-minorly handling the inability to execute JS would be the following (somewhat introspective) API:\r\n\r\n```cpp\r\ntypedef enum {\r\n  node_api_reason_call_function,\r\n  node_api_reason_throw_exception,\r\n  node_api_reason_open_handle_scope,\r\n  node_api_reason_open_escapable_handle_scope,\r\n  node_api_reason_open_callback_scope,\r\n  ...   // etc.\r\n} node_api_js_exec_failure_reason;\r\n\r\ntypedef napi_status (*node_api_js_exec_failure_callback)(\r\n    napi_env env,\r\n    node_api_js_exec_failure_reason reason,\r\n    void* reason_data,\r\n    void* user_data);\r\n\r\nNAPI_EXTERN napi_status\r\nnode_api_handle_js_execution_failure(\r\n    napi_env env,\r\n    node_api_js_exec_failure_callback exec_fail_cb,\r\n    void* user_data);\r\n```\r\n\r\nThe add-on maintainer would attach a callback similarly to the `napi_set_instance_data` finalizer, which would get called whenever we would otherwise return `napi_cannot_call_into_js`. The callback would analyze the reason and the associated `reason_data` (which would be a pointer to a stack-allocated structure the type of which depends on `reason` – a little bit like `ioctl(2)`) and would return a `napi_status` that would then be passed as the return value to the original Node-API call.\r\n\r\nThis could be used to correct a return value of `napi_pending_exception` from a call to, say, `napi_call_function` into a return value of `napi_ok`.","author":{"url":"https://github.com/gabrielschulhof","@type":"Person","name":"gabrielschulhof"},"datePublished":"2021-02-19T18:41:13.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/37446/node/issues/37446"}