You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be helpful if the deno CLI provided the option to display where a permission request is coming from. In situations where a permission request is unexpected it'd help the developer understand whether the permission request is legit or not. Or in the case that a developer needs to debug where the permission request is coming from, it would assist with that.
Today when a permission request is encountered the following is output:
┌ ⚠️ Deno requests env access.
├ Run again with --allow-env to bypass this prompt.
└ Allow? [y/n/A] (y = yes, allow; n = no, deny; A = allow all env permissions) >
This prompt could be modified to include an option to output the current stack trace:
┌ ⚠️ Deno requests env access.
├ Run again with --allow-env to bypass this prompt.
└ Allow? [y/n/t/A] (y = yes, allow; n = no, deny; t = trace, A = allow all env permissions) >
Choosing t would output a stack trace of where the permission is being requested, including the filename, line numbers, etc. After outputting the trace, the same prompt would display so the developer could then choose one of the other option.
The text was updated successfully, but these errors were encountered:
It would be helpful if the deno CLI provided the option to display where a permission request is coming from. In situations where a permission request is unexpected it'd help the developer understand whether the permission request is legit or not. Or in the case that a developer needs to debug where the permission request is coming from, it would assist with that.
Today when a permission request is encountered the following is output:
This prompt could be modified to include an option to output the current stack trace:
Choosing
t
would output a stack trace of where the permission is being requested, including the filename, line numbers, etc. After outputting the trace, the same prompt would display so the developer could then choose one of the other option.The text was updated successfully, but these errors were encountered: