Je Xia
Je Xia
yeah PR #1036 did fix this issue accutally, i will open another PR for this ASAP
> https://github.com/sickl8/esm.sh/tree/feat-get-version-closest-to-date-or-timestamp so fast!
the server uses memory for caching npm package info with configurable TTL, no back storage https://github.com/esm-dev/esm.sh/blob/02cb1c502ac716ae93fae4756e59ba9e248110a9/server/npm.go#L347-L352
i just view your code, looks great. maybe you can start with this branch: https://github.com/esm-dev/esm.sh/tree/at-flag, you can get the `at` param form `BuildContext.args.at`, it's stored as a timestamp in `uint32`
please join esm.sh server here: https://discord.gg/XDbjMeb7pb
i prefer using `uint32` that is enough for unix time without nsec right? and it can be encode to 4 bytes (i want to keep the url as short as...
closed by #1152
this happens if there are too many build tasks in the queue and it's your first time accessing the module(including version updated), then you should wait for a while until...
do you set `basepath` to `esm/esm`?
i see, thanks! i will look into it