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.
Summary
Docusaurus v2: this plugin throws.
We write a manifest simply with:
Then we read it with
getBundles(manifest, modulesToBeLoaded);
This leads to errors like:
Why
Fix error reported by Docusaurus 2 user here: facebook/docusaurus#2898
There is a Github repro, the manifest gets written to
.docusaurus/client-manifest.json
if you want to take a look.I've uploaded the manifest here: https://gist.github.com/slorber/f1ba0d0fd4b7e22f0464a9782a9f9395
The asset 14 seems to be missing, producing the
Object.keys(undefined)
errorChecklist
At this point I'd like to know if this fix seems legit to you. For the Docusaurus 2 usecase it seems to work, as I was able to build the site.
Maybe this manifest issue hides a deeper problem. In such case we should rather keep a fail-fast behavior and fix the underlying issue instead?
Or maybe it's safe to ignore a missing asset in the manifest, I have no idea 🤪
errors
orwarnings
approved terminology
unit tests
, if apply.