-
Notifications
You must be signed in to change notification settings - Fork 195
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
BUG: mdx-deck doesn't seem to work #92
Comments
This does not look like an issue anymore 🎉 |
Is this issue still not resolved? or resolved? |
@junghyeonsu Are you observing the same problem? If so, what's the project link? If a different one, would you mind opening a new issue? |
Thank you! @jrvidal Dependency installation succeeds, but the start command fails. |
Yep, I can reproduce. I've added the issue to our internal tracker. Thanks for reporting! |
name: Bug report
about: Create a report to help us improve
title: 'mdx-deck doesn't seem to work '
labels: ''
assignees: ''
Describe the bug
A clear and concise description of what the bug is.
MDX deck seems to break- try running
npm run start
in the project. Seems to use gatsby under the hood so maybe related to #4 ?This is the specific error it's throwing in the terminal:
Link to the blitz that caused the error
https://stackblitz.com/edit/mdx-deck?file=package.json
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Version of webcontainer
Hash: 7286dbe8d47d3473cde7be488b7d048fb59b05f2
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Browser name = Chrome
Full version = 90.0.4430.212
Major version = 90
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36
performance.memory = {
totalJSHeapSize: 71231247,
usedJSHeapSize: 56440659,
jsHeapSizeLimit: 4294705152
}
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: