contentlayerdev / contentlayerdev/contentlayer

Nested Component imports via MDX aren't JSX transformed

Offen
#309 6 Kommentare 4 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
blocked-upstream help wanted meta: never-stale topic: markdown/mdx
Vorherrschende Sprache
TypeScript
Sterne
3.5k
Forks
192
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

I'm running into problems when trying to import components inside a `.mdx` file, and more specifically when the imported component also imports other components. What I want to be able to do
```
// first-post.mdx

// ideally, I would like to be able to do this
import TestComponent from "components/TestComponent";

// this currently works unless this component imports another component
import TestComponent from "./components/TestComponent";

```
Importing the component by starting with the base path works as long as it is a standalone component and does not import another component. If that component does include an import statement, I get the following error:
```
error - SyntaxError: Unexpected token '<'
at new Function ()
at getMDXComponent (file:///Users/andy/Documents/Dev/2022/webby/node_modules/next-contentlayer/src/hooks/useMDXComponent.ts:18:14)
at file:///Users/andy/Documents/Dev/2022/webby/node_modules/next-contentlayer/src/hooks/useMDXComponent.ts:23:30
at Object.useMemo (/Users/andy/Documents/Dev/2022/webby/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5124:19)
at Object.useMemo (/Users/andy/Documents/Dev/2022/webby/node_modules/react/cjs/react.development.js:1650:21)
at useMDXComponent (file:///Users/andy/Documents/Dev/2022/webby/node_modules/next-contentlayer/src/hooks/useMDXComponent.ts:23:16)
at SinglePostPage (webpack-internal:///./pages/posts/[slug].tsx:42:96)
at renderWithHooks (/Users/andy/Documents/Dev/2022/webby/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5658:16)
at renderIndeterminateComponent (/Users/andy/Documents/Dev/2022/webby/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5731:15)
at renderElement (/Users/andy/Documents/Dev/2022/webby/node_modules/react-dom/cjs/react-dom-server.browser.development.js:5946:7) {
page: '/posts/[slug]'
```
The weird thing is, I'm having this issue on a project that I just spun up this morning, but not on a project that was created several months ago, even though they are using the same version of Next and ContentLayer. This could mean that it's user error, but I've looked in detail at the setup/configs for both projects and cannot find the issue.

### Repro
- A minimalist reproduction [can be found here](https://github.com/andy-stewart-design/Contentlayer-Repro)
---
- The other project that I mentioned earlier that seems to be working correctly [can be found here](https://github.com/andy-stewart-design/ydna)
- Specifically, you can see it working in [this post](https://github.com/andy-stewart-design/ydna/blob/main/content/snippets/react-animation-frame-hook.mdx), which is importing [this component](https://github.com/andy-stewart-design/ydna/blob/main/components/content/snippets/ReactAnimationFrame.tsx)
- Like I mentioned, I'm not able to find a meaningful difference in the structure/configs of the two projects

### Attempted Solutions:
- I'm getting the same error as mentioned in [this issue](https://github.com/contentlayerdev/contentlayer/issues/180). However, I have double checked, and I am defining the `contentType` as `mdx`. #180
- I also tried defining the cwd inside of `makeSource` as described [here](https://github.com/contentlayerdev/contentlayer/issues/302. ), but that did not resolve the issue. #302

Beitragsleitfaden

Beitragsleitfaden öffnen

Rechercherichtung

Beginne mit src/hooks/useMDXComponent.ts an den im Stacktrace gezeigten Zeilen und reproduziere anschließend den Fehler mit dem verlinkten Contentlayer-Repro-Projekt. Vergleiche die transformierte Ausgabe für eine eigenständige Komponente und eine mit verschachtelten Imports und verwende pages/posts/[slug].tsx als Rendering-Einstiegspunkt. Als erledigt gilt die Aufgabe, wenn importierte Komponenten mit ihren eigenen Imports ohne den Fehler Unexpected token gerendert werden.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Tech-Stack
next.js, react, typescript
Bereich
build-system
Issue-Typ
Bug
Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Aktivitätsstatus
Veraltet
Klarheit
Größtenteils klar
Anfängerfreundlichkeit
35/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.