perf: single cache file

[dsherret]

This is for Deno 2. See denoland/deno#17707 for details.

Format:

<content>\n// denoCacheMetadata=<metadata><EOF>

File format considerations:

1. We can reuse the original vector we read the file from by storing the content first and then truncating the vector to the content.
2. The file has a comment on the last line. This makes it still work if loaded as a TS/JS file. Obviously it will not work if this is something like Wasm and someone loads that, but when deno reads this file it removes the comment.
3. The metadata is json. This makes it easier to add properties in the future.
4. It's probably best for perf to read this file in one shot to reduce fs calls (especially on network drives), so reading the whole file and extracting out the metadata is ok.
5. We still want users to easily read the code in this file if they inspect it (so it doesn't use binary)

[lucacasonato]

You can use serde_json::to_writer, directly into the result buffer here. Saves one allocation.

[dsherret]

I'll try to do an estimate of the capacity.

[dsherret]

Oh, we're serializing this for the time lol. I'll change this to a single number.

{
    "secs_since_epoch": 1720706015,
    "nanos_since_epoch": 697076300
  }

[lucacasonato]

Print a debug!() if we fail to parse the metadata, or fail to parse the json?

[dsherret]

I think it's ok because we have tests here and in the CLI that ensure the cache is working. Maybe if it becomes an issue?

[dsherret]

I think only storing seconds is ok?

[lucacasonato]

LGTM