-
Notifications
You must be signed in to change notification settings - Fork 66
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
Jiti v1.21.1 breaks Docusaurus #237
Comments
Hi dear @slorber. It is a pitty if it is a regressed behavior of babel... I will investigate and keep you updated. |
Thanks for investigating. Sorry not to be more helpful, I'm on holiday 😅 |
Also breaks UnoCSS unocss/unocss#3869 |
Just released [email protected] as hotfix for this issue you can upgrade lockfile for the fix. Recent improvements in mlly.interopdefault seems caused this. (followup investigation: #238) |
Amazing, thanks so much for the prompt fix and release on this! |
Environment
Jiti v1.21.1 does not seem to be retro-compatible with v1.21.0 and breaks Docusaurus usage due to dependency being upgraded
facebook/docusaurus#10199
Reproduction
yarn create docusaurus
It fails on
yarn start
But it gets fixed once we resolve to former Jiti version
Describe the bug
Not sure exactly what happens here but it looks like Docusaurus does not see anymore the named export callbacks we call by convention on our Docusaurus plugins.
The
validateOptions
export should be called by Docusaurus core, but it is not called anymore, so it seems modules loaded by Jiti are slightly different from before.Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: