-
Notifications
You must be signed in to change notification settings - Fork 80
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
Can't get working svelte devtools in Chrome with svelte new version 3.46.4 #69
Comments
a user on svelte discord mentioned that it broke for them when updating from chrome 97 to 99 https://discord.com/channels/457912077277855764/728292755087818924/951864005985697872 |
I have the same problem。 Environment |
Same problem, on MacOs 12.3 rollup.config.js: The same project works in firefox with the firefox extension. |
Yep, same problem. Ubuntu 20.04 Did anyone find a workaround? |
Same Windows 10 build 19044.1586 Last commit in master is 17 June 2021. Is it being actively maintained? |
Solved (on local machine). This is posted until someone with write access can confirm testing & commit to main branch. Same issue listed above: Note in title area now has "PhuongTPham opened this issue on Mar 6 · 6 comments · May be fixed by 70" You all may have this figured out & fixed already, but if not here are the steps: prerequisite to steps: uninstall non-working svelte-devtools extension from your browser
After installing if you still receive the error message--do the hard refresh/f5click here, if all previous steps were completed, it will go away. |
@ontrack1 why isn't this merged yet? |
Related to or shares root cause with #68 most likely. |
Relevant Chromium bug: https://bugs.chromium.org/p/chromium/issues/detail?id=1364293 |
- not working yet, see: sveltejs/svelte-devtools#69
Describe the bug
I just update svelte latest version: 3.46.4 and dev: true in rollup.config.js.
But It can't work svelte dev tools in Chrome, I rerun many times and config same as the document: https://github.com/RedHatter/svelte-devtools
Environment
The text was updated successfully, but these errors were encountered: