You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi thanks for your work on this library, it looks really helpful.
I wanted to try and rewrite my personal site using this library, but I wanted to use Preact instead of React.
When I run the dev mode with ‘npm run dev’ I get this error: ‘can’t read property of undefined(reading context)’
I’m paraphrasing, but that’s the gist of the error. It appears to be an issue with MDXProvider and how it handles ‘context’.
Are you aware of any differences between Preact/React handle using ‘context’? Since Preact is supposed to be mostly compatible with React, I’m surprised I’d run into an issue like this. I’ll try to set up a demo and link it to this issue.
The text was updated successfully, but these errors were encountered:
@bensmithett sorry I wasn’t able to respond until now, but I ended being able to fix my issue by using Yarn instead of npm. For some reason using yarn as the package manager, the dependencies were all installed correctly. When I have time tomorrow, I can write a more detailed comment.
I’m not sure why switching to yarn fixes the issue, but I noticed it when I tried a stripped down version of your template repo on stackblitz, which uses Yarn instead of npm.
Hi thanks for your work on this library, it looks really helpful.
I wanted to try and rewrite my personal site using this library, but I wanted to use Preact instead of React.
When I run the dev mode with ‘npm run dev’ I get this error: ‘can’t read property of undefined(reading context)’
I’m paraphrasing, but that’s the gist of the error. It appears to be an issue with MDXProvider and how it handles ‘context’.
Are you aware of any differences between Preact/React handle using ‘context’? Since Preact is supposed to be mostly compatible with React, I’m surprised I’d run into an issue like this. I’ll try to set up a demo and link it to this issue.
The text was updated successfully, but these errors were encountered: