snek comments

Results 463 comments of


                                            snek

Utility method for exposing Node’s type resolution

after all is said and done we should be able to load json and native add-ons with import too. the process of migration is always going to be tough.

import(cjs) with query strings has odd behavior

everything here seems to be working as intended. its just weird and complex because two separate module systems with separate caches are being welded together.

import(cjs) with query strings has odd behavior

@ljharb its a new esm module, but it hits the existing require cache.

import(cjs) with query strings has odd behavior

when ?q=2 runs, it puts a new entry into require.cache. ?q=3 hits that cache entry.

import(cjs) with query strings has odd behavior

@ljharb query strings are always preserved in esm, and always normalized out in cjs. In this case, each ?q=x is a new esm module, but that new esm module may...

import(cjs) with query strings has odd behavior

q=0, q=1, q=2, q=3 are all distinct es modules. "re-evaluating" in this case refers to whether the cjs module they wrap reruns.

import(cjs) with query strings has odd behavior

simplified example: https://engine262.js.org/#gist=31db83a9a28067300fccedc80b9e7725

import(cjs) with query strings has odd behavior

you have to create wrappers for anything that isn't a module. the vm.SyntheticModule class can help you with that.

import(cjs) with query strings has odd behavior

@SMotaal sometime after esm is stable.

Loader Hooks

I think the current exposed hooks are the right hooks to expose, but we definitely need to work on polishing the API: - dynamic modules are a bit rough atm...