[miniflare] fix: remove __STATIC_CONTENT_MANIFEST from module worker env
#4505
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #4374.
What this PR solves / how to test:
When using Workers Sites with a module worker, the asset manifest must be imported from the
__STATIC_CONTENT_MANIFESTvirtual module. Miniflare provided this module, but also erroneously added__STATIC_CONTENT_MANIFESTto theenvobject too. Whilst this didn't break anything locally, it could cause users to develop Workers that ran locally, but not when deployed. This change ensuresenvdoesn't contain__STATIC_CONTENT_MANIFEST.To test this, run
wrangler devinfixtures/sites-appand verify__STATIC_CONTENT_MANIFESTdoesn't appear in theenvobject.Author has addressed the following:
Note for PR author:
We want to celebrate and highlight awesome PR review! If you think this PR received a particularly high-caliber review, please assign it the label
highlight pr reviewso future reviewers can take inspiration and learn from it.