-
Notifications
You must be signed in to change notification settings - Fork 924
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 compiling mdx #4809
Comments
This happened from time to time to different users. |
ah ok, it's not a blocker. I'll keep a zip of the workspace and try it again.. |
For me this error happens when the server is started and I create a new component. To resolve it, I have to stop the server, execute bit compile and then start the server again. |
I've also seen this error if you happen to have invalid syntax in your mdx file. I've found it useful to remove all content from the file with the exception of the top line and see if the error goes away. If it does you can start adding back a few lines at a time. |
This may be not installed bit components dependencies. |
this is likely to have been solved by #5067, so it should not happen again from v0.0.570 onwards. repoen the issue if the problem resurfaces :) |
Still happens with yarn but not pnpm |
interesting. why would it happen on yarn? 🤔 also, I've noticed a distinction between plugins-page/
plugin-page.docs.mdx # <-- should work out of the box
plugins-page.mdx # <-- needs env to be mdx
index.ts you can apply the mdx env by using this command:
|
You need to run a |
interesting. @pkhodaveissi - can you open a new in depth issue about it? @GiladShoham will handle |
Getting this error:
It seems it's trying to load the mdx with the react fast refresh, before compiling it to JS.
I will investigate.
Describe the bug
A clear and concise description of the issue.
Steps to Reproduce
bit create
to make a new component, ie,❯ bit create react-component ui/input/search-box
--> get the error
Screenshots, exceptions and logs
Specifications
for harmony workspace
The text was updated successfully, but these errors were encountered: