fix: stack traces in non-Node.js contexts (#26820)
This commit is contained in:
parent
1a79bedb27
commit
76f721474e
3 changed files with 52 additions and 0 deletions
|
@ -503,6 +503,13 @@ node::Environment* NodeBindings::CreateEnvironment(
|
|||
// context. We need to use the one Blink already provides.
|
||||
is.flags |=
|
||||
node::IsolateSettingsFlags::SHOULD_NOT_SET_PROMISE_REJECTION_CALLBACK;
|
||||
|
||||
// We do not want to use the stack trace callback that Node.js uses,
|
||||
// because it relies on Node.js being aware of the current Context and
|
||||
// that's not always the case. We need to use the one Blink already
|
||||
// provides.
|
||||
is.flags |=
|
||||
node::IsolateSettingsFlags::SHOULD_NOT_SET_PREPARE_STACK_TRACE_CALLBACK;
|
||||
}
|
||||
|
||||
node::SetIsolateUpForNode(context->GetIsolate(), is);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue