Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Use Frontmatter for imports.

See original GitHub issue

Really awesome project. I think makes sense to separate imports from markup. One way to do this would be to use frontmatter – a concept made popular by Jekyll and a few other projects.

---
import: { Chart } from '../components/chart'
---

# Here's a chart

The chart is rendered inside our MDX document.

<Chart />

I wonder if anyone else has thoughts on this?

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

jxnblkcommented, Aug 29, 2018

FWIW we decided against using front matter early on. I was originally in favor of it, but now think that MDX is much better without it. That said, it’s not too difficult to set up your own custom loader in front of the mdx-loader if you want to use front matter in your project, as is done here https://github.com/c8r/x0/blob/master/lib/mdx-fm-loader.js

0reactions

silvenoncommented, Aug 29, 2018

Yeah, I don’t see a need for this either. That would be a new synax we’d need to implement and parse without a clear benefit. Import/export takes care of everything already, which is also a standardized syntax, like YAML.