-
Notifications
You must be signed in to change notification settings - Fork 26
Failed to compile, unexpected character '#' #19
Comments
Thanks! That's definitely a bug. I think I have a fix in #20 if you wanna try installing the latest version |
Hey thanks for attempting to fix it! I do think the issue is resolved for the case I specified but there is one other case I would like to mention and highlight another issue I am facing. The mdx file does seem to be compiling but, I do not see any content on the page right now. I just have I only see a blank page with the following error in the console
Any idea what's going on here? Also, the second case that I mentioned. Is it necessary to have the mdx files inside another folder? In my case, I will most likely need just one mdx file and some components from BloomerJS. If I do place the |
Glad that the original issue was resolved. For your second question, mdx-go uses webpack's |
Ah! That makes sense. I'll stick to the recommended structure if that's the case. Any idea what's the issue with rendering the mdx though? That error does not seem to be going away irrespective of what I do and I always see a blank page and nothing more. |
|
ok so you must have a |
The issue keeps happening:
|
I've been trying to get this to work for a while now but, unfortunately, I haven't had the luck.
Firstly, the directory structure looks like this:
I cd to this directory and run
mdx-go docs
and get the following error:Any idea why it's breaking due to a file that isn't even present in the directory? Is there something wrong on my end that I need to change? Please do let me know.
The text was updated successfully, but these errors were encountered: