Pooya Parsa
Pooya Parsa
Wondering if we could make it safer (and faster) by using ohash for comparing log objects instead of full serialization.
This is really nice work with tests coverage 🚀 I think it is almost time we think about supporting extended serializers (like a preset addon for supporting HTML serialization), even...
Do you recall if we have the same trade-off in v8 based runtimes / Node.js specifically?
Can you please write an overview of changes 🙏
Thanks for suggestion (sorry for my late replies, busy on h3 releases I will be back to help on unwasm triage and improvements ASAP)
What about `JITI_CACHE: rebuild`
Yes it is primary fs cache. We could also have dedicate flag `JITI_REBUILD_FS_CACHE` / `rebuildFsCache` (or invalidate*)
Adding another option might make better sense since it is a new functionality. First I was thinking of new cache building mode but it is more of a one-off mode.
Thanks for PR dear @kricsleo Can you please retarget to v2 (considering #3208) also confirm if fix tested on prod? (you can add a [test](https://github.com/nitrojs/nitro-deploys/tree/main/server/routes/tests) to nitro-deploys that fails with...
(drafting until we support `jiti.import` to avoid breaking changes for current jiti users)