-
Notifications
You must be signed in to change notification settings - Fork 76
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
gatsby-theme-i18n is incompatible with the new gatsby-plugin-mdx v4 #172
Comments
I was thinking the same thing. I even considered recreating the whole i18n logic to be able to use the new version of MDX. I don't know if that's the best solution, but I independently made an identical change in my local repo, and it worked. |
I published a fork of the i18n packages. (I needed that since this project doesn't seem to be updated anymore.) You can get them all here:
Source code with example is here, but on branch "publish-fork": If this can help someone, I am happy about that... @LekoArts, do you know if there are plans for a better i18n story with Gatsby v5? |
It seems like it, unfortunately. Thanks. I'll check them out in my free time. |
You save my day. |
The new gatsby-plugin-mdx v4 has a lot of internal changes and new features.
Because of these internal changes, gatsby-theme-i18n fails to add the locale for
.mdx
files. Luckily, the fix is easy.The error is in the
gatsby-node.js
file, on line 126.Old Line:
New Line:
I'll do a pull request
The text was updated successfully, but these errors were encountered: