Closed benStre closed 1 week ago
Sorry for the problem, we'll most likely cut a patch release, once we identify the problem.
Is your repository open source so we could try it ourselves?
Thank you! The problem occurs when running a project with UIX (e.g. https://github.com/unyt-org/uix-base-project)
It can be reproduced by running this module with Deno: https://raw.githubusercontent.com/unyt-org/uix/uix-new/run.ts
deno run -A --import-map https://cdn.unyt.org/importmap.json https://raw.githubusercontent.com/unyt-org/uix/uix-new/run.ts
Thanks, we're investigating right now.
If we throw errors as part of import (async/await) loading, this can be reproduced.
It turns out there are several bugs in recent changes to V8's module loading, and I'm working on getting them fixed (e.g. https://chromium-review.googlesource.com/c/v8/v8/+/5807477). But on a slightly positive note, all these bugs are caused by throwing at the top level of a module that uses TLA (along with having complex module graphs), which means that this only affects code which ran unsuccessfully.
https://chromium-review.googlesource.com/c/v8/v8/+/5807477 seems to be resolved
Version: Deno 1.46.0 +
Since the upgrade to version 1.46.0, I am getting this fatal error when starting a Deno project. I have not yet been able to track down where the problem originates from in my project because the project is quite complex.