snek
snek
@SMotaal showing people the differences is good, but there's no reason to actually rely on these checks in code. Maybe if you're doing some advanced bundling or something, although even...
just to be clear, I'm against import.meta.type. The objects should be identical to the ones in modules.
sometimesModule.js shouldn't be possible. If it *is* possible, we have a bug.
@smotaal ambiguity breeds confusion. This is one of the reasons I'm not a fan of `type: module`. Changing the location of a file on disk really shouldn't change how it's...
Sure different versions of node could do that, but they could also break your detection system. I don't think that's a path worth going down.
loader hooks don't have caches, they respond to the main loader needing to fill in its own cache.
@jkrems i'm not sure what you mean by "try to use import/require/etc". each realm has a loader. each loader can have hooks, which run in separate realms/threads.
ahhhhh i understand now. those imports would be subject to the hooks of the current realm, of which there are none. whether or not we modify the hook behaviour there,...
the larger hazard is that we want to run loaders in their own threads, so that would be impossible anyway. i was talking about this with bradley at some point...
It is intended to return a ProgramWithDefines. The examples which use `pio_asm!` use `program.program`. I'm not sure there is really any issue here, you changed the API you were calling...