-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
feat(core, mdx-loader): deduplicate MDX compilation - siteConfig.future.experimental_faster.mdxCrossCompilerCache
#10479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
⚡️ Lighthouse report for the deploy preview of this PR
|
|
Size Change: +333 B (0%) Total Size: 11.5 MB
ℹ️ View Unchanged
|
✅ [V2]
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
@karl-cardenas-coding I've seen your comment here: #10556 (comment) Can you please share more details about how to reproduce the issue? Ideally, a minimal repro I could run. I can't easily investigate because:
Can you help me reproduce? This way, we can find a way to fix the issue. |
Docusaurus Faster
This PR is part of the Docusaurus Faster project aiming at reducing production build times
Motivation
When building in production mode, we compile the MDX document twice, for server/client environment.
However, it is kind of useless: in most cases, the MDX loader will be configured the same way for client/server. It's the case for all our content plugins. The only way to have the 2 compilation outputs to diverge with our content plugins would be to use the undocumented
vfile.data.compilerName(that I'd like to remove later).AB Benchmark
Locally modified code for benchmarking + bypass SSG step:
Test links
CI + tests, it should work exactly as before
https://deploy-preview-10479--docusaurus-2.netlify.app/
Related issues/PRs
siteConfig.future.experimental_faster.swcJsLoader#10435siteConfig.future.experimental_faster.swcJsMinimizer#10441