-
Notifications
You must be signed in to change notification settings - Fork 5
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
Integration nanostores DevTools with Vue as an island in Astro fails #11
Comments
I still haven't tried Nanostoes Devtools with Astro. What error do you see in console logs? |
Nanostores are written in pure JS with declaration types (.d.ts files) without bundling or building. If Nanostores works, devtools should also works. I'm going to assume that the problem is in the versions of the installed packages. We don't yet support “next” Vue Devtools. Try to use |
Have you tried it under Astro integration, inside _app.ts file? When I add it fails with
I think this is because that import is executed on the server |
SyntaxError: The requested module '@vue/devtools-api' does not provide an export named 'setupDevtoolsPlugin' |
Yeah, yeah. That's exactly what I wrote about. Try to install |
OK. This is fine now. There must be an issue in API v7. |
I will not close the issue just yet. Will try to implement new devtools support this month. |
Has this been implemented yet? Looks like the new Vue devtools is live, and Nanostores support seems broken. |
Already working on it. Will try to release in next two days. |
I am using the Astro framework with Vue and nanostores integrations. All is working fine, except I cannot see nanostores Devtools. They are not displayed (out of the box) under Astro DevTools or Vue Devtools.
I guess must add nanostores DevTools as the Vue plugin with the app. use() command. The problem is that the Astro-Vue integration uses a TypeScript file on the server side, so nanostores DevTools can't be added there. Any hints?
This is my repo https://github.com/hipertracker/astro-primevue-minimal
The text was updated successfully, but these errors were encountered: