-
Notifications
You must be signed in to change notification settings - Fork 46
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
No compatible plugin found for workspace with root #2003
Comments
Thank you for reporting this @developermau. I cannot reproduce on a Mac, so I'm guessing this is a Windows-specific issue. I'll try to fix it once I get a VM going :) |
No problem, I understand 👍 . |
In the meantime, try downgrading to v1.22.2, it might fix your problem! |
Thank you so much for your support! Logs
|
Hey @developermau, I got a Windows VM running but haven't yet been able to reproduce. I did find one or two funky things on Windows where the Preview.js process doesn't seem to be restarting properly when you reopen VS Code, it might be linked to that. Just curious if rebooting your computer helps? |
@developermau does the latest version work as well now? |
Describe the bug
Hi everyone!
I have a
React
+Typescript
app created byVite
. Then I created a button component and wanted to see a button preview usingPreview.js
but I had an error:No compatible plugin found for workspace with root
.Reproduction
src/AppButton.tsx
Preview.js
Open AppButton in Preview.js
Also, I tried to stop and start but it didn't work.
Optional 1. Refactor
src/App.tsx
Optional 2. Run development server
Preview.js version
v1.24.4
Framework
React 18.2.0
System Info
Used Package Manager
npm
Extension logs (useful for crashes)
2023-09-14 01:30:41.194 [info] ExtensionService#_doActivateExtension zenclabs.previewjs, startup: false, activationEvent: 'onLanguage:typescriptreact'
Preview logs (useful for rendering errors)
No response
Repo link (if available)
No response
Anything else?
Preview.js is not working on my VSCode.
Google Chrome without console errors.
The text was updated successfully, but these errors were encountered: