Skip to content
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

Vite Plugin I Vue DevTools #459

Closed
Yordan-Ramchev opened this issue Mar 4, 2024 · 4 comments
Closed

Vite Plugin I Vue DevTools #459

Yordan-Ramchev opened this issue Mar 4, 2024 · 4 comments

Comments

@Yordan-Ramchev
Copy link
Contributor

Is your feature request related to a problem?

We provide a Vite plugin for running Vue DevTools. If your project uses Vite, we highly recommend using it as the preferred option for running DevTools, as it offers more powerful features.

https://devtools-next.vuejs.org/guide/vite-plugin#vite-plugin

Describe the solution

  1. Add vite-plugin-vue-devtools in template/base/package.json
  2. Add VueDevTools in template/base/vite.config.js.data.mjs
{
    id: 'vite-plugin-vue-devtools',
    importer: "import VueDevTools from 'vite-plugin-vue-devtools'",
    initializer: 'VueDevTools()'
}

Can I get an approval to apply these updates?

@sodatea
Copy link
Member

sodatea commented Mar 6, 2024

That's a great idea!
On a second thought, though, the devtools-next project is still under heavy development; it might not be the best time to recommend the project to average users.

So, how about adding it as an "(experimental)" option at the end?

@Yordan-Ramchev
Copy link
Contributor Author

Yordan-Ramchev commented Mar 6, 2024

Yeah, that's a reasonable concern/solution.

So now the steps that we have to take are:

  1. Add another prompt option — Add VueDevtools extension for debugging? (experimental)
  2. Create vite.config.js.data.mjs in template/config/devtools
  3. Update snapshot.mjs with VueDevtools feature flag
  4. Update CI script
  5. Update locales folder.
  6. Update README.md image

Should I proceed with applying these changes?

@sodatea
Copy link
Member

sodatea commented Mar 6, 2024

Yeah, go ahead, please.

@Yordan-Ramchev
Copy link
Contributor Author

PR #460 merged — I'm closing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants