wasp
wasp copied to clipboard
wasp-lang
Chrome DevTools Automatic workspaces support
Bun is implementing metadata for Chrome Dev Tools to directly recognize and edit the local files in the project.
Check demo: https://x.com/jarredsumner/status/1927599856798867792
Maybe we can implement it too?
Vite plugin at https://github.com/ChromeDevTools/vite-plugin-devtools-json
@cprecioso @Martinsos maybe i could work on this , from my understanding do you mean ??
When developers debug Wasp-generated apps in Chrome DevTools They could directly see and edit their original .wasp, TypeScript, and other source files Instead of having to navigate through generated/compiled code.
@cprecioso @Martinsos maybe i could work on this , from my understanding do you mean ??
When developers debug Wasp-generated apps in Chrome DevTools They could directly see and edit their original .wasp, TypeScript, and other source files Instead of having to navigate through generated/compiled code.
Yes that would be it! It sounds pretty tricky though, especially since Wasp generates code so there is that "distance" between the original code and generated one?
@Martinsos @cprecioso Have Started working on this utilizing chrome devtools repo as a reference !! if i get a roadblock will notify you !!
@Martinsos @cprecioso Have Started working on this utilizing chrome devtools repo as a reference !! if i get a roadblock will notify you !!
All right, eager to see what you come up with!
It sounds pretty tricky though
@Martinsos Yep, I added the "good first issue" as I thought that it'd need a low amount of work, but on further review it does have some trickiness to it. I'll remove the tag.
@0xTaneja you're welcome to work on it, but please don't feel the need to continue if you get frustrated!
I think that a wall you'll hit is that we copy user code to .wasp/out/sdk/wasp/src, and then we compile it with the rest of the SDK to .wasp/out/sdk/wasp/dist/src. You don't need to concern yourself with these. We can just map the DevTools to the user's actual code (the one outside of .wasp), the wasp compiler will be compiling these on the fly if they get updated.
@cprecioso I have got the wall earlier !! but i have found a workaround !! will surprise you !!
@cprecioso @Martinsos here's my pr , a few conflicts but will resolve after your feedbacks,
https://github.com/user-attachments/assets/bd553a12-a741-4170-a58c-2e3d1322f27a
a quick demo from my side , i love haskell, and wasp helping me a lot in learning haskell, hence love contributing 💛