MDXTag Error: "components is not defined"
See original GitHub issueBug Report
Describe the bug
When visiting my local docz instance, I am met with the error components is not defined
upon navigating (clicking on a sidebar link) to a specific component’s view.
I am not quite sure what causes the bug. It seems as though my mdx files are compile to be <MDXTag>
components, which accepts a prop components
, but the identifier provided doesn’t seem to exist in the file. 🤷♂️
To Reproduce
Clone, cd packages/core
, npm i
, npm run docz:dev
.
https://github.com/colshacol/g2-ops-component-library
branch: “v1”
Working directly from the packages/core
directory.
Expected behavior
I expect docz to show me the mdx documentation I have written for the specific component.
Environment
macOS High Sierra 10.13.6
node v11.1.0 / v10.8.0
npm v6.2.0 / v6.4.1
// doczrc.js
import { css } from 'docz-plugin-css'
export default {
src: './src/new_components',
plugins: [
css({
preprocessor: 'postcss',
cssmodules: false,
loaderOpts: {
plugins: [],
},
}),
],
}
"docz": "^0.12.12",
"docz-plugin-css": "^0.11.0",
(Same error with 0.12.12, 0.12.11, 0.12.10, and 0.12.9.)
Additional context/Screenshots
Screen recording: https://www.youtube.com/watch?v=XlirTYEnGmg
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:23 (6 by maintainers)
Top GitHub Comments
Same error with the latest version of
docz
(0.12.12)Fixed on v0.12.13 ✅