react-markdown VS vite-tsconfig-paths

This error related to the ReactMarkdown component and the useDisclosure hook in the @chakra-ui/react.

The example above uses react-markdown, but you can use any library you want to render the markdown content. You can also use a transform function to modify the markdown content during the build process. Here is an example that uses MDX to compile the markdown content.

21.react-markdown

github.com/remarkjs/react-markdown - Biblioteca para renderizar markdown em nosso componente react.

3. Setup react-markdown and @tailwindcss/typography

The OpenAI API returns responses in Markdown format. To display responses from the chat, which contain formatting, I used the ReactMarkdown component. For code inserts, I used React Syntax Highlighter.

You can also choose to convert this to Markdown and use our Markdown metafield instead if you prefer, just note you’ll need to install a markdown package to do so. The article Building React Components from headless CMS markdown is a great read about how a package like React Markdown parses markdown from a headless CMS, and explains how to render markdown in a Next.js application.

Thank you! It's actually all thanks to the amazing react-markdown package (https://github.com/remarkjs/react-markdown), can't take any credits there :')

Perhaps something like a markdown renderer. There are plenty of projects that can render markdown, so you could store your blogs that way instead.

Following suggestion in the issue, i looked at vite-tsconfig-paths which is even better because i already have configured vscode through typescript config:

Try this one. https://github.com/aleclarson/vite-tsconfig-paths

We need vite-tsconfig-paths in order to tell Vite how to resolve absolute paths from the tsconfig file. This way you can import modules like this:

You can use vite-tsconfig-paths on SvelteKit project. And it doesn't work, plese try delete generated folder for dev server like .svelte-kit.

We already have configured path aliases with webpack and tsconfig - so I wanted to keep that behavior. Luckily we have the vite-tsconfig-paths exactly for that. It worked well. I could also try using the alias for that.