Skip to content
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

Docusaurus website missing import #7589

Closed
6 of 7 tasks
dpang314 opened this issue Jun 9, 2022 · 1 comment · Fixed by #7590
Closed
6 of 7 tasks

Docusaurus website missing import #7589

dpang314 opened this issue Jun 9, 2022 · 1 comment · Fixed by #7590
Labels
documentation The issue is related to the documentation of Docusaurus

Comments

@dpang314
Copy link
Contributor

dpang314 commented Jun 9, 2022

Have you read the Contributing Guidelines on issues?

Prerequisites

  • I'm using the latest version of Docusaurus.
  • I have tried the npm run clear or yarn clear command.
  • I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
  • I have tried creating a repro with https://new.docusaurus.io.
  • I have read the console error message carefully (if applicable).

Description

When running yarn build on the Docusaurus website, Component APITable was not imported, exported, or provided by MDXProvider as global scope is printed twice to the console. The import for APITable is missing in both versions of the no-untranslated-text.md files.

Reproducible demo

No response

Steps to reproduce

  1. Run yarn build in the docusaurus repository

Expected behavior

I did not expect Component APITable was not imported, exported, or provided by MDXProvider as global scope to be printed.

Actual behavior

Component APITable was not imported, exported, or provided by MDXProvider as global scope is printed to the console twice.

Your environment

Self-service

  • I'd be willing to fix this bug myself.
@dpang314 dpang314 added bug An error in the Docusaurus core causing instability or issues with its execution status: needs triage This issue has not been triaged by maintainers labels Jun 9, 2022
@Josh-Cena Josh-Cena added documentation The issue is related to the documentation of Docusaurus and removed bug An error in the Docusaurus core causing instability or issues with its execution status: needs triage This issue has not been triaged by maintainers labels Jun 9, 2022
@Josh-Cena
Copy link
Collaborator

Thanks, the errors are in versioned_docs, the two api/misc/eslint-plugin/no-untranslated-text.md files. If you want to fix that by adding the missing imports it would be great. I didn't fix it because it would automatically be fixed after bumping another two versions, and we seldom edit versioned files unless absolutely needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation The issue is related to the documentation of Docusaurus
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants