-
Notifications
You must be signed in to change notification settings - Fork 50
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
SyntaxError: Unexpected token 'export' #7
Comments
Actually the best thing to do is to ditch xterm-for-react. I had the same problem and its definetly easier to work with xterm.js, useEffect() and useRef to set it up: https://gist.github.com/neuron-electronics/0cabbfa5337a904d689e081e92926fa5#file-component-js |
this replicated for me also |
1 similar comment
this replicated for me also |
This is almost certainly a Next.js or SSR/SSG problem. I can see in the screenshot the Next.js debugger ui, and I was also using Next.js Next.js rejects the library when dynamically importing it in. The maintainer of this repo needs to fix this, because dynamic importing didn't work, I doubt there is a solution to this problem for Next.js users (I hope someone proves me wrong) |
Got it too. |
Describe the bug
After adding the
Xterm
component and firing up the server, I'm being shown this error on a NextJS project. I'm not really sure if there are any other additional configurations to be made in order to render this component properly. If there is, I feel theREADME
section can be improved so that new-users don't face the same issue.To Reproduce
Steps to reproduce the behavior:
Xterm
componentExpected behavior
Render the Terminal UI.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: