Closed duanwilliam closed 2 years ago
@cmfcmf I'm encountering the same issue. In fact I'm encountering lots of pain points while using this plugin. As a Docusaurus maintainer myself, may I ask you to kindly give me write permissions so I can help modernize this plugin and make it more aligned with the core's style & conventions?
Thank you @duanwilliam for reporting this! I am currently blocked on missing type definitions for @docusaurus/theme-translations
, see https://github.com/facebook/docusaurus/issues/6087.
@Josh-Cena I welcome contributions. Please feel free to open issues and/or pull requests. I have spent a lot of time last weekend to catch up with the latest Docusaurus development, but as you say, there is still stuff to do.
Should be fixed in v0.9.0.
Bug description
https://github.com/facebook/docusaurus/pull/5849 refactors the theme translation api and moves the
readDefaultCodeTranslationMessages
function, used in this plugin, from@docusaurus/utils
into a separate package,@docusaurus/theme-translations
. This should probably be updated when Docusaurus get its next stable release in2.0.0-beta.10
.Reproduction
try
yarn start
on canary build (not sure which one corresponds with the breaking pr but tested on 0.0.0-4248).Environment
Package Versions
Node Version
v14.15.0
Docusaurus Environment
preset-classic
[require.resolve('@cmfcmf/docusaurus-search-local'), {}]
Additional context