Pooya Parsa
Pooya Parsa
Thanks for PR. Keeping this idea on hold since there are install size concerns + we are introducing new uis (`/_nitro/scalar`)
unstorage is a KV database you need one `getItem` + one `setItem`
Some had been added through this patch: https://github.com/unjs/unwasm/blob/main/patches/%40webassemblyjs__helper-wasm-bytecode.patch PR welcome to add any missing one
@babs20 [this page](https://nodejs.org/api/esm.html) might explain it. Essentially when traversing the exports object, we match the first condition (from `conditions` array user pass) and then fallback to `default` if it exists....
With jiti v2, we have adopted native-ESM support and top level imports supported out of the box for main `jiti` CLI.
Thanks for issue and PR. But can you please explain what is general usecase is for this addition in undocs deployed sites?
Can you help making a minimal nitro reproduction without tanstack-start plugin? cc @schiller-manuel
No worries. I will also try to investigate later but might be much easier to find root cause with minimal reproduction. We will fix it 💯
Testing locally, original reproduction is ONLY valid on windows, `path.join('https://example.com', 'image.png')` on POSIX, returns `https:/example.com/image.png` in Node 22.12. (path utils are not URL utils..) The second issue with UNC, is...
/cc @antfu If you have any ideas.