-
Notifications
You must be signed in to change notification settings - Fork 53
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
Error: Cannot handle unknown node raw
when using with @mdx-js/mdx
#125
Comments
Cool, makes sense, you're welcome to take a look at switching to rehype raw 👍🏻 |
I was getting this error when specifying filename in the markdown. Changed
to
and this error went away. |
If anyone else is struggling with this, and also tried going down the rehype-raw rabbit hole (and failed), I've made a workaround. I created a remark plugin that you can add directly after // This is an excerpt from a @docusaurus/preset-classic docs configuration object
remarkPlugins: [
require("remark-shiki-twoslash"),
require("remark-html-to-jsx"),
],
|
Running into this now with Docusaurus v3 stable release. I will try to use @ksandin's workaround (it's not a published package, so need to bring it in manually). |
So, I patched
And that does "fix" the error, but it appears the resulting HTML set is not processed through That |
But not together! See shikijs/twoslash#125 (comment)
…for developing (#4) * docs: mdx -> md with node-loader * chore: eslint mdx file test imported component works * docs: mdx is epic! Import real code into markdown files * feat: Use `import()` to make our own mdxToMd that actually works w/o building and esbuild * docs: remark-code-import and remark-shiki-twoslash working But not together! See shikijs/twoslash#125 (comment) * docs: Removed shiki does not work reliably. Table does though * docs: Add remark toc * docs: eslint-plugin-expect-type is daboom Finally the right solution vs. markdown twoslash queries which is more appropriate in react/html context * docs: Generate table of supported sdks via react! * chore: Switching everything over to ESM Can still ship cjs lib, but working in ESM * chore: Fix linter issues * fix: try to fix build * chore: Force correct pre-install script * fix: Jest test with esm modules * chore: setup upterm to test * fix: build commands by switching all to esm * Revert "chore: setup upterm to test" This reverts commit 4be5ed8. * fix: missed apollo json * Revert "Revert "chore: setup upterm to test"" This reverts commit 09e578d. * fix: mdx build due to needing react-jsx * Revert "Revert "Revert "chore: setup upterm to test""" This reverts commit 58bded7. * chore: Still publish cjs for now even if we fully work in esm Don't want to have esm only package for now. Will have to dual publish
So, this issue from 2021 means that |
I am trying to use
remark-shiki-twoslash
with@mdx-js/mdx@2.0.0-rc.2
(v2) and have the following error:Full details are on this issue mdx-js/mdx#1820
The text was updated successfully, but these errors were encountered: