bpstrngr

I have this issue when running nodemon in a fuse mount, I don't know how these file change events look like and what handles them, might this be a similar...

i ran into this too, to me it happens without the function using destructuring too. (v6.0.0)

@eternal191 that experiment has not been available in devtools for a while.

May not seem like a huge deal at first, but if i intend to allow defaulting to json import attribute for imports of json extensions, which is arguably reasonable, if...

loosely related to nodejs/loaders#163 , in being my second encounter with an untracable error message from beyond the "load" hook in a load sequence.

~~ah so the error actually is that import statements are statically analysed beyond "load", and it isn't matching the cached respective "resolve" entry?~~ or, more likely, i figure it rather...

haha you may assume more of me, either in smarts that i know what you mean or in stubbornness that i'm protesting; i don't see the fragility there, is it...

@aduh95 21.1 now when i'm encountering it again. i'm returning {source,format,shortCircuit} entries from the registered "load" hook for many files, and at some point all i see is: ``` node:internal/event_target:1084...

actually inserting a re-parse/serialization in the load hook to get usable stack trace wasn't a big issue and it solved my problem, but the fact that i have to parse...

sorry i dropped out a bit, i layed off trying to control my chromebooks for a bit, but i'm still interested and will get back to testing. Two things i'd...