-
-
Notifications
You must be signed in to change notification settings - Fork 190
feat: integrate chii into playground #1024
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Should I be able to edit elements and styles? |
Noticed that the errors we emit during Combined with the fact that this results in a lot of extra stuff being downloaded, and that it only partially works in Firefox, and that several of the tabs don't really do anything except clutter the UI, I'm forced to wonder whether this is a good change, even though I was enthusiastic about it. Thoughts? |
I think you meant this link vs the localhost link get their names blanked out somehow Overall, I typically go straight to the actual browser's Dev Tools, mostly because the logging can't print objects. It would be nice to have a console that can print everything by default, especially if it doesn't take away the space from the playground panes like the actual devtools. I think it probably makes the playground seem more "professional" and cool especially for the newer folks, so I think it would definitely help svelte's adoption as long as it's not buggy 😄 More specifically.
|
We decided that there were too many drawbacks to using Chii in the playground. |
Swaps out our custom console implementation for the actual Chrome dev tools using Chii.
Closes #523