Skip to content

Conversation

@FND
Copy link
Contributor

@FND FND commented Nov 21, 2025

this saves them the trouble of redundantly reading and deserializing the
manifest file

this assumes that so far nobody uses

  • ... faucetDispatch's return value, other than waiting for completion
  • ... Manifest's toJSON method because that class was never exposed

plus removed a (hopefully) obsolete polyfill

FND added 2 commits November 21, 2025 13:44
this saves them the trouble of redundantly reading and deserializing the
manifest file

this assumes that so far nobody uses
* ... `faucetDispatch`'s return value, other than waiting for completion
* ... `Manifest`'s `toJSON` method because that class was never exposed
@FND FND requested a review from moonglum November 21, 2025 12:46
@FND FND changed the title Manifest exposure exposed manifest to independent API consumers Nov 21, 2025
return res.then(() => ({
get manifest() {
return assetManager.manifest.entries;
}
Copy link
Contributor Author

@FND FND Nov 21, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This might be dangerously misleading: If consumers cache this value, they're gonna be working with an outdated manifest:

let { manifest } = await faucetDispatch();
await faucetDispatch();
console.log(manifest);

Here manifest ends up being a stale copy, not the live object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants