chore(deps): bump @rspack/core in Faster from 1.2.0-alpha.0 to 1.2.2 #10870
+65
−65
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.
Pre-flight checklist
If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.If this is a new API or substantial change: the PR has an accompanying issue (closes #0000) and the maintainers have approved on my working plan.Motivation
According to #10823 (comment), the change planned in Rspack 1.2.3 increases the chance of enablement of the persistent cache in Docusaurus Faster powered. That in the current Rspack version is incompatible especially with assets of imported images.
However, Docusaurus Faster still pins Rspack to the unstable 1.2.0-alpha.0 today even though 1.2.2 has been released. This PR makes Docusaurus Faster accept stable Rspack versions including 1.2.3 or later.
Test Plan
Everything works as usual without any regressions even when Faster is enabled.
Configurations without Faster are not affected by this PR.
Test links
Deploy preview: https://deploy-preview-_____--docusaurus-2.netlify.app/
Related issues/PRs
#10823