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

Vue Devtools not working with starter on Github codespace #14367

Closed
upepo-mwindaji opened this issue Jul 24, 2022 · 2 comments
Closed

Vue Devtools not working with starter on Github codespace #14367

upepo-mwindaji opened this issue Jul 24, 2022 · 2 comments

Comments

@upepo-mwindaji
Copy link

Environment

RootDir: /workspaces/nuxt3
Nuxt project info:

  • Operating System: Linux
  • Node Version: v16.14.2
  • Nuxt Version: 3.0.0-rc.6
  • Package Manager: yarn@1.22.15
  • Builder: vite
  • User Config: dev, vite
  • Runtime Modules: -
  • Build Modules: -

Reproduction

https://github.com/upepo-mwindaji/nuxt3

Describe the bug

Chrome devtools does not work when running yarn dev on starter template within Github codespace

Additional context

I have tried running the same on local machine and everything works fine

I have tried both version of Vue Devtools: current and beta
I have tried on Google cloud VM, behavior is the same
I have tried on rc4 and rc5 also did not work
I have tried adding following configurations:
{ dev: true, vite: { mode: 'development' } }
I have tried running with yarn and pnpm
No issue running Nuxt 2 on those environments

Might be related to nuxt/framework#2284

Screenshot 2022-07-23 at 22 24 12

Logs

No response

@danielroe
Copy link
Member

I was not able to reproduce this, though note that I did need to set vite.server.hmr.protocol to wss.

import { defineNuxtConfig } from 'nuxt'

// https://v3.nuxtjs.org/api/configuration/nuxt.config
export default defineNuxtConfig({
  vite: {
    server: {
      hmr: {
        protocol: 'wss'
      }
    }
  }
})

See some debugging steps here - particularly trying using a clean Chrome profile.

@danielroe danielroe closed this as not planned Won't fix, can't repro, duplicate, stale Jul 25, 2022
@upepo-mwindaji
Copy link
Author

I retried adapting the vite configuration as you suggested and it worked indeed.

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

No branches or pull requests

2 participants