-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Open
Labels
debuggerChrome DevTools inspector/debugger integrationChrome DevTools inspector/debugger integrationpanic
Description
I'm only able to reproduce it in one particular project so far where I've messed with stuff in node_modules
quite a bit. Not sure how to slim it down at the moment.
============================================================
Deno has panicked. This is a bug in Deno. Please report this
at https://github.com/denoland/deno/issues/new.
If you can reliably reproduce this panic, include the
reproduction steps and re-run with the RUST_BACKTRACE=1 env
var set and include the backtrace in your report.
Platform: macos aarch64
Version: 2.4.3
Args: ["deno", "run", "-A", "--inspect-brk", "npm:vite"]
View stack trace at:
https://panic.deno.com/v2.4.3/aarch64-apple-darwin/o_x2KogqztBwjoguBw6nguBoz0guB47ohNo55a
thread 'main' panicked at cli/main.rs:490:5:
Fatal error in :0: Check failed: needs_context && current_scope_ == closure_scope_ && current_scope_->is_function_scope() && !function_.is_null() implies function_->context() != *context_.
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Version: Deno 2.4.3
Metadata
Metadata
Assignees
Labels
debuggerChrome DevTools inspector/debugger integrationChrome DevTools inspector/debugger integrationpanic